From: Gleb Natapov <gleb@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Hu Tao <hutao@cn.fujitsu.com>, qemu-devel <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>,
Blue Swirl <blauwirbel@gmail.com>,
Orit Wasserman <owasserm@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Alexander Graf <agraf@suse.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Andrew Jones <drjones@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Sasha Levin <levinsasha928@gmail.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Kevin Wolf <kwolf@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v14 3/4] introduce pvevent device to deal with panicked event
Date: Thu, 14 Mar 2013 11:19:19 +0200 [thread overview]
Message-ID: <20130314091919.GD11223@redhat.com> (raw)
In-Reply-To: <514194E4.3040208@redhat.com>
On Thu, Mar 14, 2013 at 10:14:12AM +0100, Paolo Bonzini wrote:
> Il 14/03/2013 09:15, Hu Tao ha scritto:
> > pvevent device is used to send guest panic event from guest to qemu.
> >
> > When guest panic happens, pvevent device driver will write a event
> > number to IO port 0x505(which is the IO port occupied by pvevent device,
> > by default). On receiving the event, pvevent device will pause guest
> > cpu(s), and send a qmp event QEVENT_GUEST_PANICKED.
> >
> > TODO: make the IO port configurable
>
> The port is already configurable as far as the device is concerned; when
> you add the port to the PC boards you will have to wind up fw-cfg.
>
Why not add fw-cfg when device is created (with -device for instance)?
> So these patches can go in already, with the sole change that the HID
> must be in the QEMU namespace rather than MSFT.
>
We should request one for QEMU.
--
Gleb.
next prev parent reply other threads:[~2013-03-14 9:19 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 8:15 [Qemu-devel] [PATCH v14 0/4] pvevent device to deal with guest panic event Hu Tao
2013-03-14 8:15 ` [Qemu-devel] [PATCH v14 1/4] add a new runstate: RUN_STATE_GUEST_PANICKED Hu Tao
2013-03-20 8:58 ` Markus Armbruster
2013-03-20 10:54 ` Paolo Bonzini
2013-03-20 11:07 ` Markus Armbruster
2013-03-14 8:15 ` [Qemu-devel] [PATCH v14 2/4] add a new qevent: QEVENT_GUEST_PANICKED Hu Tao
2013-03-20 9:04 ` Markus Armbruster
2013-03-14 8:15 ` [Qemu-devel] [PATCH v14 3/4] introduce pvevent device to deal with panicked event Hu Tao
2013-03-14 9:14 ` Paolo Bonzini
2013-03-14 9:19 ` Gleb Natapov [this message]
2013-03-14 9:43 ` Paolo Bonzini
2013-03-14 11:00 ` Alexander Graf
2013-03-14 11:03 ` Paolo Bonzini
2013-03-14 11:23 ` Alexander Graf
2013-03-14 11:28 ` Gleb Natapov
2013-03-20 9:24 ` Markus Armbruster
2013-03-14 12:34 ` Gleb Natapov
2013-03-14 13:49 ` Paolo Bonzini
2013-03-14 13:56 ` Gleb Natapov
2013-03-14 14:05 ` Paolo Bonzini
2013-03-14 14:23 ` Gleb Natapov
2013-03-14 15:50 ` Paolo Bonzini
2013-03-14 15:59 ` Gleb Natapov
2013-03-14 16:13 ` Paolo Bonzini
2013-03-15 11:34 ` Gleb Natapov
2013-03-20 9:16 ` Markus Armbruster
2013-03-14 9:46 ` Hu Tao
2013-03-20 9:15 ` Markus Armbruster
2013-03-14 8:15 ` [Qemu-devel] [PATCH v14 4/4] pvevent: add document to describe the usage Hu Tao
2013-03-14 8:45 ` Paolo Bonzini
2013-03-14 9:35 ` Hu Tao
2013-03-14 20:35 ` Eric Blake
2013-03-14 8:58 ` [Qemu-devel] [PATCH v14 0/4] pvevent device to deal with guest panic event Gleb Natapov
2013-03-14 9:36 ` Hu Tao
2013-03-20 9:29 ` Markus Armbruster
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=20130314091919.GD11223@redhat.com \
--to=gleb@redhat.com \
--cc=agraf@suse.de \
--cc=alex.williamson@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=borntraeger@de.ibm.com \
--cc=drjones@redhat.com \
--cc=hutao@cn.fujitsu.com \
--cc=jan.kiszka@siemens.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=levinsasha928@gmail.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@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 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).