From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: aik@ozlabs.ru, qemu-ppc@nongnu.org,
Gavin Shan <gwshan@linux.vnet.ibm.com>,
david@gibson.dropbear.id.au
Subject: [Qemu-devel] [PATCH v4 0/3] sPAPR: Support EEH Error Injection
Date: Mon, 10 Aug 2015 17:13:02 +1000 [thread overview]
Message-ID: <1439190785-18908-1-git-send-email-gwshan@linux.vnet.ibm.com> (raw)
The patchset depends on below Linux upstream commits:
commit ed3e81f ("powerpc/eeh: Move PE state constants around")
commit ec33d36 ("powerpc/eeh: Introduce eeh_pe_inject_err()")
According to PAPR specification 2.7, there're 3 RTAS calls relevent to error
injection: "ibm,open-errinjct", "ibm,close-errinjct", "ibm,errinjct". The
userland utility "errinjct" running on guest utilizes those 3 RTAS calls like
this way: Call "ibm,open-errinjct" that returns open-token, which is passed to
"ibm,errinjct" together with error specific arguments to do error injection.
Finally, to return the open-token by calling "ibm,close-errinject".
"ibm,errinjct" can be used to inject various errors, not limited to EEH errors.
However, this patchset is going to support injecting EEH errors only for VFIO
PCI devices.
=========
Changelog
=========
v3 -> v4:
* To record currently opened token, not next one as suggested by Alexey.
v2 -> v3:
* Replace random token number with incremental counter. Another boolean
variable to track if it's opened. Both of them are added to migration
stream.
* The return value from sPAPRPHBClass::eeh_inject_error() can be passed
to user directly. No need to do conversion.
* Corrected error code to RTAS_OUT_CLOSE_ERROR in rtas_ibm_errinjct().
* Don't expose error injection tokens for unsupported types.
v1 -> v2:
* Rebased to git://github.com/dgibson/qemu.git (branch: spapr-next)
* Remove specific PCI error types in hw/ppc/spapr.h. Use those macros
asm-powerpc/eeh.h instead.
Gavin Shan (3):
linux-headers: Add eeh.h
sPAPR: Support RTAS call ibm, {open, close}-errinjct
sPAPR: Support RTAS call ibm,errinjct
hw/ppc/spapr.c | 5 ++
hw/ppc/spapr_pci.c | 36 ++++++++++
hw/ppc/spapr_pci_vfio.c | 56 ++++++++++++++++
hw/ppc/spapr_rtas.c | 143 ++++++++++++++++++++++++++++++++++++++++
include/hw/pci-host/spapr.h | 2 +
include/hw/ppc/spapr.h | 17 ++++-
linux-headers/asm-powerpc/eeh.h | 56 ++++++++++++++++
7 files changed, 314 insertions(+), 1 deletion(-)
create mode 100644 linux-headers/asm-powerpc/eeh.h
--
2.1.0
next reply other threads:[~2015-08-11 0:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 7:13 Gavin Shan [this message]
2015-08-10 7:13 ` [Qemu-devel] [PATCH v4 1/3] linux-headers: Add eeh.h Gavin Shan
2015-08-11 9:11 ` Peter Maydell
2015-08-12 1:55 ` David Gibson
2015-08-12 2:00 ` Alexey Kardashevskiy
2015-08-13 1:30 ` Gavin Shan
2015-08-13 1:42 ` David Gibson
2015-08-14 1:10 ` Gavin Shan
2015-08-24 7:23 ` Gavin Shan
2015-08-24 12:00 ` Gavin Shan
2015-08-10 7:13 ` [Qemu-devel] [PATCH v4 2/3] sPAPR: Support RTAS call ibm, {open, close}-errinjct Gavin Shan
2015-08-10 7:13 ` [Qemu-devel] [PATCH v4 3/3] sPAPR: Support RTAS call ibm,errinjct 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=1439190785-18908-1-git-send-email-gwshan@linux.vnet.ibm.com \
--to=gwshan@linux.vnet.ibm.com \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).