From: Keir Fraser <keir@xensource.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>,
Jan Beulich <jbeulich@novell.com>,
xen-devel@lists.xensource.com, Keir Fraser <keir@xensource.com>
Subject: Re: EFER in HVM guests
Date: Wed, 29 Nov 2006 17:21:50 +0000 [thread overview]
Message-ID: <C193722E.53FE%keir@xensource.com> (raw)
In-Reply-To: <8FFF7E42E93CC646B632AB40643802A80184FF9F@scsmsx412.amr.corp.intel.com>
*Please* can you make the handling of generic CPUID leaves and architectural
MSRs common HVM code? There is lots of needless code duplication right now
with niggling differences that shouldn't be necessary.
-- Keir
On 29/11/06 16:34, "Nakajima, Jun" <jun.nakajima@intel.com> wrote:
>> I think it does - allowing a guest to enable EFER.LME when the
>> hypervisor is a 32-bit one is clearly a security problem: While I
>> haven't tried it, I would suspect the moment you load a context
>> with such an EFER the whole system's dead.
>> Not being able to access EFER is also a potential problem, as a
>> guest should be allowed to set EFER.NX (at least) - the CPUID
>> handling code specifically does not suppress this bit if the guest
>> is allowed to use PAE (which we agreed a few days ago should
>> be the default anyway).
>>
>> Jan
>>
>
> I agree that we should allow 32-bit guests to set EFER.NX on the PAE
> Xen. We'll fix it. EFER.SCE should not be set on IA-32.
next prev parent reply other threads:[~2006-11-29 17:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 16:34 EFER in HVM guests Nakajima, Jun
2006-11-29 17:21 ` Keir Fraser [this message]
2006-11-29 17:37 ` Petersson, Mats
-- strict thread matches above, loose matches on Subject: below --
2006-12-20 1:27 Li, Xin B
2006-12-19 14:25 Li, Xin B
2006-12-19 20:38 ` Woller, Thomas
2006-12-20 11:29 ` Petersson, Mats
2006-12-19 9:12 Li, Xin B
2006-12-19 9:46 ` Petersson, Mats
2006-12-19 7:04 Li, Xin B
2006-12-19 6:44 Li, Xin B
2006-12-18 15:10 Li, Xin B
2006-12-18 15:47 ` Petersson, Mats
2006-12-13 14:13 Li, Xin B
2006-12-13 14:09 Li, Xin B
2006-12-13 12:48 Li, Xin B
2006-12-13 13:08 ` Jan Beulich
2006-12-13 14:37 ` Keir Fraser
2006-12-15 16:04 ` Woller, Thomas
2006-11-29 18:24 Nakajima, Jun
2006-11-29 13:07 Jan Beulich
2006-11-29 13:09 ` Keir Fraser
2006-11-29 14:08 ` Jan Beulich
2006-11-29 14:22 ` Petersson, Mats
2006-11-29 13:11 ` Petersson, Mats
2006-11-29 14:09 ` Jan Beulich
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=C193722E.53FE%keir@xensource.com \
--to=keir@xensource.com \
--cc=jbeulich@novell.com \
--cc=jun.nakajima@intel.com \
--cc=xen-devel@lists.xensource.com \
/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.