All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: Zachary Amsden <zach-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>,
	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: Wed, 19 Sep 2007 09:55:36 -0500	[thread overview]
Message-ID: <20070919145536.GH7519@us.ibm.com> (raw)
In-Reply-To: <46F0E46C.1060905-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

* Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> [2007-09-19 03:58]:
> Ryan Harper wrote:
> >>
> >>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.
> >  
> 
> If the host is 64-bit, so is the guest, although the guest can choose to 
> ignore the 64-bit capabilities (and 32-bit guest OSes do; but VMware 
> might be doing something tricky).

Hrm.  I'm not sure I understand the distiction you are making.  I'll
give a 32-bit host a try without the patch and see if I see the same
behavior.

-- 
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/

  parent reply	other threads:[~2007-09-19 14:55 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
     [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 [this message]
     [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=20070919145536.GH7519@us.ibm.com \
    --to=ryanh-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@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.