From: "Scott Parish" <srparish@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, jun.nakajima@intel.com,
Scott Parish <srparish@us.ibm.com>
Subject: Re: [patch] nx bit shouldn't get set when disabled
Date: Wed, 8 Jun 2005 22:39:40 +0000 [thread overview]
Message-ID: <20050608223940.GI14747@us.ibm.com> (raw)
In-Reply-To: <d246c2258805470a73cb0b357f3a6739@cl.cam.ac.uk>
Sorry, i'll be more careful in the future.
sRp
On Wed, Jun 08, 2005 at 10:31:36PM +0100, Keir Fraser wrote:
>
> You sent this only to me (not Jun or the list). :-)
>
> On 8 Jun 2005, at 21:47, Scott Parish wrote:
>
> >On Wed, Jun 08, 2005 at 10:23:47PM +0100, Keir Fraser wrote:
> >
> >>I'm not inclined to take patches for xen/x86_64/pci-dma.c
> >>anyway: I think we can patch the xen/i386 one and share it with
> >>xen/x86_64.
> >
> >I'll start looking into this.
> >
> >>So the extra masking isn't required?
> >
> >Not for any reason i know of. Jun?
> >
> >sRp
> >
> >--
> >Scott Parish
> >Signed-off-by: srparish@us.ibm.com
>
>
--
Scott Parish
Signed-off-by: srparish@us.ibm.com
next prev parent reply other threads:[~2005-06-08 22:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 21:02 [patch] predicate NX flag Nakajima, Jun
2005-06-08 18:06 ` [patch] nx bit shouldn't get set when disabled Scott Parish
2005-06-08 19:56 ` Keir Fraser
2005-06-08 19:47 ` Scott Parish
2005-06-08 21:23 ` Keir Fraser
[not found] ` <20050608204727.GH3182@us.ibm.com>
[not found] ` <d246c2258805470a73cb0b357f3a6739@cl.cam.ac.uk>
2005-06-08 22:39 ` Scott Parish [this message]
2005-06-09 12:59 ` Scott Parish
-- strict thread matches above, loose matches on Subject: below --
2005-06-08 21:30 Ian Pratt
2005-06-08 21:28 ` Keir Fraser
2005-06-08 21:56 Nakajima, Jun
2005-06-08 22:00 ` Keir Fraser
2005-06-08 22:47 Nakajima, Jun
2005-06-08 22:33 ` Scott Parish
2005-06-08 23:29 Nakajima, Jun
2005-06-09 15:02 Nakajima, Jun
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=20050608223940.GI14747@us.ibm.com \
--to=srparish@us.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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.