From: Oleksii Kurochko <oleksii.kurochko@gmail.com>
To: Jan Beulich <jbeulich@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH partly-for-4.20 v3 0/4] x86/HVM: emulation (MMIO) improvements
Date: Thu, 23 Jan 2025 16:09:52 +0100 [thread overview]
Message-ID: <a8cb8a0d-9c44-4e1b-92f3-50928f03ebd2@gmail.com> (raw)
In-Reply-To: <729f7896-55b7-4b5b-a7e9-6eb0420e0b14@suse.com>
On 1/23/25 11:29 AM, Jan Beulich wrote:
> The main fix is patch 2, with the earlier patch setting the stage and
> the latter ones simplifying other things at least a little in exchange.
>
> 1: allocate emulation cache entries dynamically
> 2: correct read/write split at page boundaries
> 3: slightly improve CMPXCHG16B emulation
> 4: drop redundant access splitting
>
> Oleksii - the first two patches (plus the simple one from v2 that I just
> committed) are backporting material, and hence I'd like to ask for a
> release ack for at least those two.
R-Acked-by: Oleksii Kurochko <oleksii.kurochko@gmail.com> for first two
patches.
Thanks.
~ Oleksii
prev parent reply other threads:[~2025-01-23 15:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 10:29 [PATCH partly-for-4.20 v3 0/4] x86/HVM: emulation (MMIO) improvements Jan Beulich
2025-01-23 10:30 ` [PATCH for-4.20 v3 1/4] x86/HVM: allocate emulation cache entries dynamically Jan Beulich
2025-01-23 10:31 ` [PATCH for-4.20 v3 2/4] x86/HVM: correct read/write split at page boundaries Jan Beulich
2025-01-23 12:43 ` Roger Pau Monné
2025-01-23 10:31 ` [PATCH v3 3/4] x86/HVM: slightly improve CMPXCHG16B emulation Jan Beulich
2025-01-23 10:32 ` [PATCH v3 4/4] x86/HVM: drop redundant access splitting Jan Beulich
2025-01-23 15:09 ` Oleksii Kurochko [this message]
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=a8cb8a0d-9c44-4e1b-92f3-50928f03ebd2@gmail.com \
--to=oleksii.kurochko@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--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 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.