From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Knorr Subject: Re: Re: [Xen-changelog] Fix NX/XD enable on secondary CPUs. Date: Wed, 13 Jul 2005 13:14:25 +0200 Message-ID: <20050713111425.GB5047@bytesex> References: <87vf3fko1x.fsf@bytesex.org> <315357b30e7899abafb8910435dad331@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <315357b30e7899abafb8910435dad331@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Wed, Jul 13, 2005 at 11:52:27AM +0100, Keir Fraser wrote: > > Does EFER_NX need setting for 32-bit PAE? > > We don't set it for *any* cpus in x86_32 builds, even cpu0... The Dom0 linux kernel probably does for CPU #0 ... > > (XEN) (file=traps.c, line=872) Non-priv domain attempted > >RDMSR(c0000080,00000000,20100000). > > (XEN) (file=traps.c, line=864) Non-priv domain attempted > >WRMSR(c0000080,00000800,00000000). ... what the DomU kernel isn't allowed to do on CPU #1. Gerd -- panic("it works"); /* avoid being flooded with debug messages */