qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Vijay Mohan Pandarathil <vijaymohan.pandarathil@hp.com>
Cc: gleb@redhat.com, kvm@vger.kernel.org, linux-pci@vger.kernel.org,
	qemu-devel@nongnu.org, linux-kernel@vger.kernel.org,
	blauwirbel@gmail.com, bhelgaas@google.com, lance.oritz@hp.com
Subject: Re: [Qemu-devel] [PATCH v7 0/3] AER-KVM: Error containment of VFIO devices assigned to KVM guests
Date: Tue, 12 Mar 2013 15:08:04 -0600	[thread overview]
Message-ID: <1363122484.24132.113.camel@bling.home> (raw)
In-Reply-To: <1362815537-27303-1-git-send-email-vijaymohan.pandarathil@hp.com>

On Sat, 2013-03-09 at 01:52 -0600, Vijay Mohan Pandarathil wrote:
> Add support for error containment when a VFIO device assigned to a KVM
> guest encounters an error. This is for PCIe devices/drivers that support AER
> functionality. When the host OS is notified of an error in a device either
> through the firmware first approach or through an interrupt handled by the AER
> root port driver, the error handler registered by the vfio-pci driver gets
> invoked. The qemu process is signaled through an eventfd registered per
> VFIO device by the qemu process. In the eventfd handler, qemu decides on
> what action to take. In this implementation, guest is brought down to
> contain the error.
> 
> 
> v7:
>  - Rebased to latest upstream
>  - Used device_lock() for synchronising err_trigger access
> v6:
>  - Rebased to latest upstream
>  - Resolved merge conflict with vfio_dev_present()
> v5:
>  - Rebased to latest upstream stable bits
>  - Incorporated v4 feedback
> v4:
>  - Stop the guest instead of terminating
>  - Remove unwanted returns from functions
>  - Incorporate other feedback
> v3:
>  - Removed PCI_AER* flags from device info ioctl.
>  - Incorporated feedback
> v2:
>  - Rebased to latest upstream stable bits
>  - Changed the new ioctl to be part of VFIO_SET_IRQs ioctl
>  - Added a new patch to get/put reference to a vfio device from struct device
>  - Incorporated all other feedback.
> 
> ---
> 
> Vijay Mohan Pandarathil(3):
> 
> [PATCH 1/3] VFIO: Wrapper to get reference to vfio_device from device 
> [PATCH 2/3] VFIO-AER: Vfio-pci driver changes for supporting AER
> [PATCH 3/3] QEMU-AER: Qemu changes to support AER for VFIO-PCI devices
> 
> Kernel files changed
> 
>  drivers/vfio/vfio.c  | 30 +++++++++++++++++++++++++++++-
>  include/linux/vfio.h |  3 +++
>  2 files changed, 32 insertions(+), 1 deletion(-)
> 
>  drivers/vfio/pci/vfio_pci.c         | 44 ++++++++++++++++++++++++-
>  drivers/vfio/pci/vfio_pci_intrs.c   | 64 +++++++++++++++++++++++++++++++++++++
>  drivers/vfio/pci/vfio_pci_private.h |  1 +
>  include/uapi/linux/vfio.h           |  1 +
>  4 files changed, 109 insertions(+), 1 deletion(-)

Applied 1 & 2 to my next tree, patch 3 is qemu and depends on the vfio.h
change getting into mainline so will need to be re-sent once that
happens.  Thanks,

Alex

> Qemu files changed
> 
>  hw/vfio_pci.c              | 123 +++++++++++++++++++++++++++++++++++++++++++++
>  linux-headers/linux/vfio.h |   1 +
>  2 files changed, 124 insertions(+)

      parent reply	other threads:[~2013-03-12 21:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-09  7:52 [Qemu-devel] [PATCH v7 0/3] AER-KVM: Error containment of VFIO devices assigned to KVM guests Vijay Mohan Pandarathil
2013-03-09  7:52 ` [Qemu-devel] [PATCH v7 1/3] VFIO: Wrapper for getting reference to vfio_device from device Vijay Mohan Pandarathil
2013-03-09  7:52 ` [Qemu-devel] [PATCH v7 2/3] VFIO-AER: Vfio-pci driver changes for supporting AER Vijay Mohan Pandarathil
2013-03-09  7:52 ` [Qemu-devel] [PATCH v7 3/3] QEMU-AER: Qemu changes to support AER for VFIO-PCI devices Vijay Mohan Pandarathil
2013-03-12 21:08 ` Alex Williamson [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=1363122484.24132.113.camel@bling.home \
    --to=alex.williamson@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=blauwirbel@gmail.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lance.oritz@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vijaymohan.pandarathil@hp.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 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).