From: David Woodhouse <dwmw2@infradead.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
"H. Peter Anvin" <h.peter.anvin@intel.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH] x86: Allow write-combining on MMIO mappings again
Date: Thu, 26 Jan 2017 10:55:58 +0000 [thread overview]
Message-ID: <1485428158.4727.176.camel@infradead.org> (raw)
In-Reply-To: <5889E1690200007800134264@prv-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 519 bytes --]
On Thu, 2017-01-26 at 03:45 -0700, Jan Beulich wrote:
>
> This is too broad a statement: MMIO pages for which mfn_valid()
> is true would still allow WC use.
... where mfn_valid() would be true for MMIO regions in the low memory
hole, but not for regions above all physical memory?
> The only other issue with the patch that I can see is that you need
> to eliminate all the hard tabs you're introducing.
Bad emacs; no biscuit. I shall teach it that we're not in Kansas any
more, and repost. Thanks.
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 4938 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-26 10:55 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 [this message]
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
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=1485428158.4727.176.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=h.peter.anvin@intel.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.