From: "Michael S. Tsirkin" <mst@redhat.com>
To: Will Deacon <will.deacon@arm.com>
Cc: virtualization@lists.linux-foundation.org
Subject: Re: VIRTIO_F_IOMMU_PLATFORM
Date: Mon, 10 Oct 2016 21:07:35 +0300 [thread overview]
Message-ID: <20161010210411-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20161010165903.GH14561@arm.com>
On Mon, Oct 10, 2016 at 05:59:03PM +0100, Will Deacon wrote:
> On Fri, Oct 07, 2016 at 07:24:34AM +0300, Michael S. Tsirkin wrote:
> > On Tue, Sep 27, 2016 at 09:57:14AM +0100, Will Deacon wrote:
> > > Hi Michael,
> > >
> > > In commit 1a937693993f ("virtio: new feature to detect IOMMU device quirk"),
> > > you added a new feature bit (VIRTIO_F_IOMMU_PLATFORM) to describe whether
> > > or not a given virtio device requires physical address or bus addresses.
> > >
> > > Is there a plan to get this incorporated into the virtio spec [1]? At the
> > > moment, I can't see a working draft that includes the new bit. Having it
> > > in the spec would help convince implementors that it's not just a Linux
> > > thing.
> > >
> > > Thanks,
> > >
> > > Will
> > >
> > > [1] http://docs.oasis-open.org/virtio/virtio/v1.0/cs04/virtio-v1.0-cs04.html
> >
> > Absolutely. Want to contribute a patch?
>
> I could have a look. Is there a git repo for the sources to the working
> draft?
>
> Will
Yes, though unfortunately it's svn :(
git svn clone --stdlayout https://tools.oasis-open.org/version-control/svn/virtio
Check out the main branch.
Patches must be sent to virtio-dev or virtio-comments list (subscription
required).
Thanks!
--
MST
next prev parent reply other threads:[~2016-10-10 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 8:57 VIRTIO_F_IOMMU_PLATFORM Will Deacon
2016-10-07 4:24 ` VIRTIO_F_IOMMU_PLATFORM Michael S. Tsirkin
2016-10-10 16:59 ` VIRTIO_F_IOMMU_PLATFORM Will Deacon
2016-10-10 18:07 ` Michael S. Tsirkin [this message]
2016-10-11 1:51 ` VIRTIO_F_IOMMU_PLATFORM 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=20161010210411-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=will.deacon@arm.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).