qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, tianyu.lan@intel.com,
	kevin.tian@intel.com, jan.kiszka@siemens.com,
	jasowang@redhat.com, alex.williamson@redhat.com,
	bd.aviv@gmail.com
Subject: Re: [Qemu-devel] [PATCH v5 00/18] VT-d: vfio enablement and misc enhances
Date: Tue, 24 Jan 2017 16:48:49 +0200	[thread overview]
Message-ID: <20170124164751-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20170124114910.GD16400@pxdev.xzpeter.org>

On Tue, Jan 24, 2017 at 07:49:10PM +0800, Peter Xu wrote:
> On Tue, Jan 24, 2017 at 06:25:53PM +0800, Peter Xu wrote:
> > This is v5 of vt-d vfio enablement series.
> > 
> > Most of the changes in v5 is not functionally, but related to
> > comments, error_report()s, debugging, squashing patches, etc. (which
> > are confirmed changes in v4), besides a tiny tweak when unmapping a
> > whole address space (please see below changelog). There are still
> > discussions in v4 thread, we can just continue there (or here), and
> > from this version I'll remove RFC tag.
> > 
> > I didn't rebase to master since current master failed to build on my
> > laptop (with a "vl.c/hax..." error), however this series should be
> > okay to be applied cleanly upon it.
> 
> Sorry I forgot to append the todo list (please help adding in in case
> I missed anything):
> 
> - don't need to notify IOTLB (psi/gsi/global) invalidations to devices
>   that with ATS enabled
> - investigate when guest map page while mask contains existing mapped
>   pages (e.g. map 12k-16k first, then map 0-12k)
> - coalesce unmap during page walk (currently, we send it once per
>   page)
> - when do PSI for unmap, whether we can send one notify directly
>   instead of walking over the page table?
> 
> Above does not contain those that are still during discussion. And,
> some of the entries still need tests to further prove it's
> feasibility.
> 
> Thanks,
> 
> -- peterx

While valid I don't think above need to block merging.

-- 
MST

  reply	other threads:[~2017-01-24 14:48 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-24 10:25 [Qemu-devel] [PATCH v5 00/18] VT-d: vfio enablement and misc enhances Peter Xu
2017-01-24 10:25 ` [Qemu-devel] [PATCH v5 01/18] vfio: trace map/unmap for notify as well Peter Xu
2017-01-24 10:25 ` [Qemu-devel] [PATCH v5 02/18] vfio: introduce vfio_get_vaddr() Peter Xu
2017-01-24 16:29   ` Alex Williamson
2017-01-25  4:32     ` Peter Xu
2017-01-25 16:43       ` Alex Williamson
2017-01-25 17:16         ` Paolo Bonzini
2017-01-26  6:26           ` Peter Xu
2017-01-25 17:11     ` Paolo Bonzini
2017-01-25 17:36       ` Alex Williamson
2017-01-25 17:40         ` Paolo Bonzini
2017-01-25 18:36           ` Alex Williamson
2017-01-25 19:42             ` Paolo Bonzini
2017-01-25 20:09               ` Alex Williamson
2017-01-26  6:46                 ` Peter Xu
2017-01-26  7:12       ` Peter Xu
2017-01-26 10:55         ` Paolo Bonzini
2017-01-26 12:01           ` Peter Xu
2017-01-24 10:25 ` [Qemu-devel] [PATCH v5 03/18] vfio: allow to notify unmap for very large region Peter Xu
2017-01-24 16:32   ` Alex Williamson
2017-01-31  3:35     ` David Gibson
2017-02-03  7:30       ` Peter Xu
2017-01-24 10:25 ` [Qemu-devel] [PATCH v5 04/18] intel_iommu: add "caching-mode" option Peter Xu
2017-01-24 10:25 ` [Qemu-devel] [PATCH v5 05/18] intel_iommu: simplify irq region translation Peter Xu
2017-01-24 10:25 ` [Qemu-devel] [PATCH v5 06/18] intel_iommu: renaming gpa to iova where proper Peter Xu
2017-01-24 10:26 ` [Qemu-devel] [PATCH v5 07/18] intel_iommu: fix trace for inv desc handling Peter Xu
2017-01-24 10:26 ` [Qemu-devel] [PATCH v5 08/18] intel_iommu: fix trace for addr translation Peter Xu
2017-01-24 10:26 ` [Qemu-devel] [PATCH v5 09/18] intel_iommu: vtd_slpt_level_shift check level Peter Xu
2017-01-24 10:26 ` [Qemu-devel] [PATCH v5 10/18] memory: add section range info for IOMMU notifier Peter Xu
2017-01-24 10:26 ` [Qemu-devel] [PATCH v5 11/18] memory: provide IOMMU_NOTIFIER_FOREACH macro Peter Xu
2017-01-24 10:26 ` [Qemu-devel] [PATCH v5 12/18] memory: provide iommu_replay_all() Peter Xu
2017-01-24 10:26 ` [Qemu-devel] [PATCH v5 13/18] memory: introduce memory_region_notify_one() Peter Xu
2017-01-24 10:26 ` [Qemu-devel] [PATCH v5 14/18] memory: add MemoryRegionIOMMUOps.replay() callback Peter Xu
2017-01-24 10:26 ` [Qemu-devel] [PATCH v5 15/18] intel_iommu: provide its own replay() callback Peter Xu
2017-01-24 10:26 ` [Qemu-devel] [PATCH v5 16/18] intel_iommu: do replay when context invalidate Peter Xu
2017-01-24 10:26 ` [Qemu-devel] [PATCH v5 17/18] intel_iommu: allow dynamic switch of IOMMU region Peter Xu
2017-01-24 10:26 ` [Qemu-devel] [PATCH v5 18/18] intel_iommu: enable vfio devices Peter Xu
2017-01-24 11:49 ` [Qemu-devel] [PATCH v5 00/18] VT-d: vfio enablement and misc enhances Peter Xu
2017-01-24 14:48   ` Michael S. Tsirkin [this message]
2017-01-25  4:48     ` Peter Xu
2017-01-25 14:26       ` Michael S. Tsirkin
2017-01-26  7:16         ` 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=20170124164751-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=kevin.tian@intel.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tianyu.lan@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 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).