From: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
To: qemu-devel@nongnu.org
Cc: izumi.taku@jp.fujitsu.com, alex.williamson@redhat.com
Subject: [Qemu-devel] [RFC v4 0/9] pass aer error to guest for vfio device
Date: Mon, 2 Mar 2015 15:16:03 +0800 [thread overview]
Message-ID: <cover.1425280224.git.chen.fan.fnst@cn.fujitsu.com> (raw)
For now, for vfio pci passthough devices when qemu receives
an error from host aer report, there just terminate the guest,
but usually user want to know what error occurred but stop the
guest, so this patches add aer capability support for vfio device,
and pass the error to guest, and have guest driver to recover
from the error.
and turning on SERR# for error forwording in bridge control register
patch in seabios has been merged.
v3-v4:
1. add 'x-aer' for user to off aer capability.
2. refactor vfio device to parse extended capabilities.
v2-v3:
1. refactor vfio device to parse extended capability.
2. add global property for piix4 to disable vfio aer cap.
v1-v2:
1. turn on SERR# for bridge control register in firmware.
2. initilize aer capability for vfio device.
3. fix some trivial bug.
Chen Fan (9):
pcie_aer: fix typos in pcie_aer_inject_error comment
aer: fix a wrong init PCI_ERR_COR_STATUS w1cmask type register
vfio: add pcie extanded capability support
aer: impove pcie_aer_init to support vfio device
vfio: add aer support for vfio device
vfio: add 'x-aer' option to disable aer capability
pcie_aer: expose pcie_aer_msg() interface
vfio-pci: pass the aer error to guest
pcie: fix several trivial typos
hw/pci-bridge/ioh3420.c | 3 +-
hw/pci-bridge/xio3130_downstream.c | 3 +-
hw/pci-bridge/xio3130_upstream.c | 3 +-
hw/pci/pcie_aer.c | 17 ++--
hw/vfio/pci.c | 160 +++++++++++++++++++++++++++++++++++--
include/hw/pci/pci.h | 2 +-
include/hw/pci/pcie_aer.h | 7 +-
7 files changed, 174 insertions(+), 21 deletions(-)
--
1.9.3
next reply other threads:[~2015-03-02 7:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 7:16 Chen Fan [this message]
2015-03-02 7:16 ` [Qemu-devel] [RFC v4 1/9] pcie_aer: fix typos in pcie_aer_inject_error comment Chen Fan
2015-03-02 7:16 ` [Qemu-devel] [RFC v4 2/9] aer: fix a wrong init PCI_ERR_COR_STATUS w1cmask type register Chen Fan
2015-03-02 7:16 ` [Qemu-devel] [RFC v4 3/9] vfio: add pcie extanded capability support Chen Fan
2015-03-09 20:28 ` Alex Williamson
2015-03-11 2:42 ` Chen Fan
2015-03-02 7:16 ` [Qemu-devel] [RFC v4 4/9] aer: impove pcie_aer_init to support vfio device Chen Fan
2015-03-09 20:29 ` Alex Williamson
2015-03-11 2:37 ` Chen Fan
2015-03-12 10:29 ` Chen Fan
2015-03-02 7:16 ` [Qemu-devel] [RFC v4 5/9] vfio: add aer support for " Chen Fan
2015-03-02 7:16 ` [Qemu-devel] [RFC v4 6/9] vfio: add 'x-aer' option to disable aer capability Chen Fan
2015-03-09 20:29 ` Alex Williamson
2015-03-11 3:42 ` Chen Fan
2015-03-11 15:44 ` Alex Williamson
2015-03-02 7:16 ` [Qemu-devel] [RFC v4 7/9] pcie_aer: expose pcie_aer_msg() interface Chen Fan
2015-03-02 7:16 ` [Qemu-devel] [RFC v4 8/9] vfio-pci: pass the aer error to guest Chen Fan
2015-03-09 20:29 ` Alex Williamson
2015-03-11 2:57 ` Chen Fan
2015-03-02 7:16 ` [Qemu-devel] [RFC v4 9/9] pcie: fix several trivial typos Chen Fan
2015-03-09 1:33 ` [Qemu-devel] [RFC v4 0/9] pass aer error to guest for vfio device Chen Fan
2015-03-09 20:34 ` Alex Williamson
2015-03-10 1:27 ` Chen Fan
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=cover.1425280224.git.chen.fan.fnst@cn.fujitsu.com \
--to=chen.fan.fnst@cn.fujitsu.com \
--cc=alex.williamson@redhat.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=qemu-devel@nongnu.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).