All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Gianluca Guida <gianluca.guida@eu.citrix.com>
Cc: "Li, Haicheng" <haicheng.li@intel.com>,
	"'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>,
	"Li, Xin" <xin.li@intel.com>
Subject: Re: Weekly VMX status report. Xen: #18846 & Xen0: #749
Date: Sat, 13 Dec 2008 14:06:18 +0000	[thread overview]
Message-ID: <C56971DA.2035D%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4942F41D.6060702@eu.citrix.com>

On 12/12/2008 23:30, "Gianluca Guida" <gianluca.guida@eu.citrix.com> wrote:

> Keir Fraser wrote:
>> Is there any guest that actually cares about having EFER_NX really cleared?
>> Presumably the only way of detecting this would be reserved-bit page faults,
>> which no OS is likely to want to deliberately cause?
> 
> Yes, no OS we've actually experienced at the moment rely on reserved bit
> faults (with the most notable exception of Tim's fast path for MMIO and
> non present pages in Xen's shadow entries).
> I am sure about this for a very simple reason: -- some kind of secret I
> would like to share with you and xen-devel -- shadow code doesn't check
> at all for reserved bits when propagating changes from guest to shadows,
> so we never propagate reserved bit faults to guests. [working on this]

Well, I vote for leaving EFER_NX always on then. It makes the code simpler
too. Anyone against this?

 -- Keir

  reply	other threads:[~2008-12-13 14:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E88DD564E9DC5446A76B2B47C3BCCA1540A67C2A@pdsmsx503.ccr.corp.intel.com>
2008-12-07  8:41 ` Weekly VMX status report. Xen: #18846 & Xen0: #749 Keir Fraser
2008-12-08  3:00   ` Cui, Dexuan
2008-12-12 20:37   ` Gianluca Guida
2008-12-12 23:22     ` Keir Fraser
2008-12-12 23:30       ` Gianluca Guida
2008-12-13 14:06         ` Keir Fraser [this message]
2008-12-13 15:14           ` Nakajima, Jun
2008-12-13 15:40             ` Keir Fraser
2008-12-13 22:43               ` Nakajima, Jun
2008-12-13 23:21                 ` Keir Fraser
2008-12-15 13:02                 ` Keir Fraser
2008-12-16  5:54                   ` Li, Haicheng
2008-12-16  7:24                     ` Li, Haicheng
2008-12-16 11:55                       ` Keir Fraser
     [not found] <E88DD564E9DC5446A76B2B47C3BCCA15432C0FC2@pdsmsx503.ccr.corp.intel.com>
2008-12-16 12:29 ` Keir Fraser
2008-12-16 12:33   ` Li, Xin
2008-12-06 11:45 Li, Haicheng
2008-12-06 12:16 ` Keir Fraser
2008-12-06 12:21   ` Li, Haicheng

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=C56971DA.2035D%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=gianluca.guida@eu.citrix.com \
    --cc=haicheng.li@intel.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xin.li@intel.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.