From: Yan Zhao <yan.y.zhao@intel.com>
To: alex.williamson@redhat.com, zhenyuw@linux.intel.com
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
intel-gvt@eclists.intel.com, pbonzini@redhat.com,
kevin.tian@intel.com, Yan Zhao <yan.y.zhao@intel.com>
Subject: [PATCH 0/2] use vfio_iova_rw() to read/write IOVAs from CPU side
Date: Thu, 2 Jan 2020 20:00:55 -0500 [thread overview]
Message-ID: <20200103010055.4140-1-yan.y.zhao@intel.com> (raw)
When device models read/write memory pointed by a range of IOVAs, it is
better to use vfio interfaces. And because this read/write is from CPUs,
there's no need to call vfio_pin_pages() to pin those memory.
patch 1 introduces interface vfio_iova_rw() in vfio to read/write
userspace IOVAs without pinning userspace pages.
patch 2 let gvt switch from kvm side rw interface to vfio_iova_rw().
Yan Zhao (2):
vfio: introduce vfio_iova_rw to read/write a range of IOVAs
drm/i915/gvt: subsitute kvm_read/write_guest with vfio_iova_rw
drivers/gpu/drm/i915/gvt/kvmgt.c | 26 +++-------
drivers/vfio/vfio.c | 45 ++++++++++++++++++
drivers/vfio/vfio_iommu_type1.c | 81 ++++++++++++++++++++++++++++++++
include/linux/vfio.h | 5 ++
4 files changed, 138 insertions(+), 19 deletions(-)
--
2.17.1
next reply other threads:[~2020-01-03 1:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 1:00 Yan Zhao [this message]
2020-01-03 1:02 ` [PATCH 1/2] vfio: introduce vfio_iova_rw to read/write a range of IOVAs Yan Zhao
2020-01-09 18:16 ` Alex Williamson
2020-01-10 3:24 ` Yan Zhao
2020-01-03 1:03 ` [PATCH 2/2] drm/i915/gvt: subsitute kvm_read/write_guest with vfio_iova_rw Yan Zhao
2020-01-07 10:21 ` Paolo Bonzini
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=20200103010055.4140-1-yan.y.zhao@intel.com \
--to=yan.y.zhao@intel.com \
--cc=alex.williamson@redhat.com \
--cc=intel-gvt@eclists.intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=zhenyuw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®