From: "Tian, Kevin" <kevin.tian@intel.com>
To: David Woodhouse <dwmw2@infradead.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
"Anvin, H Peter" <h.peter.anvin@intel.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v3] x86/ept: Allow write-combining on !mfn_valid() MMIO mappings again
Date: Fri, 14 Apr 2017 07:51:34 +0000 [thread overview]
Message-ID: <AADFC41AFE54684AB9EE6CBC0274A5D190CAAEC7@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1486380790.5110.71.camel@infradead.org>
> From: David Woodhouse [mailto:dwmw2@infradead.org]
> Sent: Monday, February 6, 2017 7:33 PM
>
> On Fri, 2017-01-27 at 10:36 -0500, Konrad Rzeszutek Wilk wrote:
> > . snip ..
> > >
> > > >
> > > > Signed-off-by: David Woodhouse <dwmw@amazon.com>
> > > Reviewed-by: Jan Beulich <jbeulich@suse.com>
> > >
> > > But before committing I'd prefer to have a VMX maintainer ack
> > > too.
> > Who is gone until Feb yth (Spring festival in China).
>
> Not sure what number that 'y' was supposed to be, but I see Kevin
> posting today... :)
>
> Would also be very good to have a definitive answer about the safety of
> mixing WC and UC on MMIO mappings on Intel hardware.
answer is yes, it's safe.
Thanks
Kevin
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-04-14 7:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 12:28 Xen Security Advisory 154 (CVE-2016-2270) - x86: inconsistent cachability flags on guest mappings Xen.org security team
2017-01-25 14:08 ` David Woodhouse
2017-01-25 14:21 ` Jan Beulich
2017-01-25 14:34 ` David Woodhouse
2017-01-25 16:08 ` David Woodhouse
2017-01-26 8:57 ` [PATCH] x86: Allow write-combining on MMIO mappings again David Woodhouse
2017-01-26 10:45 ` Jan Beulich
2017-01-26 10:55 ` David Woodhouse
2017-01-26 11:32 ` Jan Beulich
2017-01-26 12:39 ` [PATCH v2] x86/ept: Allow write-combining on !mfn_valid() " David Woodhouse
2017-01-26 14:35 ` Jan Beulich
2017-01-26 14:42 ` David Woodhouse
2017-01-26 14:50 ` [PATCH v3] " David Woodhouse
2017-01-26 15:48 ` Jan Beulich
2017-01-27 15:36 ` Konrad Rzeszutek Wilk
2017-02-06 11:33 ` David Woodhouse
2017-02-07 5:08 ` Tian, Kevin
2017-04-14 7:51 ` Tian, Kevin [this message]
2017-02-07 5:05 ` Tian, Kevin
2017-02-08 16:04 ` David Woodhouse
2017-02-01 20:23 ` Xen Security Advisory 154 (CVE-2016-2270) - x86: inconsistent cachability flags on guest mappings David Woodhouse
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=AADFC41AFE54684AB9EE6CBC0274A5D190CAAEC7@SHSMSX101.ccr.corp.intel.com \
--to=kevin.tian@intel.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=dwmw2@infradead.org \
--cc=h.peter.anvin@intel.com \
--cc=jun.nakajima@intel.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.org \
/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.