On Thu, Apr 25, 2019 at 01:29:17PM +0200, Auger Eric wrote:
> Hi,
> On 4/23/19 1:15 PM, Jean-Philippe Brucker wrote:
> > Hi,
> >
> > On 14/03/2019 15:32, Jean-Philippe Brucker wrote:
> >> The IOMMU device allows a guest to manage DMA mappings for physical,
> >> emulated and paravirtualized endpoints. Add device description for the
> >> virtio-iommu device and driver. Introduce PROBE, ATTACH, DETACH, MAP and
> >> UNMAP requests, as well as translation error reporting.
> >>
> >> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/37
> >> Signed-off-by: Jean-Philippe Brucker <>
> >
> > If there aren't any more comments on this version, could I request a
> > vote? The virtio-iommu spec has been reviewed on the virtio-dev list by
> > several of the people on Cc. The Linux driver has been in good shape for
> > a while, but Joerg would like to see progress on this specification
> > before merging it upstream. It's too late in the release cycle for Linux
> > v5.2, but I'm hoping to get something in v5.3.
> Is there any calendar for the "OASIS Virtual I/O Device (VIRTIO) TC" votes?
All active and past ballots are here:
https://www.oasis-open.org/committees/ballots.php?wg_abbrev=virtio
> I think the QEMU device
> > will follow the Linux driver since it depends on API headers.
> Yes sure I will respin the QEMU VIRTIO-IOMMU device accordingly.
>
> Thanks
>
> Eric
> >
> > Thanks,
> > Jean
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
