qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hu Tao <hutao@cn.fujitsu.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v20 0/7] Add pvpanic device to deal with guest panic event
Date: Fri, 19 Apr 2013 15:06:18 +0800	[thread overview]
Message-ID: <cover.1366354934.git.hutao@cn.fujitsu.com> (raw)

This series introduces a new simulated device, pvpanic, to notify
qemu when guest panic event happens.

Along with this series, there are two patches to add seabios ACPI
driver and kernel ACPI driver for the device, respectively.

Tested with:

  - qemu(kvm)/qemu(tcg)
  - qemu piix/q35
  - default ioport/custom ioport

Changes from v19:

  - use qemu_log_mask instead of fprintf
  - add CONFIG_PVPANIC


Christian Borntraeger (1):
  Wire up disabled wait a panicked event on s390

Hu Tao (6):
  add a new runstate: RUN_STATE_GUEST_PANICKED
  add a new qevent: QEVENT_GUEST_PANICKED
  introduce a new qom device to deal with panicked event
  pvpanic: pass configurable ioport to seabios
  pvpanic: add document of pvpanic
  pvpanic: create pvpanic by default for machine 1.5

 QMP/qmp-events.txt                 |  14 ++++
 default-configs/i386-softmmu.mak   |   1 +
 default-configs/x86_64-softmmu.mak |   1 +
 docs/specs/pvpanic.txt             |  39 ++++++++++
 hw/i386/pc_piix.c                  |  16 ++++-
 hw/i386/pc_q35.c                   |  15 +++-
 hw/misc/Makefile.objs              |   2 +
 hw/misc/pvpanic.c                  | 144 +++++++++++++++++++++++++++++++++++++
 hw/nvram/fw_cfg.c                  |   8 ++-
 include/hw/i386/pc.h               |   3 +
 include/hw/nvram/fw_cfg.h          |   2 +
 include/monitor/monitor.h          |   1 +
 include/sysemu/sysemu.h            |   1 +
 monitor.c                          |   1 +
 qapi-schema.json                   |   5 +-
 qmp.c                              |   3 +-
 target-s390x/kvm.c                 |  17 ++++-
 vl.c                               |  13 +++-
 18 files changed, 274 insertions(+), 12 deletions(-)
 create mode 100644 docs/specs/pvpanic.txt
 create mode 100644 hw/misc/pvpanic.c

-- 
1.8.1.4

             reply	other threads:[~2013-04-19  7:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19  7:06 Hu Tao [this message]
2013-04-19  7:06 ` [Qemu-devel] [PATCH v20 1/7] add a new runstate: RUN_STATE_GUEST_PANICKED Hu Tao
2013-04-19  7:06 ` [Qemu-devel] [PATCH v20 2/7] add a new qevent: QEVENT_GUEST_PANICKED Hu Tao
2013-04-19  7:06 ` [Qemu-devel] [PATCH v20 3/7] introduce a new qom device to deal with panicked event Hu Tao
2013-04-19  7:06 ` [Qemu-devel] [PATCH v20 4/7] pvpanic: pass configurable ioport to seabios Hu Tao
2013-04-24 16:34   ` Markus Armbruster
2013-04-25  2:33     ` Hu Tao
2013-04-24 16:35   ` Markus Armbruster
2013-04-25  5:43     ` Hu Tao
2013-04-25 12:59       ` Markus Armbruster
2013-04-19  7:06 ` [Qemu-devel] [PATCH v20 5/7] pvpanic: add document of pvpanic Hu Tao
2013-04-19  7:06 ` [Qemu-devel] [PATCH v20 6/7] pvpanic: create pvpanic by default for machine 1.5 Hu Tao
2013-04-24 16:33   ` Markus Armbruster
2013-04-25  2:33     ` Hu Tao
2013-04-19  7:06 ` [Qemu-devel] [PATCH v20 7/7] Wire up disabled wait a panicked event on s390 Hu Tao

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=cover.1366354934.git.hutao@cn.fujitsu.com \
    --to=hutao@cn.fujitsu.com \
    --cc=qemu-devel@nongnu.org \
    /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).