From: Alex Williamson <alex.williamson@redhat.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: iommu@lists.linux-foundation.org, chegu_vinod@hp.com,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 0/2] vfio: type1 iommu hugepage support
Date: Sat, 25 May 2013 08:39:53 -0600 [thread overview]
Message-ID: <1369492793.2646.164.camel@ul30vt.home> (raw)
In-Reply-To: <20130525112153.GD2418@localhost.localdomain>
On Sat, 2013-05-25 at 07:21 -0400, Konrad Rzeszutek Wilk wrote:
> On Fri, May 24, 2013 at 11:24:26AM -0600, Alex Williamson wrote:
> > This series let's the vfio type1 iommu backend take advantage of iommu
> > large page support. See patch 2/2 for the details. This has been
> > tested on both amd_iommu and intel_iommu, but only my AMD system has
> > large page support. I'd appreciate any testing and feedback on other
> > systems, particularly vt-d systems supporting large pages. Mapping
> > efficiency should be improved a bit without iommu hugepages, but I
> > hope that it's much more noticeable with huge pages, especially for
> > very large QEMU guests.
>
> I took a very very quick look - and I am wondering if there should also
> be a flag to turn it on/off in ther kernel in such case? Especially in the
> field if a user finds out that their particular IOMMU chipset might
> be doing something funky with large-pages ?
Yeah, that's probably a reasonable feature. intel-iommu has a boot
option to disable superpages, but we could make it more consistent at
the vfio level if we have a switch there. It could provided interesting
performance and debugging info. I'll add a module option to do this.
Thanks,
Alex
> > This change includes a clarification to the mapping expectations for
> > users of the type1 iommu, but is compatible with known users and works
> > with existing QEMU userspace supporting vfio. Thanks,
> >
> > Alex
> >
> > ---
> >
> > Alex Williamson (2):
> > vfio: Convert type1 iommu to use rbtree
> > vfio: hugepage support for vfio_iommu_type1
> >
> >
> > drivers/vfio/vfio_iommu_type1.c | 607 ++++++++++++++++++++++++---------------
> > include/uapi/linux/vfio.h | 8 -
> > 2 files changed, 387 insertions(+), 228 deletions(-)
> > _______________________________________________
> > iommu mailing list
> > iommu@lists.linux-foundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2013-05-25 14:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 17:24 [Qemu-devel] [PATCH 0/2] vfio: type1 iommu hugepage support Alex Williamson
2013-05-24 17:24 ` [Qemu-devel] [PATCH 1/2] vfio: Convert type1 iommu to use rbtree Alex Williamson
2013-05-24 17:24 ` [Qemu-devel] [PATCH 2/2] vfio: hugepage support for vfio_iommu_type1 Alex Williamson
2013-05-25 11:20 ` Konrad Rzeszutek Wilk
2013-05-25 14:23 ` Alex Williamson
2013-05-27 8:41 ` Sethi Varun-B16395
2013-05-27 13:37 ` Alex Williamson
2013-05-25 11:21 ` [Qemu-devel] [PATCH 0/2] vfio: type1 iommu hugepage support Konrad Rzeszutek Wilk
2013-05-25 14:39 ` Alex Williamson [this message]
2013-05-28 16:27 ` [Qemu-devel] [PATCH 3/2] vfio: Provide module option to disable vfio_iommu_type1 " Alex Williamson
2013-05-28 16:42 ` Konrad Rzeszutek Wilk
2013-05-31 2:33 ` Chegu Vinod
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=1369492793.2646.164.camel@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=chegu_vinod@hp.com \
--cc=iommu@lists.linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).