All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: Thomas Huth <thuth@redhat.com>
Cc: lvivier@redhat.com, peter.maydell@linaro.org,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Gavin Shan <gwshan@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH v8 0/7] sPAPR: Support EEH Error Injection
Date: Thu, 1 Oct 2015 17:25:04 +1000	[thread overview]
Message-ID: <20151001072504.GA13255@gwshan> (raw)
In-Reply-To: <55F7B4A7.3090008@redhat.com>

On Tue, Sep 15, 2015 at 08:03:19AM +0200, Thomas Huth wrote:
>On 14/09/15 06:14, David Gibson wrote:
>> On Mon, Sep 14, 2015 at 11:36:08AM +1000, Gavin Shan wrote:
>>> 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.
>> 
>> I'm happy to merge 6..7/7 once 1..5/7 are in - I'm not sure what tree
>> they should be going through.
>
>According to the MAINTAINERS file, there is no explicit maintainer for
>the linux-headers directory ... so I think you should maybe try to get
>an "Acked-by" from Jan Kiszka (for the update-linux-header script)
>and/or Michael Tsirkin (for the PCI stuff) and then take this through
>your tree?
>

Jan and Michael, any ideas on how to handle this? :-)

Thanks,
Gavin

> Thomas
>
>

      reply	other threads:[~2015-10-01  7:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14  1:36 [Qemu-devel] [PATCH v8 0/7] sPAPR: Support EEH Error Injection Gavin Shan
2015-09-14  1:36 ` [Qemu-devel] [PATCH v8 1/7] scripts: Allow include "stdint.h" in virtio headers Gavin Shan
2015-09-14  1:36 ` [Qemu-devel] [PATCH v8 2/7] scripts: Include arch/powerpc/include/uapi/asm/eeh.h Gavin Shan
2015-09-14  1:36 ` [Qemu-devel] [PATCH v8 3/7] scripts: Submit changes while updating linux headers Gavin Shan
2015-09-14  4:12   ` David Gibson
2015-09-14  1:36 ` [Qemu-devel] [PATCH v8 4/7] Synchronize Linux headers from kernel 4.3.0-rc1 Gavin Shan
2015-09-14  1:36 ` [Qemu-devel] [PATCH v8 5/7] Obsolete PCI_MSIX_FLAGS_BIRMASK Gavin Shan
2015-09-14  1:36 ` [Qemu-devel] [PATCH v8 6/7] sPAPR: Support RTAS call ibm, {open, close}-errinjct Gavin Shan
2015-09-14  1:36 ` [Qemu-devel] [PATCH v8 7/7] sPAPR: Support RTAS call ibm,errinjct Gavin Shan
2015-09-14  4:14 ` [Qemu-devel] [PATCH v8 0/7] sPAPR: Support EEH Error Injection David Gibson
2015-09-15  6:03   ` Thomas Huth
2015-10-01  7:25     ` Gavin Shan [this message]

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=20151001072504.GA13255@gwshan \
    --to=gwshan@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=jan.kiszka@siemens.com \
    --cc=lvivier@redhat.com \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=thuth@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.