From: Gavin Shan <shangw@linux.vnet.ibm.com>
To: kvm@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Cc: aik@ozlabs.ru, alex.williamson@redhat.com,
Gavin Shan <shangw@linux.vnet.ibm.com>
Subject: [PATCH 0/3] VFIO change for EEH support
Date: Fri, 15 Mar 2013 15:26:27 +0800 [thread overview]
Message-ID: <1363332390-12754-1-git-send-email-shangw@linux.vnet.ibm.com> (raw)
The EEH (Enhanced Error Handling) is one of RAS features on IBM Power
machines. In order to support EEH, the VFIO needs some modification
as the patchset addresses. Firstly, the address (domain:bus:slot:function)
of passed PCI devices looks quite different from host and guest perspectives.
So we have to mantain the address mapping in host so that the EEH could
direct the EEH errors from guest to proper PCI device. Unfortunately, it
seems that the VFIO implementation doesn't include the mechanism yet. On
the other hand, it's totally business of individual platforms. So I introduced
some weak functions in VFIO driver and individual platforms can override
that to figure out more information that platform needs. Apart from that,
the last patch [3/3] is changing the current behavior of accessing uncoverred
config space for specific PCI device.
The patchset is expected to be applied after Alexy's patchset (supporting
VFIO on PowerNV platform). Besides, there're patchset based on it queued
in my personal tree for EEH core to support PowerKVM guest. With all of
them (Alexy's patchset, this patchset, EEH core patchset), I can sucessfully
pass PCI device to guest and recover it from EEH errors.
drivers/vfio/pci/vfio_pci.c | 42 ++++++++++++++++++++++++++++++------
drivers/vfio/pci/vfio_pci_config.c | 31 +++++++++++++++++---------
include/linux/vfio.h | 7 +++++-
include/uapi/linux/vfio.h | 16 +++++++++++++
4 files changed, 77 insertions(+), 19 deletions(-)
Thanks,
Gavin
next reply other threads:[~2013-03-15 7:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 7:26 Gavin Shan [this message]
2013-03-15 7:26 ` [PATCH 1/3] VFIO: Architecture dependent VFIO device operations Gavin Shan
2013-03-15 7:26 ` [PATCH 2/3] VFIO: VFIO_DEVICE_SET_ADDR_MAPPING command Gavin Shan
2013-03-15 19:29 ` Alex Williamson
2013-03-16 1:34 ` Gavin Shan
2013-03-16 5:37 ` Benjamin Herrenschmidt
2013-03-18 21:01 ` Alex Williamson
2013-03-19 3:24 ` Gavin Shan
2013-03-19 4:18 ` Alex Williamson
2013-03-19 4:45 ` Benjamin Herrenschmidt
2013-03-20 18:48 ` Alex Williamson
2013-03-20 19:31 ` Benjamin Herrenschmidt
2013-03-20 19:46 ` Alex Williamson
2013-03-21 2:09 ` Gavin Shan
2013-03-15 7:26 ` [PATCH 3/3] VFIO: Direct access config reg without capability Gavin Shan
2013-03-15 19:41 ` Alex Williamson
2013-03-16 3:34 ` Gavin Shan
2013-03-16 5:30 ` Benjamin Herrenschmidt
2013-03-18 21:15 ` Alex Williamson
2013-03-21 0:58 ` Alex Williamson
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=1363332390-12754-1-git-send-email-shangw@linux.vnet.ibm.com \
--to=shangw@linux.vnet.ibm.com \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).