From: Jan Beulich <jbeulich@suse.com>
To: paul@xen.org
Cc: xen-devel@lists.xenproject.org,
'Paul Durrant' <Paul.Durrant@citrix.com>,
'Roger Pau Monne' <roger.pau@citrix.com>, 'Wei Liu' <wl@xen.org>,
'Andrew Cooper' <andrew.cooper3@citrix.com>
Subject: Re: [Xen-devel] [PATCH v5 05/10] x86emul: support MOVDIR64B insn
Date: Wed, 25 Mar 2020 12:46:44 +0100 [thread overview]
Message-ID: <1cc4b223-42c4-1c3b-98fb-d43cda1c47bf@suse.com> (raw)
In-Reply-To: <00c301d60297$471cb7f0$d55627d0$@xen.org>
On 25.03.2020 12:19, Paul Durrant wrote:
>> -----Original Message-----
>> From: Xen-devel <xen-devel-bounces@lists.xenproject.org> On Behalf Of Jan Beulich
>> Sent: 24 March 2020 12:34
>> To: xen-devel@lists.xenproject.org
>> Cc: Andrew Cooper <andrew.cooper3@citrix.com>; Paul Durrant <Paul.Durrant@citrix.com>; Wei Liu
>> <wl@xen.org>; Roger Pau Monne <roger.pau@citrix.com>
>> Subject: [Xen-devel] [PATCH v5 05/10] x86emul: support MOVDIR64B insn
>>
>> Introduce a new blk() hook, paralleling the rmw() on in certain way, but
>> being intended for larger data sizes, and hence its HVM intermediate
>> handling function doesn't fall back to splitting the operation if the
>> requested virtual address can't be mapped.
>>
>> Note that SDM revision 071 doesn't specify exception behavior for
>> ModRM.mod == 0b11; assuming #UD here.
>>
>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>> ---
>> TBD: If we want to avoid depending on correct MTRR settings,
>> hvmemul_map_linear_addr() may need to gain a parameter to allow
>> controlling cachability of the produced mapping(s).
>
> Or could we deal with this by adding an optional cache flush into the unmap?
But (non-)cachability of a range can't generally by covered by
simply flushing the cache.
>> Of course the
>> function will also need to be made capable of mapping at least
>> p2m_mmio_direct pages for this and the two ENQCMD insns to be
>> actually useful.
>
>
> I/O emulation parts LGTM so...
>
> Reviewed-by: Paul Durrant <paul@xen.org>
Thanks much.
Jan
next prev parent reply other threads:[~2020-03-25 11:47 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 12:26 [Xen-devel] [PATCH v5 00/10] x86emul: further work Jan Beulich
2020-03-24 12:29 ` [Xen-devel] [PATCH v5 02/10] x86emul: support AVX512_BF16 insns Jan Beulich
2020-03-24 12:29 ` [Xen-devel] [PATCH v5 02/10] x86emul: support MOVDIRI insn Jan Beulich
2020-03-25 20:58 ` Andrew Cooper
2020-03-26 9:20 ` Jan Beulich
2020-03-24 12:30 ` [Xen-devel] [PATCH v5 01/10] x86emul: support AVX512_BF16 insns Jan Beulich
2020-03-25 20:02 ` Andrew Cooper
2020-03-27 18:20 ` Andrew Cooper
2020-03-30 6:40 ` Jan Beulich
2020-03-24 12:33 ` [Xen-devel] [PATCH v5 03/10] x86: determine HAVE_AS_* just once Jan Beulich
2020-03-25 21:12 ` Andrew Cooper
2020-03-26 9:50 ` Jan Beulich
2020-03-26 13:42 ` Anthony PERARD
2020-03-26 14:20 ` Jan Beulich
2020-04-09 12:24 ` Jan Beulich
2020-03-24 12:33 ` [Xen-devel] [PATCH v5 04/10] x86: move back clang no integrated assembler tests Jan Beulich
2020-03-24 12:34 ` [Xen-devel] [PATCH v5 05/10] x86emul: support MOVDIR64B insn Jan Beulich
2020-03-25 11:19 ` Paul Durrant
2020-03-25 11:46 ` Jan Beulich [this message]
2020-04-02 23:12 ` Andrew Cooper
2020-04-03 7:57 ` Jan Beulich
2020-04-03 15:13 ` Andrew Cooper
2020-04-03 15:25 ` Jan Beulich
2020-03-24 12:34 ` [Xen-devel] [PATCH v5 06/10] x86emul: support ENQCMD insn Jan Beulich
2020-03-24 12:35 ` [Xen-devel] [PATCH v5 07/10] x86/HVM: scale MPERF values reported to guests (on AMD) Jan Beulich
2020-03-24 12:36 ` [Xen-devel] [PATCH v5 08/10] x86emul: support RDPRU Jan Beulich
2020-03-24 12:37 ` [Xen-devel] [PATCH v5 09/10] x86/HVM: don't needlessly intercept APERF/MPERF/TSC MSR reads Jan Beulich
2020-03-27 2:24 ` Tian, Kevin
2020-03-24 12:37 ` [Xen-devel] [PATCH v5 10/10] x86emul: support MCOMMIT Jan Beulich
2020-04-02 23:47 ` Andrew Cooper
2020-04-03 8:00 ` Jan Beulich
2020-04-03 15:00 ` Andrew Cooper
2020-04-03 15:09 ` Jan Beulich
2020-04-03 15:25 ` Andrew Cooper
2020-03-24 12:43 ` [Xen-devel] [PATCH v5 00/10] x86emul: further work Jan Beulich
2020-03-25 10:59 ` Paul Durrant
2020-03-25 11:41 ` Andrew Cooper
2020-03-25 11:45 ` Jan Beulich
2020-03-26 11:49 ` 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=1cc4b223-42c4-1c3b-98fb-d43cda1c47bf@suse.com \
--to=jbeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=paul@xen.org \
--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).