From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Aviv B.D." <bd.aviv@gmail.com>
Cc: Jason Wang <jasowang@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Alex Williamson <alex.williamson@redhat.com>,
qemu-devel@nongnu.org, Peter Xu <peterx@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 1/3] IOMMU: add option to enable VTD_CAP_CM to vIOMMU capility exposoed to guest
Date: Tue, 22 Nov 2016 17:13:15 +0200 [thread overview]
Message-ID: <20161122171021-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAM3WwMg6MD_UNGshxfUZsWQtUyaBZmS3QSOjJpDeZAfwq3z-jg@mail.gmail.com>
On Tue, Nov 22, 2016 at 03:15:45PM +0200, Aviv B.D. wrote:
> However, if you insist on this part I will add the relevant code...
I wouldn't bother at this point. Getting to a point where
we can merge it with vfio support seems more important.
--
MST
next prev parent reply other threads:[~2016-11-22 15:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 11:04 [Qemu-devel] [PATCH v6 0/3] IOMMU: intel_iommu support map and unmap notifications Aviv B.D
2016-11-08 11:04 ` [Qemu-devel] [PATCH v6 1/3] IOMMU: add option to enable VTD_CAP_CM to vIOMMU capility exposoed to guest Aviv B.D
2016-11-09 7:28 ` Jason Wang
2016-11-09 22:00 ` Michael S. Tsirkin
2016-11-11 2:32 ` Jason Wang
2016-11-11 3:39 ` Michael S. Tsirkin
2016-11-11 4:15 ` Jason Wang
2016-11-21 12:41 ` Aviv B.D.
2016-11-22 3:59 ` Jason Wang
2016-11-21 13:35 ` Michael S. Tsirkin
2016-11-22 4:11 ` Jason Wang
2016-11-22 13:15 ` Aviv B.D.
2016-11-22 15:13 ` Michael S. Tsirkin [this message]
2016-11-22 15:09 ` Michael S. Tsirkin
2016-12-01 3:02 ` Tian, Kevin
2016-11-08 11:04 ` [Qemu-devel] [PATCH v6 2/3] IOMMU: change iommu_op->translate's is_write to flags, add support to NO_FAIL flag mode Aviv B.D
2016-11-08 11:04 ` [Qemu-devel] [PATCH v6 3/3] IOMMU: enable intel_iommu map and unmap notifiers Aviv B.D
2016-11-10 15:13 ` Michael S. Tsirkin
2016-11-10 15:14 ` [Qemu-devel] [PATCH v6 0/3] IOMMU: intel_iommu support map and unmap notifications Michael S. Tsirkin
2016-11-10 15:30 ` Alex Williamson
2016-11-10 15:54 ` Michael S. Tsirkin
2016-11-10 16:04 ` Alex Williamson
2016-11-10 19:20 ` Michael S. Tsirkin
2016-11-10 19:44 ` Alex Williamson
2016-11-16 13:54 ` Michael S. Tsirkin
2016-11-16 15:34 ` Alex Williamson
2016-11-16 19:50 ` Aviv B.D.
2016-11-16 19:57 ` Michael S. Tsirkin
2016-11-21 11:36 ` Aviv B.D.
2016-11-16 20:03 ` Alex Williamson
2016-11-16 20:17 ` Michael S. Tsirkin
2016-11-16 19:20 ` Aviv B.D.
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=20161122171021-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=bd.aviv@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=jasowang@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.