From: Peter Xu <peterx@redhat.com>
To: Eric Auger <eric.auger@redhat.com>
Cc: peter.maydell@linaro.org, kevin.tian@intel.com,
tnowicki@marvell.com, jean-philippe@linaro.org,
quintela@redhat.com, qemu-devel@nongnu.org, dgilbert@redhat.com,
bharatb.linux@gmail.com, qemu-arm@nongnu.org, mst@redhat.com,
eric.auger.pro@gmail.com
Subject: Re: [PATCH v15 3/9] virtio-iommu: Implement attach/detach command
Date: Sat, 8 Feb 2020 08:41:54 -0500 [thread overview]
Message-ID: <20200208134154.GD823968@xz-x1> (raw)
In-Reply-To: <20200208120022.1920-4-eric.auger@redhat.com>
On Sat, Feb 08, 2020 at 01:00:16PM +0100, Eric Auger wrote:
> This patch implements the endpoint attach/detach to/from
> a domain.
>
> Domain and endpoint internal datatypes are introduced.
> Both are stored in RB trees. The domain owns a list of
> endpoints attached to it. Also helpers to get/put
> end points and domains are introduced.
>
> As for the IOMMU memory regions, a callback is called on
> PCI bus enumeration that initializes for a given device
> on the bus hierarchy an IOMMU memory region. The PCI bus
> hierarchy is stored locally in IOMMUPciBus and IOMMUDevice
> objects.
>
> At the time of the enumeration, the bus number may not be
> computed yet.
>
> So operations that will need to retrieve the IOMMUdevice
> and its IOMMU memory region from the bus number and devfn,
> once the bus number is garanteed to be frozen, use an array
> of IOMMUPciBus, lazily populated.
>
> Signed-off-by: Eric Auger <eric.auger@redhat.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
(Hope this is the last one missing r-b besides patch 8, I'll leave
patch 8 for the others or Michael when merging)
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2020-02-08 13:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 12:00 [PATCH v15 0/9] VIRTIO-IOMMU device Eric Auger
2020-02-08 12:00 ` [PATCH v15 1/9] virtio-iommu: Add skeleton Eric Auger
2020-02-08 12:00 ` [PATCH v15 2/9] virtio-iommu: Decode the command payload Eric Auger
2020-02-08 12:00 ` [PATCH v15 3/9] virtio-iommu: Implement attach/detach command Eric Auger
2020-02-08 13:41 ` Peter Xu [this message]
2020-02-08 14:00 ` Auger Eric
2020-02-08 12:00 ` [PATCH v15 4/9] virtio-iommu: Implement map/unmap Eric Auger
2020-02-08 12:00 ` [PATCH v15 5/9] virtio-iommu: Implement translate Eric Auger
2020-02-08 12:00 ` [PATCH v15 6/9] virtio-iommu: Implement fault reporting Eric Auger
2020-02-08 12:00 ` [PATCH v15 7/9] virtio-iommu-pci: Add virtio iommu pci support Eric Auger
2020-02-08 12:00 ` [PATCH v15 8/9] hw/arm/virt: Add the virtio-iommu device tree mappings Eric Auger
2020-02-11 15:00 ` Peter Maydell
2020-02-11 17:31 ` Auger Eric
2020-02-13 13:45 ` Auger Eric
2020-02-08 12:00 ` [PATCH v15 9/9] virtio-iommu: Support migration Eric Auger
2020-02-10 16:45 ` Juan Quintela
2020-02-11 13:56 ` [PATCH v15 0/9] VIRTIO-IOMMU device Michael S. Tsirkin
2020-02-11 15:02 ` Peter Maydell
2020-02-11 16:30 ` Michael S. Tsirkin
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=20200208134154.GD823968@xz-x1 \
--to=peterx@redhat.com \
--cc=bharatb.linux@gmail.com \
--cc=dgilbert@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=kevin.tian@intel.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=tnowicki@marvell.com \
/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).