From: Jan Beulich <jbeulich@suse.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Ragiadakou, Xenia" <Xenia.Ragiadakou@amd.com>,
jason.andryuk@amd.com, agarciav@amd.com,
"Teddy Astie" <teddy.astie@vates.tech>
Subject: Re: [PATCH] xen/x86: allow Dom0 PVH to call XENMEM_exchange
Date: Tue, 29 Apr 2025 08:24:29 +0200 [thread overview]
Message-ID: <c9ed2626-6353-4e4e-add8-e06ffff54427@suse.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2504281300340.785180@ubuntu-linux-20-04-desktop>
On 28.04.2025 22:02, Stefano Stabellini wrote:
> On Mon, 28 Apr 2025, Teddy Astie wrote:
>> Hello Stefano,
>>
>> Le 25/04/2025 à 22:21, Stefano Stabellini a écrit :
>>> From: Xenia Ragiadakou <Xenia.Ragiadakou@amd.com>
>>>
>>> Dom0 PVH might need XENMEM_exchange when passing contiguous memory
>>> addresses to firmware or co-processors not behind an IOMMU.
>>>
>>> XENMEM_exchange was blocked for HVM/PVH DomUs, and accidentally it
>>> impacted Dom0 PVH as well.
>>>
>>> Permit Dom0 PVH to call XENMEM_exchange while leaving it blocked for
>>> HVM/PVH DomUs.
>>>
>>
>> In addition to Jan's remarks, I think it wants some additional
>> clarifications on the hypercall interface. public/memory.h indicates
>> "only PV guests can use this operation", so the interface is actually
>> unspecified about HVM guests (e.g what are MFN/GMFN in this case ?).
>
> That is a new addition from c08a11ab98c.
Later addition or not, I agree with Teddy that it wants amending.
Jan
> If you see fae7d5be8bb, there
> is a statement that "we permitted this operation".
prev parent reply other threads:[~2025-04-29 6:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 20:19 [PATCH] xen/x86: allow Dom0 PVH to call XENMEM_exchange Stefano Stabellini
2025-04-28 7:14 ` Jan Beulich
2025-04-28 20:00 ` Stefano Stabellini
2025-04-29 6:43 ` Jan Beulich
2025-04-29 21:52 ` Stefano Stabellini
2025-04-30 6:27 ` Jan Beulich
2025-04-30 7:41 ` Roger Pau Monné
2025-05-01 0:19 ` Stefano Stabellini
2025-05-01 13:44 ` Jason Andryuk
2025-05-02 7:19 ` Jan Beulich
2025-05-02 16:49 ` Stefano Stabellini
2025-05-05 7:57 ` Roger Pau Monné
2025-05-12 9:14 ` Jan Beulich
2025-05-05 10:40 ` Marek Marczykowski-Górecki
2025-05-05 14:30 ` Roger Pau Monné
2025-05-05 18:11 ` Stefano Stabellini
2025-05-05 20:36 ` Demi Marie Obenour
2025-05-06 8:54 ` Roger Pau Monné
2025-05-07 23:02 ` Stefano Stabellini
2025-05-08 9:12 ` Roger Pau Monné
2025-05-08 10:28 ` Marek Marczykowski-Górecki
2025-05-08 23:28 ` Stefano Stabellini
2025-05-08 23:25 ` Stefano Stabellini
2025-05-09 8:32 ` Roger Pau Monné
2025-05-09 21:10 ` Stefano Stabellini
2025-05-09 22:16 ` Teddy Astie
2025-05-09 22:31 ` Stefano Stabellini
2025-05-12 8:51 ` Roger Pau Monné
2025-05-12 9:24 ` Jan Beulich
2025-04-28 8:11 ` Teddy Astie
2025-04-28 20:02 ` Stefano Stabellini
2025-04-29 6:24 ` Jan Beulich [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=c9ed2626-6353-4e4e-add8-e06ffff54427@suse.com \
--to=jbeulich@suse.com \
--cc=Xenia.Ragiadakou@amd.com \
--cc=agarciav@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=jason.andryuk@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=teddy.astie@vates.tech \
--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.