From: Auger Eric <eric.auger@redhat.com>
To: Peter Xu <peterx@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 v13 00/10] VIRTIO-IOMMU device
Date: Mon, 3 Feb 2020 14:51:37 +0100 [thread overview]
Message-ID: <08c5cf5a-18b6-d001-c470-709ec2190730@redhat.com> (raw)
In-Reply-To: <20200203134954.GB155875@xz-x1>
Hi Peter,
On 2/3/20 2:49 PM, Peter Xu wrote:
> On Mon, Feb 03, 2020 at 01:58:04PM +0100, Auger Eric wrote:
>> Hi,
>>
>> On 1/25/20 6:19 PM, Eric Auger wrote:
>>> This series implements the QEMU virtio-iommu device.
>>>
>>> This matches the v0.12 spec (voted) and the corresponding
>>> virtio-iommu driver upstreamed in 5.3. All kernel dependencies
>>> are resolved for DT integration. The virtio-iommu can be
>>> instantiated in ARM virt using "-device virtio-iommu-pci".
>>>
>>> Non DT mode is not yet supported as it has non resolved kernel
>>> dependencies [1].
>>>
>>> This feature targets 5.0.
>> If possible I would like to make this feature upstream in 5.0. Do you
>> guys have other comments/objections?
>
> Hi, Eric, Sorry that I forgot to read the series after a long PTO.
>
> I'll do it today.
No worries ;-)
Thank you in advance
Eric
>
prev parent reply other threads:[~2020-02-03 13:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 17:19 [PATCH v13 00/10] VIRTIO-IOMMU device Eric Auger
2020-01-25 17:19 ` [PATCH v13 01/10] virtio-iommu: Add skeleton Eric Auger
2020-01-25 17:19 ` [PATCH v13 02/10] virtio-iommu: Decode the command payload Eric Auger
2020-01-25 17:19 ` [PATCH v13 03/10] virtio-iommu: Implement attach/detach command Eric Auger
2020-02-03 13:49 ` Peter Xu
2020-02-03 14:59 ` Auger Eric
2020-02-03 15:19 ` Peter Xu
2020-02-03 17:46 ` Auger Eric
2020-02-03 18:19 ` Peter Xu
2020-02-04 12:26 ` Auger Eric
2020-01-25 17:19 ` [PATCH v13 04/10] virtio-iommu: Implement map/unmap Eric Auger
2020-01-25 17:19 ` [PATCH v13 05/10] virtio-iommu: Implement translate Eric Auger
2020-01-25 17:19 ` [PATCH v13 06/10] virtio-iommu: Implement fault reporting Eric Auger
2020-02-03 13:55 ` Peter Xu
2020-02-03 15:01 ` Auger Eric
2020-01-25 17:19 ` [PATCH v13 07/10] virtio-iommu-pci: Add virtio iommu pci support Eric Auger
2020-02-03 13:03 ` Michael S. Tsirkin
2020-02-03 13:20 ` Auger Eric
2020-02-03 13:28 ` Michael S. Tsirkin
2020-02-03 13:38 ` Auger Eric
2020-02-03 13:46 ` Michael S. Tsirkin
2020-02-03 13:52 ` Auger Eric
2020-01-25 17:19 ` [PATCH v13 08/10] hw/arm/virt: Add the virtio-iommu device tree mappings Eric Auger
2020-01-25 17:19 ` [PATCH v13 09/10] virtio-iommu: Support migration Eric Auger
2020-01-25 17:19 ` [PATCH v13 10/10] tests: Add virtio-iommu test Eric Auger
2020-02-03 12:58 ` [PATCH v13 00/10] VIRTIO-IOMMU device Auger Eric
2020-02-03 13:49 ` Peter Xu
2020-02-03 13:51 ` Auger Eric [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=08c5cf5a-18b6-d001-c470-709ec2190730@redhat.com \
--to=eric.auger@redhat.com \
--cc=bharatb.linux@gmail.com \
--cc=dgilbert@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=jean-philippe@linaro.org \
--cc=kevin.tian@intel.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--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).