From: Jan Kiszka <jan.kiszka@siemens.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: kvm list <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Avi Kivity <avi@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Gleb Natapov <gleb@redhat.com>
Subject: Re: [PATCH 5/6 v5] deal with guest panicked event accoring to -onpanic parameter
Date: Tue, 03 Jul 2012 08:45:29 +0200 [thread overview]
Message-ID: <4FF29509.3030909@siemens.com> (raw)
In-Reply-To: <4FF29482.6050206@cn.fujitsu.com>
On 2012-07-03 08:43, Wen Congyang wrote:
>> I'm not talking about changing the interface to the guest, I'm talking
>> about how to model it in QEMU. And that difference would be transparent
>> to the guest. I pointed you to examples like hw/kvm/clock.c.
>
> OK, I will read the code in hw/kvm/clock.c
Just to avoid confusion: That example is just good for a trivial
framework. It does vmstate saving, something you don't need as your
"device" is stateless. If you want to find out how to register PIO
ranges, also check e.g. hw/pcspk.c.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: Gleb Natapov <gleb@redhat.com>, kvm list <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Avi Kivity <avi@redhat.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH 5/6 v5] deal with guest panicked event accoring to -onpanic parameter
Date: Tue, 03 Jul 2012 08:45:29 +0200 [thread overview]
Message-ID: <4FF29509.3030909@siemens.com> (raw)
In-Reply-To: <4FF29482.6050206@cn.fujitsu.com>
On 2012-07-03 08:43, Wen Congyang wrote:
>> I'm not talking about changing the interface to the guest, I'm talking
>> about how to model it in QEMU. And that difference would be transparent
>> to the guest. I pointed you to examples like hw/kvm/clock.c.
>
> OK, I will read the code in hw/kvm/clock.c
Just to avoid confusion: That example is just good for a trivial
framework. It does vmstate saving, something you don't need as your
"device" is stateless. If you want to find out how to register PIO
ranges, also check e.g. hw/pcspk.c.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-07-03 6:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 6:55 [PATCH v5] kvm: notify host when the guest is panicked Wen Congyang
2012-06-27 6:57 ` [PATCH 1/6 v5] start vm after reseting it Wen Congyang
2012-06-27 6:58 ` [PATCH 2/6 v5] update linux headers Wen Congyang
2012-06-27 7:00 ` [PATCH 3/6 v5] add a new runstate: RUN_STATE_GUEST_PANICKED Wen Congyang
2012-06-27 7:01 ` [PATCH 4/6 v5] add a new qevent: QEVENT_GUEST_PANICKED Wen Congyang
2012-06-27 7:02 ` [PATCH 5/6 v5] deal with guest panicked event accoring to -onpanic parameter Wen Congyang
2012-06-27 14:39 ` Jan Kiszka
2012-06-28 1:15 ` Wen Congyang
2012-06-28 8:26 ` Jan Kiszka
2012-06-28 8:26 ` Jan Kiszka
2012-07-03 6:07 ` Wen Congyang
2012-07-03 6:07 ` [Qemu-devel] " Wen Congyang
2012-07-03 6:36 ` Jan Kiszka
2012-07-03 6:36 ` [Qemu-devel] " Jan Kiszka
2012-07-03 6:36 ` Jan Kiszka
2012-07-03 6:43 ` Wen Congyang
2012-07-03 6:43 ` [Qemu-devel] " Wen Congyang
2012-07-03 6:45 ` Jan Kiszka [this message]
2012-07-03 6:45 ` Jan Kiszka
2012-06-27 14:52 ` Cornelia Huck
2012-06-27 14:57 ` Daniel P. Berrange
2012-06-27 7:04 ` [PATCH 6/6 v5] deal with panicked event accoring to '-machine panic_action=action' Wen Congyang
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=4FF29509.3030909@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=berrange@redhat.com \
--cc=gleb@redhat.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=wency@cn.fujitsu.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.