From: George Dunlap <George.Dunlap@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>, Wei Liu <wl@xen.org>,
Roger Pau Monne <roger.pau@citrix.com>,
"Tim (Xen.org)" <tim@xen.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: Ping: [PATCH 0/2] x86/P2M: allow 2M superpage use for shadowed guests
Date: Thu, 23 Jun 2022 12:28:03 +0000 [thread overview]
Message-ID: <F9BEFBCF-F4E3-43C4-9BF9-87E5FA36637E@citrix.com> (raw)
In-Reply-To: <5a8a8f01-03cb-b84a-bbca-9c5f6d2ea9cc@suse.com>
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
> On 23 Jun 2022, at 13:00, Jan Beulich <jbeulich@suse.com> wrote:
>
> On 09.12.2021 12:25, Jan Beulich wrote:
>> I did notice this anomaly in the context of IOMMU side work.
>>
>> 1: shadow: slightly consolidate sh_unshadow_for_p2m_change()
>> 2: P2M: allow 2M superpage use for shadowed guests
>
> This has been pending for over half a year. Anyone?
I can put it on a list of things to look at tomorrow.
-George
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-06-23 12:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 11:25 [PATCH 0/2] x86/P2M: allow 2M superpage use for shadowed guests Jan Beulich
2021-12-09 11:26 ` [PATCH 1/2] x86/shadow: slightly consolidate sh_unshadow_for_p2m_change() Jan Beulich
2022-06-24 19:16 ` George Dunlap
2022-06-27 6:26 ` Jan Beulich
2021-12-09 11:27 ` [PATCH 2/2] x86/P2M: allow 2M superpage use for shadowed guests Jan Beulich
2022-06-24 19:27 ` George Dunlap
2022-06-27 6:33 ` Jan Beulich
2022-07-18 5:42 ` George Dunlap
2022-06-23 12:00 ` Ping: [PATCH 0/2] " Jan Beulich
2022-06-23 12:28 ` George Dunlap [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=F9BEFBCF-F4E3-43C4-9BF9-87E5FA36637E@citrix.com \
--to=george.dunlap@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=tim@xen.org \
--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 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.