From: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
To: virtio-dev@lists.oasis-open.org,
virtualization@lists.linux-foundation.org
Cc: eric.auger@redhat.com, eric.auger.pro@gmail.com
Subject: [RFC] virtio-iommu version 0.6
Date: Tue, 6 Feb 2018 18:11:06 +0000 [thread overview]
Message-ID: <20180206181106.21815-1-jean-philippe.brucker@arm.com> (raw)
Please find version 0.6 of the virtio-iommu specification at the following
locations.
Document: http://jpbrucker.net/virtio-iommu/spec/virtio-iommu.pdf
http://jpbrucker.net/virtio-iommu/spec/virtio-iommu.html
Sources: git://linux-arm.org/virtio-iommu.git viommu/v0.6
I didn't receive any comment for v0.5 [1], so this update is fairly light:
* Changed range definition in map and unmap requests
* Use virtio-iommu device ID
* Update IORT node ID and simplify layout
The following document shows the difference between v0.5 and v0.6:
http://jpbrucker.net/virtio-iommu/spec/diffs/virtio-iommu-pdf-diff-v0.5-v0.6.pdf
Next version will hopefully add vSVA (PASID+PRI) and/or architectural
optimizations, but I can't provide a timeline yet. I'll probably send a
small draft first.
I will send the Linux driver soon. In the meantime you can fetch it on my
development branches, based on next-20180206.
git://linux-arm.org/linux-jpb.git virtio-iommu/devel
git://linux-arm.org/kvmtool-jpb.git virtio-iommu/devel
Any comments welcome!
Thanks,
Jean
[1] https://www.spinics.net/lists/kvm/msg157402.html
next reply other threads:[~2018-02-06 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 18:11 Jean-Philippe Brucker [this message]
2018-03-19 10:03 ` [virtio-dev] [RFC] virtio-iommu version 0.6 Tian, Kevin
[not found] ` <AADFC41AFE54684AB9EE6CBC0274A5D191085A76@SHSMSX101.ccr.corp.intel.com>
2018-03-21 13:13 ` Jean-Philippe Brucker
2018-03-22 9:44 ` Tian, Kevin
2018-04-10 16:18 ` Jean-Philippe Brucker
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=20180206181106.21815-1-jean-philippe.brucker@arm.com \
--to=jean-philippe.brucker@arm.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.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