From: Peter Xu <peterx@redhat.com>
To: Yi Sun <yi.y.sun@linux.intel.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, rth@twiddle.net,
ehabkost@redhat.com, mst@redhat.com, marcel.apfelbaum@gmail.com,
jasowang@redhat.com, kevin.tian@intel.com, yi.l.liu@intel.com,
yi.y.sun@intel.com
Subject: Re: [Qemu-devel] [PATCH v1 3/3] intel_iommu: add scalable-mode option to make scalable mode work
Date: Tue, 5 Mar 2019 11:07:04 +0800 [thread overview]
Message-ID: <20190305030704.GG1657@xz-x1> (raw)
In-Reply-To: <1551753295-30167-4-git-send-email-yi.y.sun@linux.intel.com>
On Tue, Mar 05, 2019 at 10:34:55AM +0800, Yi Sun wrote:
> This patch adds an option to provide flexibility for user to expose
> Scalable Mode to guest. User could expose Scalable Mode to guest by
> the config as below:
>
> "-device intel-iommu,caching-mode=on,scalable-mode=on"
>
> The Linux iommu driver has supported scalable mode. Please refer below
> patch set:
>
> https://www.spinics.net/lists/kernel/msg2985279.html
>
> Signed-off-by: Liu, Yi L <yi.l.liu@intel.com>
> Signed-off-by: Yi Sun <yi.y.sun@linux.intel.com>
> ---
> RFC v2->v1:
> - move 's->dma_drain' check from 'vtd_init' to 'vtd_decide_config'.
Reviewed-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
next prev parent reply other threads:[~2019-03-05 3:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 2:34 [Qemu-devel] [PATCH v1 0/3] intel_iommu: support scalable mode Yi Sun
2019-03-05 2:34 ` [Qemu-devel] [PATCH v1 1/3] intel_iommu: scalable mode emulation Yi Sun
2019-03-05 3:06 ` Peter Xu
2019-03-05 2:34 ` [Qemu-devel] [PATCH v1 2/3] intel_iommu: add 256 bits qi_desc support Yi Sun
2019-03-05 2:34 ` [Qemu-devel] [PATCH v1 3/3] intel_iommu: add scalable-mode option to make scalable mode work Yi Sun
2019-03-05 3:07 ` Peter Xu [this message]
2019-03-05 3:09 ` [Qemu-devel] [PATCH v1 0/3] intel_iommu: support scalable mode Peter Xu
2019-03-05 3:23 ` Michael S. Tsirkin
2019-03-05 3:24 ` Yi Sun
2019-03-05 4:48 ` Peter Xu
2019-03-05 5:15 ` Yi Sun
2019-03-05 5:36 ` Peter Xu
2019-03-05 6:27 ` Yi Sun
2019-03-05 6:39 ` Peter Xu
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=20190305030704.GG1657@xz-x1 \
--to=peterx@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jasowang@redhat.com \
--cc=kevin.tian@intel.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=yi.l.liu@intel.com \
--cc=yi.y.sun@intel.com \
--cc=yi.y.sun@linux.intel.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 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.