From: Juergen Gross <jgross@suse.com>
To: Oleksandr Tyshchenko <olekstysh@gmail.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Cc: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH] xen/virtio: Handle PCI devices which Host controller is described in DT
Date: Fri, 7 Oct 2022 07:57:13 +0200 [thread overview]
Message-ID: <014e7036-5daf-6465-663c-b690d6f719ee@suse.com> (raw)
In-Reply-To: <20221006174804.2003029-1-olekstysh@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1072 bytes --]
On 06.10.22 19:48, Oleksandr Tyshchenko wrote:
> From: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
>
> Use the same "xen-grant-dma" device concept (based on generic IOMMU
> device-tree bindings) for the PCI devices behind device-tree based
> PCI Host controller.
>
> Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
> ---
> Slightly RFC. This is needed to support Xen grant mappings for virtio-pci devices
> on Arm at some point in the future. The Xen toolstack side is not published yet.
> Here, for PCI devices we use the same way to pass backend domid to the guest as for
> platform devices.
I should mention we decided at the Xen Summit, that I will start a try to
modify the virtio spec to include the backend id (domid in the Xen case)
in the device independent config part.
As this will take some time to be accepted (if ever), other means to
specify the backend domid are needed until then. DT is one possibility
(at least on Arm), while Xenstore is the way to go for setups with a
Xen toolstack.
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3149 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2022-10-07 5:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 17:48 [PATCH] xen/virtio: Handle PCI devices which Host controller is described in DT Oleksandr Tyshchenko
2022-10-07 1:14 ` Stefano Stabellini
2022-10-12 20:26 ` Oleksandr Tyshchenko
2022-10-13 0:33 ` Stefano Stabellini
2022-10-15 15:47 ` Oleksandr Tyshchenko
2022-10-17 20:39 ` Stefano Stabellini
2022-10-19 13:34 ` Oleksandr Tyshchenko
2022-10-19 20:38 ` Stefano Stabellini
2022-10-20 18:01 ` Oleksandr Tyshchenko
2022-10-07 5:57 ` Juergen Gross [this message]
2022-10-07 20:24 ` Stefano Stabellini
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=014e7036-5daf-6465-663c-b690d6f719ee@suse.com \
--to=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_tyshchenko@epam.com \
--cc=olekstysh@gmail.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 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).