From: Oleksandr <olekstysh@gmail.com>
To: Julien Grall <julien@xen.org>
Cc: nd <nd@arm.com>, "Stefano Stabellini" <sstabellini@kernel.org>,
"Julien Grall" <julien.grall.oss@gmail.com>,
"Bertrand Marquis" <Bertrand.Marquis@arm.com>,
"Jan Beulich" <jbeulich@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"Rahul Singh" <Rahul.Singh@arm.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: RFC: PCI devices passthrough on Arm design proposal
Date: Mon, 20 Jul 2020 14:27:02 +0300 [thread overview]
Message-ID: <a9951d1d-d858-de65-284f-3b604ec102e1@gmail.com> (raw)
In-Reply-To: <2fd6c418-db41-8070-5644-344fefd8128d@xen.org>
On 18.07.20 14:24, Julien Grall wrote:
Hello Julien
>
>
> On 17/07/2020 20:17, Oleksandr wrote:
>> I would like to clarify regarding an IOMMU driver changes which
>> should be done to support PCI pass-through properly.
>>
>> Design document mentions about SMMU, but Xen also supports IPMMU-VMSA
>> (under tech preview now). It would be really nice if the required
>> support is extended to that kind of IOMMU as well.
>>
>> May I clarify what should be implemented in the Xen driver in order
>> to support PCI pass-through feature on Arm?
>
> I would expect callbacks to:
> - add a PCI device
> - remove a PCI device
> - assign a PCI device
> - deassign a PCI device
>
> AFAICT, they are already existing. So it is a matter of plumbing. This
> would then be up to the driver to configure the IOMMU correctly.
Got it.
>
>> Should the IOMMU H/W be "PCI-aware" for that purpose?
>
> The only requirement is that your PCI devices are behind an IOMMU :).
> Other than that the IOMMU can mostly be configured the same way as you
> would do for the non-PCI devices.
That's good.
> The main difference would be how you find the master ID.
>
> I am aware that on some platforms, the masterID may be shared between
> multiple PCI devices. In that case, we would need to have a way to
> assign all the devices to the same guest (maybe using group?).
Or just prevent these devices from being assigned to different guests?
During assigning a device to newly created guest check whether masterID
is already in use for any existing guests and deny operation in such a
case.
--
Regards,
Oleksandr Tyshchenko
next prev parent reply other threads:[~2020-07-20 11:27 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F6E40FB-79C5-4AE8-81CA-E16CA37BB298@arm.com>
[not found] ` <BD475825-10F6-4538-8294-931E370A602C@arm.com>
2020-07-16 17:10 ` RFC: PCI devices passthrough on Arm design proposal Rahul Singh
2020-07-16 20:51 ` Stefano Stabellini
2020-07-17 6:53 ` Bertrand Marquis
2020-07-17 7:41 ` Oleksandr Andrushchenko
2020-07-17 11:26 ` Julien Grall
2020-07-17 11:41 ` Oleksandr Andrushchenko
2020-07-17 13:21 ` Bertrand Marquis
2020-07-17 12:46 ` Rahul Singh
2020-07-17 12:55 ` Jan Beulich
2020-07-17 13:12 ` Bertrand Marquis
2020-07-17 8:10 ` Jan Beulich
2020-07-17 8:47 ` Oleksandr Andrushchenko
2020-07-17 13:28 ` Rahul Singh
2020-07-17 13:14 ` Bertrand Marquis
2020-07-17 13:19 ` Jan Beulich
2020-07-17 13:59 ` Bertrand Marquis
2020-07-17 14:06 ` Jan Beulich
2020-07-17 14:34 ` Bertrand Marquis
2020-07-17 14:41 ` Roger Pau Monné
2020-07-17 14:49 ` Bertrand Marquis
2020-07-17 15:05 ` Roger Pau Monné
2020-07-17 15:23 ` Bertrand Marquis
2020-07-17 15:30 ` Roger Pau Monné
2020-07-17 15:51 ` Bertrand Marquis
2020-07-17 16:08 ` Roger Pau Monné
2020-07-17 16:18 ` Julien Grall
2020-07-17 19:17 ` Oleksandr
2020-07-18 9:58 ` Bertrand Marquis
2020-07-18 11:24 ` Julien Grall
2020-07-20 11:27 ` Oleksandr [this message]
2020-07-20 8:47 ` Roger Pau Monné
2020-07-20 9:24 ` Julien Grall
2020-07-20 23:23 ` Stefano Stabellini
2020-07-21 9:54 ` Rahul Singh
2020-07-17 11:16 ` Roger Pau Monné
2020-07-17 13:22 ` Bertrand Marquis
2020-07-17 13:29 ` Julien Grall
2020-07-17 13:44 ` Bertrand Marquis
2020-07-17 13:49 ` Julien Grall
2020-07-17 14:01 ` Bertrand Marquis
2020-07-17 14:31 ` Roger Pau Monné
2020-07-17 15:21 ` Bertrand Marquis
2020-07-17 15:55 ` Roger Pau Monné
2020-07-18 9:49 ` Bertrand Marquis
2020-07-20 8:45 ` Roger Pau Monné
2020-07-20 23:24 ` Stefano Stabellini
2020-07-21 1:39 ` Rob Herring
2020-07-21 19:35 ` Stefano Stabellini
[not found] ` <8ac91a1b-e6b3-0f2b-0f23-d7aff100936d@xen.org>
2020-07-17 13:50 ` Julien Grall
2020-07-17 13:59 ` Jan Beulich
2020-07-17 14:12 ` Julien Grall
2020-07-17 14:23 ` Jan Beulich
2020-07-17 14:47 ` Bertrand Marquis
2020-07-17 15:26 ` Julien Grall
2020-07-17 15:47 ` Bertrand Marquis
2020-07-17 16:05 ` Roger Pau Monné
2020-07-18 9:55 ` Bertrand Marquis
2020-07-18 11:14 ` Julien Grall
2020-07-20 11:32 ` Rahul Singh
2020-07-18 11:32 ` Julien Grall
2020-07-18 11:08 ` Julien Grall
2020-07-20 11:26 ` Rahul Singh
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=a9951d1d-d858-de65-284f-3b604ec102e1@gmail.com \
--to=olekstysh@gmail.com \
--cc=Bertrand.Marquis@arm.com \
--cc=Rahul.Singh@arm.com \
--cc=jbeulich@suse.com \
--cc=julien.grall.oss@gmail.com \
--cc=julien@xen.org \
--cc=nd@arm.com \
--cc=roger.pau@citrix.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.