From: Jerone Young <jyoung5@us.ibm.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: xen-devel@lists.xensource.com
Subject: RE: HG question
Date: Fri, 15 Jul 2005 11:32:42 -0500 [thread overview]
Message-ID: <1121445163.3036.7.camel@thinkpad> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D37200173048F31C2@scsmsx402.amr.corp.intel.com>
Well we had an issue with our blades where the bios disabled the ability
for the CPU to interpert NX bit. We should have a check to see if the NX
bit is supported & remove it from pages if it's not. I'll get a patch to
the list on this.
On Fri, 2005-07-15 at 09:07 -0700, Nakajima, Jun wrote:
> BTW, the current x86_64 xenlinux requires the CPUs to support NX/XD.
> It's basically a bug, but the priority is low at this point because only
> very early stepping of x86_64 CPUs don't support NX/XD as far as I know.
>
> Keir Fraser wrote:
> > On 15 Jul 2005, at 16:31, Puthiyaparambil, Aravindh wrote:
> >
> >> Is there any way to find out using mercurial if a certain patch was
> >> applied to the unstable tree or not? For example what command should
> >> I use to find out if "[PATCH] Restoring NX/XD for x86_64 xenlinux"
> >> made it into the tree or not?
> >
> > hg -v history | grep "Restoring NX"
> >
> > -- Keir
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
> Jun
> ---
> Intel Open Source Technology Center
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
--
Jerone Young
IBM Linux Technology Center
jyoung5@us.ibm.com
512-838-1157 (T/L: 678-1157)
next prev parent reply other threads:[~2005-07-15 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-15 16:07 HG question Nakajima, Jun
2005-07-15 16:32 ` Jerone Young [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-15 15:31 Puthiyaparambil, Aravindh
2005-07-15 15:38 ` Mark Williamson
2005-07-15 15:44 ` Keir Fraser
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=1121445163.3036.7.camel@thinkpad \
--to=jyoung5@us.ibm.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.