From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: linuxppc-dev@ozlabs.org
Cc: kvm@vger.kernel.org, aik@ozlabs.ru,
Gavin Shan <gwshan@linux.vnet.ibm.com>,
agraf@suse.de, alex.williamson@redhat.com,
david@gibson.dropbear.id.au
Subject: [PATCH v3 0/2] EEH Error Injection Support for VFIO Devices
Date: Sat, 21 Mar 2015 06:58:43 +1100 [thread overview]
Message-ID: <1426881525-11044-1-git-send-email-gwshan@linux.vnet.ibm.com> (raw)
Those two patches are extention to EEH support for VFIO PCI devices,
which allows to inject EEH errors to VFIO PCI devices from userspace
for testing purpose.
Changelog
=========
v2 -> v3:
* Use offsetofend(), instead of sizeof(struct vfio_eeh_pe_op)
to calculate argument buffer size.
v1 -> v2:
* Use EEH_ERR_FUNC_{MIN,MAX} to validate PCI error function.
* Put additional arguments for error injection to union in
struct vfio_eeh_pe_op.
Gavin Shan (2):
powerpc/eeh: Introduce eeh_pe_inject_err()
drivers/vfio: Support EEH error injection
Documentation/vfio.txt | 12 ++++++++++++
arch/powerpc/include/asm/eeh.h | 26 ++++++++++++++++++++++++++
arch/powerpc/kernel/eeh.c | 35 +++++++++++++++++++++++++++++++++++
drivers/vfio/vfio_spapr_eeh.c | 10 ++++++++++
include/uapi/linux/vfio.h | 36 +++++++++++++++++++++++++++++++++++-
5 files changed, 118 insertions(+), 1 deletion(-)
--
1.8.3.2
next reply other threads:[~2015-03-20 19:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 19:58 Gavin Shan [this message]
2015-03-20 19:58 ` [PATCH v3 1/2] powerpc/eeh: Introduce eeh_pe_inject_err() Gavin Shan
2015-03-23 1:33 ` David Gibson
2015-03-20 19:58 ` [PATCH v3 2/2] drivers/vfio: Support EEH error injection Gavin Shan
2015-03-23 1:39 ` David Gibson
2015-03-23 1:56 ` Gavin Shan
2015-03-23 3:43 ` David Gibson
2015-03-23 5:03 ` Gavin Shan
2015-03-23 5:10 ` David Gibson
2015-03-23 5:20 ` Gavin Shan
2015-03-23 16:14 ` Alex Williamson
2015-03-23 22:47 ` Gavin Shan
2015-03-24 1:22 ` David Gibson
2015-03-24 2:41 ` Gavin Shan
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=1426881525-11044-1-git-send-email-gwshan@linux.vnet.ibm.com \
--to=gwshan@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@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).