From: "Liu, Yi L" <yi.l.liu@intel.com>
To: alex.williamson@redhat.com, kwankhede@nvidia.com
Cc: kevin.tian@intel.com, baolu.lu@linux.intel.com,
yi.l.liu@intel.com, yi.y.sun@intel.com, joro@8bytes.org,
jean-philippe.brucker@arm.com, peterx@redhat.com,
linux-kernel@vger.kernel.org
Subject: [RFC v2 0/2] vfio/pci: wrap pci device as a mediated device
Date: Tue, 12 Mar 2019 16:18:21 +0800 [thread overview]
Message-ID: <1552378703-11202-1-git-send-email-yi.l.liu@intel.com> (raw)
This patchset aims to add a vfio-pci-like meta driver as a demo
user of the vfio changes introduced in "vfio/mdev: IOMMU aware
mediated device" patchset from Baolu Lu.
Previous RFC v1 has given two proposals and the discussion could
be found in following link. Per the comments, this patchset adds
a separate driver named vfio-pci-mdev. It leverages some symbols
from existing vfio-pci. When device is bound to vfio-pci-mdev
driver, it would be wrapped as a mediated device. And user should
create a mdev on this device via the mdev interface exposed to
user.
https://lkml.org/lkml/2019/3/4/529
The new vfio-pci-mdev driver could be used to verify the vfio
changes in "vfio/mdev: IOMMU aware mediated device". Besides,
per Alex's comments, it could also be a good base driver for
experimenting with device specific mdev migration.
Specific interface tested in this proposal:
*) int mdev_set_iommu_device(struct device *dev,
struct device *iommu_device)
introduced in the patch as below:
"[PATCH v5 6/8] vfio/mdev: Add iommu related member in mdev_device"
Links:
*) Link of "vfio/mdev: IOMMU aware mediated device"
https://lwn.net/Articles/780522/
Please feel free give your comments.
Thanks,
Yi Liu
Change log:
v1->v2:
- instead of adding kernel option to existing vfio-pci
module in v1, v2 follows Alex's suggestion to add a
separate vfio-pci-mdev module.
- new patchset subject: "vfio/pci: wrap pci device as a mediated device"
Liu, Yi L (2):
vfio/pci: export common symbols in vfio-pci
vfio/pci: add vfio-pci-mdev driver
drivers/vfio/pci/Kconfig | 11 ++
drivers/vfio/pci/Makefile | 5 +
drivers/vfio/pci/vfio_pci.c | 101 ++++++-----
drivers/vfio/pci/vfio_pci_mdev.c | 334 ++++++++++++++++++++++++++++++++++++
drivers/vfio/pci/vfio_pci_private.h | 17 ++
5 files changed, 428 insertions(+), 40 deletions(-)
create mode 100644 drivers/vfio/pci/vfio_pci_mdev.c
--
2.7.4
next reply other threads:[~2019-03-13 8:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 8:18 Liu, Yi L [this message]
2019-03-12 8:18 ` [RFC v2 1/2] vfio/pci: export common symbols in vfio-pci Liu, Yi L
2019-03-19 18:14 ` Alex Williamson
2019-03-20 11:49 ` Liu, Yi L
2019-03-20 19:22 ` Alex Williamson
2019-03-23 11:06 ` Liu, Yi L
2019-03-25 18:17 ` Alex Williamson
2019-03-26 12:37 ` Liu, Yi L
2019-03-26 15:35 ` Alex Williamson
2019-03-27 8:42 ` Liu, Yi L
2019-03-12 8:18 ` [RFC v2 2/2] vfio/pci: add vfio-pci-mdev driver Liu, Yi L
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=1552378703-11202-1-git-send-email-yi.l.liu@intel.com \
--to=yi.l.liu@intel.com \
--cc=alex.williamson@redhat.com \
--cc=baolu.lu@linux.intel.com \
--cc=jean-philippe.brucker@arm.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=yi.y.sun@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).