From: Alexander Graf <agraf@suse.de>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>,
kvm-ppc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Cc: aik@ozlabs.ru, alex.williamson@redhat.com, qiudayu@linux.vnet.ibm.com
Subject: Re: [PATCH v8 0/3] EEH Support for VFIO PCI Device
Date: Thu, 05 Jun 2014 12:54:47 +0000 [thread overview]
Message-ID: <53906897.4080209@suse.de> (raw)
In-Reply-To: <1401950169-30206-1-git-send-email-gwshan@linux.vnet.ibm.com>
On 05.06.14 08:36, Gavin Shan wrote:
> The series of patches adds support EEH for PCI devices, which are passed
> through to PowerKVM based guest via VFIO. The implementation is straightforward
> based on the issues or problems we have to resolve to support EEH for PowerKVM
> based guest.
>
> - Emulation for EEH RTAS requests. All EEH RTAS requests goes to QEMU firstly.
> If QEMU can't handle it, the request will be sent to host via newly introduced
> VFIO container IOCTL command (VFIO_EEH_OP) and gets handled in host kernel.
>
> The series of patches requires corresponding QEMU changes.
Acked-by: Alexander Graf <agraf@suse.de>
Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Graf <agraf@suse.de>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>,
kvm-ppc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Cc: aik@ozlabs.ru, alex.williamson@redhat.com, qiudayu@linux.vnet.ibm.com
Subject: Re: [PATCH v8 0/3] EEH Support for VFIO PCI Device
Date: Thu, 05 Jun 2014 14:54:47 +0200 [thread overview]
Message-ID: <53906897.4080209@suse.de> (raw)
In-Reply-To: <1401950169-30206-1-git-send-email-gwshan@linux.vnet.ibm.com>
On 05.06.14 08:36, Gavin Shan wrote:
> The series of patches adds support EEH for PCI devices, which are passed
> through to PowerKVM based guest via VFIO. The implementation is straightforward
> based on the issues or problems we have to resolve to support EEH for PowerKVM
> based guest.
>
> - Emulation for EEH RTAS requests. All EEH RTAS requests goes to QEMU firstly.
> If QEMU can't handle it, the request will be sent to host via newly introduced
> VFIO container IOCTL command (VFIO_EEH_OP) and gets handled in host kernel.
>
> The series of patches requires corresponding QEMU changes.
Acked-by: Alexander Graf <agraf@suse.de>
Alex
next prev parent reply other threads:[~2014-06-05 12:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 6:36 [PATCH v8 0/3] EEH Support for VFIO PCI Device Gavin Shan
2014-06-05 6:36 ` Gavin Shan
2014-06-05 6:36 ` [PATCH v8 1/3] powerpc/eeh: Avoid event on passed PE Gavin Shan
2014-06-05 6:36 ` Gavin Shan
2014-06-05 6:36 ` [PATCH v8 2/3] powerpc/eeh: EEH support for VFIO PCI device Gavin Shan
2014-06-05 6:36 ` Gavin Shan
2014-06-05 6:50 ` Benjamin Herrenschmidt
2014-06-05 6:50 ` Benjamin Herrenschmidt
2014-06-06 0:46 ` Gavin Shan
2014-06-06 0:46 ` Gavin Shan
2014-06-05 6:36 ` [PATCH v8 3/3] drivers/vfio: " Gavin Shan
2014-06-05 6:36 ` Gavin Shan
2014-06-05 17:18 ` Alex Williamson
2014-06-05 17:18 ` Alex Williamson
2014-06-06 0:55 ` Gavin Shan
2014-06-06 0:55 ` Gavin Shan
2014-06-05 12:54 ` Alexander Graf [this message]
2014-06-05 12:54 ` [PATCH v8 0/3] EEH Support for VFIO PCI Device Alexander Graf
2014-06-06 0:56 ` Gavin Shan
2014-06-06 0:56 ` 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=53906897.4080209@suse.de \
--to=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=qiudayu@linux.vnet.ibm.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.