From: Yan Zhao <yan.y.zhao@intel.com>
To: alex.williamson@redhat.com
Cc: kevin.tian@intel.com, Yan Zhao <yan.y.zhao@intel.com>,
cohuck@redhat.com, qemu-devel@nongnu.org,
zhenyuw@linux.intel.com, shaopeng.he@intel.com,
zhi.a.wang@intel.com
Subject: [RFC PATCH 0/2] QEMU: Dynamic trap/untrap of VFIO PCI BARs
Date: Wed, 4 Dec 2019 22:44:51 -0500 [thread overview]
Message-ID: <20191205034451.30181-1-yan.y.zhao@intel.com> (raw)
This patchset enables PCI BARs to be dynamically trapped/passthroughed
in response to vendor driver's needs.
To dynamic trap/untrap PCI BARs, 3 info required:
(1) which part of PCI BARs are to be trapped/passthroughed
(2) when to do the trap/passthrough transition
(3) to trap or to passthrough
Patch 1 let vendor driver specify which sparse mmaped subregions are
disablable. Therefore providing the first info.
Patch 2 probes and creates dynamic trap bar info region, whose
"dt_fd" field provides the second info, and
"trap" field provide the third info.
The corresponding kernel implementation is at
https://www.spinics.net/lists/kernel/msg3337337.html.
Yan Zhao (2):
hw/vfio: add a 'disablable' flag to sparse mmaped region
hw/vfio/pci: init dynamic-trap-bar-info region
hw/vfio/common.c | 28 +++++++-
hw/vfio/pci.c | 117 ++++++++++++++++++++++++++++++++++
hw/vfio/pci.h | 5 ++
hw/vfio/trace-events | 4 +-
include/hw/vfio/vfio-common.h | 2 +
linux-headers/linux/vfio.h | 13 ++++
6 files changed, 167 insertions(+), 2 deletions(-)
--
2.17.1
next reply other threads:[~2019-12-05 3:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 3:44 Yan Zhao [this message]
2019-12-05 3:45 ` [RFC PATCH 1/2] hw/vfio: add a 'disablable' flag to sparse mmaped region Yan Zhao
2019-12-05 3:45 ` [RFC PATCH 2/2] hw/vfio/pci: init dynamic-trap-bar-info region Yan Zhao
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=20191205034451.30181-1-yan.y.zhao@intel.com \
--to=yan.y.zhao@intel.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=kevin.tian@intel.com \
--cc=qemu-devel@nongnu.org \
--cc=shaopeng.he@intel.com \
--cc=zhenyuw@linux.intel.com \
--cc=zhi.a.wang@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).