[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] virtualization of cr0 reg flags on hvm system


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Garth Goodson" <ggoodson@xxxxxxxxx>
  • Date: Tue, 22 Aug 2006 10:13:31 -0700
  • Delivery-date: Wed, 23 Aug 2006 02:12:01 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=OqzZG/boD5P7qr67tn1AnSnm83Q08uKs+PB894DsleS7rkAjC2+ZPsHns77FUKcYHqR2X5qdbZKhU9BaRIMuJ3xGweKIeV45wbAqxDW8yGOcpWcFPQlMkBDI3eN0+KoXn6RW97xmHtjnSf4C9f6mSAyrorEVhpakB3GVE3vfJ/A=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I'm experimenting with getting a fully virtualized i386 system up and
running on AMD HVM hardware under Xen.  (The reason for using i386 and
not amd64 is that the amd64 dies early in the kernel loading process.)

I have found that the kernel boots until it reaches a point where it
tries to load the cr0 register with the current cr0 value or'ed with a
set of flags.  In particular the load_cr0 call below never seems to
complete.  If I remove the CR0_WP (write-protect) flag, the kernel
continues booting.

I'm using xen unstable (tip's changeset: 11217:6a8204e4619d).  Is the
support of the WP flag a known issue?  Are there any fixes for it?


1224         cr0 = rcr0();
1225         /*
1226          * CR0_MP, CR0_NE and CR0_TS are also set by npx_probe() for the
1227          * BSP.  See the comments there about why we set them.
1228          */
1229         cr0 |= CR0_MP | CR0_NE | CR0_TS | CR0_WP | CR0_AM;
1230         load_cr0(cr0);

Thanks,
-Garth

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.