From: Gleb Natapov <gleb@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: "Pandarathil, Vijaymohan R" <vijaymohan.pandarathil@hp.com>,
Alex Williamson <alex.williamson@redhat.com>,
Bjorn Helgaas <bhelgaas@google.com>,
"Ortiz, Lance E" <lance.oritz@hp.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 3/3] QEMU-AER: Qemu changes to support AER for VFIO-PCI devices
Date: Tue, 5 Feb 2013 10:04:36 +0200 [thread overview]
Message-ID: <20130205080436.GV23213@redhat.com> (raw)
In-Reply-To: <CAAu8pHvk_2Mf2F-YTDC-wdyD1Jic-DHUanSQfOa3g0VchTcNig@mail.gmail.com>
On Sun, Feb 03, 2013 at 04:36:11PM +0000, Blue Swirl wrote:
> On Sun, Feb 3, 2013 at 2:10 PM, Pandarathil, Vijaymohan R
> <vijaymohan.pandarathil@hp.com> wrote:
> > - Create eventfd per vfio device assigned to a guest and register an
> > event handler
> >
> > - This fd is passed to the vfio_pci driver through the SET_IRQ ioctl
> >
> > - When the device encounters an error, the eventfd is signalled
> > and the qemu eventfd handler gets invoked.
> >
> > - In the handler decide what action to take. Current action taken
> > is to terminate the guest.
>
> Usually this is not OK, but I guess this is not guest triggerable.
>
Still not OK. Why not stop a guest with appropriate stop reason?
--
Gleb.
next prev parent reply other threads:[~2013-02-05 8:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 14:10 [PATCH v3 3/3] QEMU-AER: Qemu changes to support AER for VFIO-PCI devices Pandarathil, Vijaymohan R
2013-02-03 14:10 ` [Qemu-devel] " Pandarathil, Vijaymohan R
2013-02-03 16:36 ` Blue Swirl
2013-02-03 16:36 ` [Qemu-devel] " Blue Swirl
2013-02-03 16:36 ` Blue Swirl
2013-02-05 8:04 ` Gleb Natapov [this message]
2013-02-05 9:05 ` Pandarathil, Vijaymohan R
2013-02-05 9:21 ` Gleb Natapov
2013-02-05 10:59 ` Pandarathil, Vijaymohan R
2013-02-05 10:59 ` Pandarathil, Vijaymohan R
2013-02-05 11:36 ` Gleb Natapov
2013-02-05 12:05 ` Pandarathil, Vijaymohan R
2013-02-05 12:30 ` Gleb Natapov
2013-02-05 13:37 ` Alex Williamson
2013-02-05 13:42 ` Gleb Natapov
2013-02-05 14:51 ` Alex Williamson
2013-02-04 16:57 ` Alex Williamson
2013-02-04 16:57 ` Alex Williamson
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=20130205080436.GV23213@redhat.com \
--to=gleb@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=blauwirbel@gmail.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 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.