From: Ryan Harper <ryanh-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Zachary Amsden <zach-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Ryan Harper <ryanh-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Subject: Re: [RFC][PATCH] ignore set_cr3 GP fault in non-pae mode
Date: Tue, 18 Sep 2007 17:03:08 -0500 [thread overview]
Message-ID: <20070918220308.GF7519@us.ibm.com> (raw)
In-Reply-To: <1190152700.8353.14.camel-cxY/u30q8FloTgUnLF1by8fTvwmfpRNyZeezCHUQhQ4@public.gmane.org>
* Zachary Amsden <zach-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org> [2007-09-18 16:59]:
> On Tue, 2007-09-18 at 16:25 -0500, Ryan Harper wrote:
> > * Nakajima, Jun <jun.nakajima-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> [2007-09-18 16:22]:
> > > Anthony Liguori wrote:
> > > > Ryan Harper wrote:
> > > > > Playing around with running VMware-server within a KVM guest and
> > > noticed
> > > > > that whenever we launch a VM within the guest, KVM reports a GP
> > > fault in
> > > > > set_cr3. Removing the fault injection (raised for attempting to set
> > > > > reserved bits) for the non-pae case allows memtest to boot and run
> > > > > within VMWare Server, running in a KVM Linux guest.
> > > > >
> > > > > This same test (Linux, VMware-server, booting/running memtest iso)
> > > works
> > > > > fine on bare-metal. Thoughts?
> > > > >
> > > >
> > > > Setting reserved bits is different from setting MBZ bits since the
> > > > behaviors undefined. If something as common as VMware is depending on
> > > > being able to set a reserved bit then perhaps the right thing to do
> > > from
> > > > KVM's perspective is to let it.
> > > >
> > > > I'm curious if Zach or Jun have any comments about the right thing to
> > > do
> > > > here.
> > > >
> > >
> > > As long as the guest is protected mode (unlike the long mode), the Intel
> > > spec does _not_ say that reserved bits checking is enforced for CR3. As
> > > far as I looked at the AMD spec, looks like #GP is caused even in
> > > protected mode... Does the test work for AMD systems?
> >
> > I ran my test on an AMD host.
>
> We have a test which verifies #GP is not caused by setting the bits on
> either AMD or Intel chips. "Stray" bits can get turned on in some cases
> when switching between 64-bit, PAE and non-PAE address modes.
>
> Were you testing on a 64-bit host kernel?
64-bit Host running 32-bit KVM Guest. VMware-server shouldn't be seeing
anything 64-bit AFAIK.
>
> Zach
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-09-18 22:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 19:05 [RFC][PATCH] ignore set_cr3 GP fault in non-pae mode Ryan Harper
[not found] ` <20070918190516.GC7519-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-09-18 19:15 ` Anthony Liguori
[not found] ` <46F023D8.90905-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-09-18 21:21 ` Nakajima, Jun
[not found] ` <97D612E30E1F88419025B06CB4CF1BE1037F9013-1a9uaKK1+wJcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-18 21:25 ` Ryan Harper
[not found] ` <20070918212509.GE7519-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-09-18 21:34 ` Nakajima, Jun
2007-09-18 21:58 ` Zachary Amsden
[not found] ` <1190152700.8353.14.camel-cxY/u30q8FloTgUnLF1by8fTvwmfpRNyZeezCHUQhQ4@public.gmane.org>
2007-09-18 22:03 ` Ryan Harper [this message]
[not found] ` <20070918220308.GF7519-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-09-19 8:57 ` Avi Kivity
[not found] ` <46F0E46C.1060905-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-19 14:55 ` Ryan Harper
[not found] ` <20070919145536.GH7519-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-09-19 15:08 ` Anthony Liguori
[not found] ` <46F13B5F.4050107-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-09-19 16:01 ` Zachary Amsden
[not found] ` <1190217717.8353.29.camel-cxY/u30q8FloTgUnLF1by8fTvwmfpRNyZeezCHUQhQ4@public.gmane.org>
2007-09-19 16:26 ` Avi Kivity
2007-09-19 17:09 ` Ryan Harper
2007-09-23 12:57 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070918220308.GF7519@us.ibm.com \
--to=ryanh-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=zach-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.