From: Konrad Rzeszutek Wilk <konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Alex Williamson
<alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
chegu_vinod-VXdhtT5mjnY@public.gmane.org,
qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org,
kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/2] vfio: type1 iommu hugepage support
Date: Sat, 25 May 2013 07:21:54 -0400 [thread overview]
Message-ID: <20130525112153.GD2418@localhost.localdomain> (raw)
In-Reply-To: <20130524171613.14229.84050.stgit-xdHQ/5r00wBBDLzU/O5InQ@public.gmane.org>
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 ?
>
> 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-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Alex Williamson <alex.williamson@redhat.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: [PATCH 0/2] vfio: type1 iommu hugepage support
Date: Sat, 25 May 2013 07:21:54 -0400 [thread overview]
Message-ID: <20130525112153.GD2418@localhost.localdomain> (raw)
In-Reply-To: <20130524171613.14229.84050.stgit@bling.home>
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 ?
>
> 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
WARNING: multiple messages have this Message-ID (diff)
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Alex Williamson <alex.williamson@redhat.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 07:21:54 -0400 [thread overview]
Message-ID: <20130525112153.GD2418@localhost.localdomain> (raw)
In-Reply-To: <20130524171613.14229.84050.stgit@bling.home>
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 ?
>
> 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 11:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 17:24 [PATCH 0/2] vfio: type1 iommu hugepage support Alex Williamson
2013-05-24 17:24 ` [Qemu-devel] " Alex Williamson
2013-05-24 17:24 ` Alex Williamson
[not found] ` <20130524171613.14229.84050.stgit-xdHQ/5r00wBBDLzU/O5InQ@public.gmane.org>
2013-05-24 17:24 ` [PATCH 1/2] vfio: Convert type1 iommu to use rbtree Alex Williamson
2013-05-24 17:24 ` [Qemu-devel] " Alex Williamson
2013-05-24 17:24 ` Alex Williamson
2013-05-24 17:24 ` [PATCH 2/2] vfio: hugepage support for vfio_iommu_type1 Alex Williamson
2013-05-24 17:24 ` [Qemu-devel] " Alex Williamson
2013-05-24 17:24 ` Alex Williamson
[not found] ` <20130524172438.14229.59476.stgit-xdHQ/5r00wBBDLzU/O5InQ@public.gmane.org>
2013-05-25 11:20 ` Konrad Rzeszutek Wilk
2013-05-25 11:20 ` [Qemu-devel] " Konrad Rzeszutek Wilk
2013-05-25 11:20 ` Konrad Rzeszutek Wilk
[not found] ` <20130525112009.GC2418-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2013-05-25 14:23 ` Alex Williamson
2013-05-25 14:23 ` [Qemu-devel] " Alex Williamson
2013-05-25 14:23 ` Alex Williamson
2013-05-27 8:41 ` Sethi Varun-B16395
2013-05-27 8:41 ` [Qemu-devel] " Sethi Varun-B16395
2013-05-27 8:41 ` Sethi Varun-B16395
[not found] ` <C5ECD7A89D1DC44195F34B25E172658D552685-RL0Hj/+nBVDYdknt8GnhQq4g8xLGJsHaLnY5E4hWTkheoWH0uzbU5w@public.gmane.org>
2013-05-27 13:37 ` Alex Williamson
2013-05-27 13:37 ` [Qemu-devel] " Alex Williamson
2013-05-27 13:37 ` Alex Williamson
2013-05-25 11:21 ` Konrad Rzeszutek Wilk [this message]
2013-05-25 11:21 ` [Qemu-devel] [PATCH 0/2] vfio: type1 iommu hugepage support Konrad Rzeszutek Wilk
2013-05-25 11:21 ` Konrad Rzeszutek Wilk
[not found] ` <20130525112153.GD2418-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2013-05-25 14:39 ` Alex Williamson
2013-05-25 14:39 ` [Qemu-devel] " Alex Williamson
2013-05-25 14:39 ` Alex Williamson
2013-05-28 16:27 ` [PATCH 3/2] vfio: Provide module option to disable vfio_iommu_type1 " Alex Williamson
2013-05-28 16:27 ` [Qemu-devel] " Alex Williamson
2013-05-28 16:27 ` Alex Williamson
[not found] ` <20130528162637.28848.76733.stgit-xdHQ/5r00wBBDLzU/O5InQ@public.gmane.org>
2013-05-28 16:42 ` Konrad Rzeszutek Wilk
2013-05-28 16:42 ` [Qemu-devel] " Konrad Rzeszutek Wilk
2013-05-28 16:42 ` Konrad Rzeszutek Wilk
2013-05-31 2:33 ` Chegu Vinod
2013-05-31 2:33 ` [Qemu-devel] " Chegu Vinod
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=20130525112153.GD2418@localhost.localdomain \
--to=konrad.wilk-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=chegu_vinod-VXdhtT5mjnY@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.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.