From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Paul Durrant <Paul.Durrant@citrix.com>, Wei Liu <wl@xen.org>,
RogerPau Monne <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH 1/6] x86emul: generalize wbinvd() hook
Date: Tue, 27 Aug 2019 13:51:02 +0100 [thread overview]
Message-ID: <f8712de9-7fb0-32d9-7c1b-b5cb85504eec@citrix.com> (raw)
In-Reply-To: <fc5f0b03-2e69-8fa9-289f-50e8abb57210@citrix.com>
On 27/08/2019 11:44, Andrew Cooper wrote:
>> I was also uncertain about the new cache_flush_permitted() instance -
>> generally I think it wouldn't be too bad if we allowed line flushes in
>> all cases, in which case the checks in the ->wbinvd_intercept() handlers
>> would suffice (as they did until now).
> This is a more general issue which we need to address. To support
> encrypted memory in VM's, we must guarantee that WC mappings which the
> guest creates are really WC, which means we must not use IPAT or play
> any "fall back to WB" games.
>
> Furthermore, AMD's encrypt-in-place algorithm requires the guest to be
> able to use WBINVD.
Apologies. AMD's algorithm requires aliased WP and WB mappings, not WC.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-08-27 12:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 11:47 [Xen-devel] [PATCH 0/6] x86emul: further work Jan Beulich
2019-07-01 11:56 ` [Xen-devel] [PATCH 1/6] x86emul: generalize wbinvd() hook Jan Beulich
2019-07-02 10:22 ` Paul Durrant
2019-07-02 10:50 ` Jan Beulich
2019-07-02 10:53 ` Paul Durrant
2019-08-27 10:44 ` Andrew Cooper
2019-08-27 12:51 ` Andrew Cooper [this message]
2019-08-27 18:47 ` Andrew Cooper
2019-09-02 11:10 ` [Xen-devel] Ping: " Jan Beulich
2019-09-02 12:04 ` Paul Durrant
2019-07-01 11:56 ` [Xen-devel] [PATCH 2/6] x86emul: support WBNOINVD Jan Beulich
2019-07-02 10:38 ` Paul Durrant
2019-08-27 14:47 ` Andrew Cooper
2019-08-27 15:08 ` Jan Beulich
2019-08-27 16:45 ` Andrew Cooper
2019-08-28 11:42 ` Andrew Cooper
2019-07-01 11:56 ` [Xen-devel] [PATCH 3/6] x86emul: generalize invlpg() hook Jan Beulich
2019-07-02 10:47 ` Paul Durrant
2019-08-27 14:55 ` Andrew Cooper
2019-07-01 11:57 ` [Xen-devel] [PATCH 4/6] x86: move INVPCID_TYPE_* to x86-defns.h Jan Beulich
2019-07-02 10:49 ` Paul Durrant
2019-08-27 14:57 ` Andrew Cooper
2019-07-01 11:57 ` [Xen-devel] [PATCH 5/6] x86emul: support INVPCID Jan Beulich
2019-07-02 12:54 ` Paul Durrant
2019-08-27 15:31 ` Andrew Cooper
2019-08-27 15:53 ` Jan Beulich
2019-08-27 17:27 ` Andrew Cooper
2019-08-28 7:14 ` Jan Beulich
2019-08-28 11:33 ` Andrew Cooper
2019-07-01 11:58 ` [Xen-devel] [PATCH 6/6] x86emul: support MOVDIR{I,64B} insns Jan Beulich
2019-08-27 16:04 ` Andrew Cooper
2019-08-28 6:26 ` Jan Beulich
2019-08-28 11:51 ` Andrew Cooper
2019-08-28 12:19 ` Jan Beulich
2019-08-15 14:24 ` [Xen-devel] [PATCH 0/6] x86emul: further work Andrew Cooper
2019-08-27 8:37 ` Jan Beulich
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=f8712de9-7fb0-32d9-7c1b-b5cb85504eec@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=roger.pau@citrix.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).