Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
Cc: virtio-comment@lists.oasis-open.org,
	virtio-dev@lists.oasis-open.org, joro@8bytes.org,
	tnowicki@caviumnetworks.com, eric.auger@redhat.com,
	kevin.tian@intel.com, lorenzo.pieralisi@arm.com,
	bharat.bhushan@nxp.com, bauerman@linux.ibm.com
Subject: Re: [virtio-comment] Re: [virtio-dev] [PATCH v2] Add virtio-iommu device specification
Date: Tue, 30 Apr 2019 08:40:17 -0400	[thread overview]
Message-ID: <20190430083952-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <9ff6957a-b7bc-27e8-a7d1-cf9e3c956aa1@arm.com>

On Tue, Apr 23, 2019 at 12:15:59PM +0100, 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 <jean-philippe.brucker@arm.com>
> 
> If there aren't any more comments on this version, could I request a
> vote?

Ballot created: https://www.oasis-open.org/committees/ballot.php?id=3386




> 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. I think the QEMU device
> will follow the Linux driver since it depends on API headers.
> 
> Thanks,
> Jean
> 
> This publicly archived list offers a means to provide input to the
> OASIS Virtual I/O Device (VIRTIO) TC.
> 
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
> 
> Subscribe: virtio-comment-subscribe@lists.oasis-open.org
> Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
> List help: virtio-comment-help@lists.oasis-open.org
> List archive: https://lists.oasis-open.org/archives/virtio-comment/
> Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
> List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
> Committee: https://www.oasis-open.org/committees/virtio/
> Join OASIS: https://www.oasis-open.org/join/

This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/


      parent reply	other threads:[~2019-04-30 12:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14 15:32 [virtio-comment] [PATCH v2] Add virtio-iommu device specification Jean-Philippe Brucker
2019-04-23 11:15 ` [virtio-comment] Re: [virtio-dev] " Jean-Philippe Brucker
2019-04-25 11:29   ` Auger Eric
2019-04-30 12:41     ` [virtio-comment] " Michael S. Tsirkin
2019-04-30 12:45     ` Michael S. Tsirkin
2019-04-30 13:40       ` Jean-Philippe Brucker
2019-04-30 12:40   ` Michael S. Tsirkin [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=20190430083952-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=bauerman@linux.ibm.com \
    --cc=bharat.bhushan@nxp.com \
    --cc=eric.auger@redhat.com \
    --cc=jean-philippe.brucker@arm.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=tnowicki@caviumnetworks.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.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