From: Jerone Young <jerone@gmail.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] supporting non-NX/XD capable processors on x86_64 xenlinux
Date: Wed, 17 Aug 2005 19:43:32 -0500 [thread overview]
Message-ID: <9f50a7a005081717435b03b396@mail.gmail.com> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D3720017304E65827@scsmsx402.amr.corp.intel.com>
This is identical to the patch Scott Parish sent awhile back. Jun you
said that this was not a good way of going about fixing this (actually
it was kind of toward another problem ...but I think we were also
trying to get x86-64 xen to just boot at the time). I guess this is
the best way then?
On 8/17/05, Nakajima, Jun <jun.nakajima@intel.com> wrote:
> I remember some people complained that x86_64 xenlinux failed to boot on
> the systems with processor(s) that does not NX/XD. The patch should fix
> the problem as far as I tested.
>
> Signed-off-by: Jun Nakajima <jun.nakajima@intel.com>
>
> Jun
> ---
> Intel Open Source Technology Center
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
>
>
next prev parent reply other threads:[~2005-08-18 0:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 23:12 [PATCH] supporting non-NX/XD capable processors on x86_64 xenlinux Nakajima, Jun
2005-08-18 0:07 ` David Hopwood
2005-08-18 0:43 ` Jerone Young [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-18 4:29 Nakajima, Jun
2005-08-18 8:48 ` Keir Fraser
2005-08-18 14:15 Nakajima, Jun
2005-08-18 15:09 ` Keir Fraser
2005-08-18 15:39 ` Jerone Young
2005-08-18 16:05 ` Keir Fraser
2005-08-18 15:51 ` Andi Kleen
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=9f50a7a005081717435b03b396@mail.gmail.com \
--to=jerone@gmail.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.