WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [Patch] Enable SMEP CPU feature support for XEN itself

To: "Li, Xin" <xin.li@xxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>, "Yang, Wei Y" <wei.y.yang@xxxxxxxxx>
Subject: Re: [Xen-devel] [Patch] Enable SMEP CPU feature support for XEN itself
From: Keir Fraser <keir.xen@xxxxxxxxx>
Date: Thu, 02 Jun 2011 20:24:24 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 02 Jun 2011 12:25:06 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:user-agent:date:subject:from:to:cc:message-id :thread-topic:thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=lIqSBzAdnd+u5Ebwoo9ekC9F4K2xOpizEPUTpy1CrXk=; b=SB5bJt/wjefBmE/T+SM+QJ6fDHSSY+qFa/Tpx1JroSVelAxjRwaWY2vF3MgTNUGS0h +rSgR4hgfAvLfkKj5iZQdHqnrOszX3qLEzGgQyxgcwrBpQvwcitydFbUlPo6mZcShK6N e1MPsG4X8VIKJ2RnDN8XlZnENHt428LH5gn/Y=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=lxkUzXCVH8s/hXuT9Fyvcb8sGGu095cEGLRyKAJMCI0sI1n5NXXbMmcpuoaDpZhLPa F1XBeEiL2Em+73Y1O3SOv04Ah3iHNmOZyAVOEqVgBRRfU7ubzIKvcQwu4i0AJs0ko8Bu S9UZwhViTW5NUYTFV1+YA7/vuR1eEmjT2dUW0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <FC2FB65B4D919844ADE4BE3C2BB739AD5AB9E58C@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcwhKSFqC1+9aLNySkqezZkJGvVaUgACElDwAApQ4SE=
Thread-topic: [Xen-devel] [Patch] Enable SMEP CPU feature support for XEN itself
User-agent: Microsoft-Entourage/12.29.0.110113
On 02/06/2011 15:36, "Li, Xin" <xin.li@xxxxxxxxx> wrote:

>> } else
>>> setup_clear_cpu_cap(X86_FEATURE_SMEP);
> 
> This needs to be done on APs too.  Thus I think we still need define
> setup_smep as __cpuinit.

The whole point of setup_clear_cpu_cap() is that it only needs to run on the
BP and the change gets picked up by every AP automatically as it boots.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel