From: Oleksandr Tyshchenko <olekstysh@gmail.com>
To: "Orzel, Michal" <michal.orzel@amd.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Tyshchenko <Oleksandr_Tyshchenko@epam.com>,
Julien Grall <julien@xen.org>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Re: [PATCH] xen/public: arch-arm: Drop XEN_DMOP_get_ioreq_server_info from supported
Date: Tue, 2 Sep 2025 11:08:24 +0300 [thread overview]
Message-ID: <da4e48f0-12d8-4e85-8693-42d64440aa8b@gmail.com> (raw)
In-Reply-To: <5d670f97-5e04-45b8-b9ad-81e42706bc47@amd.com>
On 02.09.25 10:27, Orzel, Michal wrote:
Hello Michal
>
>
> On 01/09/2025 14:58, Oleksandr Tyshchenko wrote:
>> The said sub-op is not supported on Arm64, since it:
>> - does not support the buffered emulation (so bufioreq_port/bufioreq_gfn
>> cannot be returned), please refer to ioreq_server_create()
>> - does not support "legacy" mechanism of mapping IOREQ Server
>> magic pages (so ioreq_gfn/bufioreq_gfn cannot be returned), please
>> refer to arch_ioreq_server_map_pages(). On Arm64, only the Acquire
>> Resource infrastructure is used to query and map the IOREQ Server pages.
> These points are valid. However, I don't understand why you mention Arm64 only.
> What about Arm32? It's the same here.>
I will s/Arm64/Arm
>> Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
>> ---
>> xen/include/public/arch-arm.h | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/xen/include/public/arch-arm.h b/xen/include/public/arch-arm.h
>> index e2412a1747..023cc2f468 100644
>> --- a/xen/include/public/arch-arm.h
>> +++ b/xen/include/public/arch-arm.h
>> @@ -130,7 +130,6 @@
>> * HYPERVISOR_dm_op
>> * Exactly these sub-operations are supported:
>> * * XEN_DMOP_create_ioreq_server
>> - * * XEN_DMOP_get_ioreq_server_info
>> * * XEN_DMOP_map_io_range_to_ioreq_server
>> * * XEN_DMOP_unmap_io_range_from_ioreq_server
>> * * XEN_DMOP_set_ioreq_server_state
> This list is kept in sync with the op_size array in xen/arch/arm/dm.c.
> I think we should drop this op from there, not only from the comment listing
> supported ops.
I think you are right, will do
>
> ~Michal
>
>
>
prev parent reply other threads:[~2025-09-02 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 12:58 [PATCH] xen/public: arch-arm: Drop XEN_DMOP_get_ioreq_server_info from supported Oleksandr Tyshchenko
2025-09-02 7:27 ` Orzel, Michal
2025-09-02 8:08 ` Oleksandr Tyshchenko [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=da4e48f0-12d8-4e85-8693-42d64440aa8b@gmail.com \
--to=olekstysh@gmail.com \
--cc=Oleksandr_Tyshchenko@epam.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=bertrand.marquis@arm.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=sstabellini@kernel.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.