qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Gleb Natapov <gleb@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Hu Tao <hutao@cn.fujitsu.com>, qemu-devel <qemu-devel@nongnu.org>,
	Luiz Capitulino <lcapitulino@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>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v19 3/7] introduce a new qom device to deal with panicked event
Date: Thu, 18 Apr 2013 13:04:25 +0200	[thread overview]
Message-ID: <516FD339.3080201@redhat.com> (raw)
In-Reply-To: <87obdcgpjx.fsf@blackfin.pond.sub.org>

Il 18/04/2013 11:23, Markus Armbruster ha scritto:
> Hu Tao <hutao@cn.fujitsu.com> writes:
> 
>> pvpanic device is used to send guest panic event from guest to qemu.
>>
>> When guest panic happens, pvpanic device driver will write a event
>> number to IO port 0x505(which is the IO port occupied by pvpanic device,
>> by default). On receiving the event, pvpanic device will pause guest
>> cpu(s), and send a qmp event QEVENT_GUEST_PANICKED.
>>
>> Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
>> Signed-off-by: Hu Tao <hutao@cn.fujitsu.com>
>> ---
>>  hw/misc/Makefile.objs |   2 +
>>  hw/misc/pvpanic.c     | 123 ++++++++++++++++++++++++++++++++++++++++++++++++++
>>  2 files changed, 125 insertions(+)
>>  create mode 100644 hw/misc/pvpanic.c
>>
>> diff --git a/hw/misc/Makefile.objs b/hw/misc/Makefile.objs
>> index 03699c3..d72ea83 100644
>> --- a/hw/misc/Makefile.objs
>> +++ b/hw/misc/Makefile.objs
>> @@ -38,3 +38,5 @@ obj-$(CONFIG_OMAP) += omap_tap.o
>>  obj-$(CONFIG_PXA2XX) += pxa2xx_pcmcia.o
>>  obj-$(CONFIG_SLAVIO) += slavio_misc.o
>>  obj-$(CONFIG_ZYNQ) += zynq_slcr.o
>> +
>> +common-obj-y += pvpanic.o

Sorry for not noticing before, you need to add CONFIG_PVPANIC to both
i386-softmmu.mak and x86_64-softmmu.mak.

If you can respin tomorrow we can include it in 1.5 quite easily, BIOS
patch included.

Paolo

>> diff --git a/hw/misc/pvpanic.c b/hw/misc/pvpanic.c
>> new file mode 100644
>> index 0000000..c3adcdf
>> --- /dev/null
>> +++ b/hw/misc/pvpanic.c
>> @@ -0,0 +1,123 @@
>> +/*
>> + * QEMU simulated pvpanic device.
>> + *
>> + * Copyright Fujitsu, Corp. 2013
>> + *
>> + * Authors:
>> + *     Wen Congyang <wency@cn.fujitsu.com>
>> + *     Hu Tao <hutao@cn.fujitsu.com>
>> + *
>> + * This work is licensed under the terms of the GNU GPL, version 2 or later.
>> + * See the COPYING file in the top-level directory.
>> + *
>> + */
>> +
>> +#include <qapi/qmp/qobject.h>
>> +#include <qapi/qmp/qjson.h>
>> +#include <monitor/monitor.h>
>> +#include <sysemu/sysemu.h>
>> +#include <sysemu/kvm.h>
>> +
>> +/* The bit of supported pv event */
>> +#define PVPANIC_F_PANICKED      0
>> +
>> +/* The pv event value */
>> +#define PVPANIC_PANICKED        (1 << PVPANIC_F_PANICKED)
>> +
>> +#define TYPE_ISA_PVPANIC_DEVICE    "pvpanic"
>> +#define ISA_PVPANIC_DEVICE(obj)    \
>> +    OBJECT_CHECK(PVPanicState, (obj), TYPE_ISA_PVPANIC_DEVICE)
>> +
>> +static void panicked_mon_event(const char *action)
>> +{
>> +    QObject *data;
>> +
>> +    data = qobject_from_jsonf("{ 'action': %s }", action);
>> +    monitor_protocol_event(QEVENT_GUEST_PANICKED, data);
>> +    qobject_decref(data);
>> +}
>> +
>> +static void handle_event(int event)
>> +{
>> +    static bool logged;
>> +
>> +    if (event & ~PVPANIC_PANICKED && !logged) {
>> +        fprintf(stderr, "pvpanic: unknown event %#x.\n", event);
>> +        logged = true;
>> +    }
> 
> qemu_log_mask(LOG_GUEST_ERROR, ...)?
> 
> Could be done on top, without a respin.
> 
>> +
>> +    if (event & PVPANIC_PANICKED) {
>> +        panicked_mon_event("pause");
>> +        vm_stop(RUN_STATE_GUEST_PANICKED);
>> +        return;
>> +    }
>> +}
> [...]
> 

  reply	other threads:[~2013-04-18 11:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-18  2:14 [Qemu-devel] [PATCH v19 0/7] Add pvpanic device to deal with guest panic event Hu Tao
2013-04-18  2:14 ` [Qemu-devel] [PATCH v19 1/7] add a new runstate: RUN_STATE_GUEST_PANICKED Hu Tao
2013-04-18  2:14 ` [Qemu-devel] [PATCH v19 2/7] add a new qevent: QEVENT_GUEST_PANICKED Hu Tao
2013-04-18  2:14 ` [Qemu-devel] [PATCH v19 3/7] introduce a new qom device to deal with panicked event Hu Tao
2013-04-18  9:23   ` Markus Armbruster
2013-04-18 11:04     ` Paolo Bonzini [this message]
2013-04-19  7:07       ` Hu Tao
2013-04-18  2:14 ` [Qemu-devel] [PATCH v19 4/7] pvpanic: pass configurable ioport to seabios Hu Tao
2013-04-18  9:22   ` Markus Armbruster
2013-04-19  6:50     ` Hu Tao
2013-04-19  8:27       ` Markus Armbruster
2013-05-30 13:00   ` Michael S. Tsirkin
2013-04-18  2:14 ` [Qemu-devel] [PATCH v19 5/7] pvpanic: add document of pvpanic Hu Tao
2013-04-18  2:14 ` [Qemu-devel] [PATCH v19 6/7] pvpanic: create pvpanic by default for machine 1.5 Hu Tao
2013-04-18  2:14 ` [Qemu-devel] [PATCH v19 7/7] Wire up disabled wait a panicked event on s390 Hu Tao
2013-06-03 15:44 ` [Qemu-devel] [PATCH v19 0/7] Add pvpanic device to deal with guest panic event Anthony Liguori

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=516FD339.3080201@redhat.com \
    --to=pbonzini@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=gleb@redhat.com \
    --cc=hutao@cn.fujitsu.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=lcapitulino@redhat.com \
    --cc=levinsasha928@gmail.com \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=owasserm@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).