From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: Gleb Natapov <gleb@redhat.com>, kvm list <kvm@vger.kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH] kvm: notify host when guest panicked
Date: Tue, 12 Jun 2012 09:49:28 +0200 [thread overview]
Message-ID: <4FD6F488.7090303@de.ibm.com> (raw)
In-Reply-To: <4FD6E5EC.3090802@cn.fujitsu.com>
>> We have three solutions to implement this feature:
>> 1. use vmcall
>> 2. use I/O port
>> 3. use virtio-serial.
>
>> We have decided to avoid touching hypervisor. The reason why I choose
>> choose the I/O port is:
>> 1. it is easier to implememt
>> 2. it does not depend any virtual device
>> 3. it can work when startint the kernel
Havent looked deeply into that, butz wouldnt kvm_hypercall0 also fulfill all of these
points? You just have to define the number for each architecture and then it should be
possible to write a simple panic driver that works on all architectures.
>> --- a/include/linux/kvm_para.h
>> +++ b/include/linux/kvm_para.h
>> @@ -20,6 +20,14 @@
>> #define KVM_HC_FEATURES 3
>> #define KVM_HC_PPC_MAP_MAGIC_PAGE 4
>>
>> +#define KVM_PV_PORT (0x505UL)
>> +
ignoring the above, shouldnt a port number go into an architecture specific file?
Christian
next prev parent reply other threads:[~2012-06-12 7:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 6:46 [Qemu-devel] [PATCH] kvm: notify host when guest panicked Wen Congyang
2012-05-21 6:49 ` [Qemu-devel] [PATCH 1/3] start vm after reseting it Wen Congyang
[not found] ` <20120530161720.7c9b88b9@doriath.home>
2012-06-12 7:23 ` Wen Congyang
2012-06-13 6:54 ` Wen Congyang
2012-05-21 6:50 ` [Qemu-devel] [PATCH 2/3] update linux headers Wen Congyang
2012-05-21 6:50 ` [Qemu-devel] [PATCH 3/3] deal with guest panicked event Wen Congyang
2012-05-22 11:32 ` Jan Kiszka
[not found] ` <20120530162314.1e9e4d3c@doriath.home>
2012-06-12 6:55 ` Wen Congyang
2012-06-12 12:35 ` Luiz Capitulino
2012-06-12 12:40 ` Daniel P. Berrange
2012-06-12 13:21 ` Luiz Capitulino
2012-06-12 13:29 ` Paolo Bonzini
2012-06-13 7:02 ` Wen Congyang
2012-06-13 7:53 ` Paolo Bonzini
2012-06-13 8:00 ` Wen Congyang
2012-06-12 6:47 ` [Qemu-devel] [PATCH] kvm: notify host when guest panicked Wen Congyang
2012-06-12 7:49 ` Christian Borntraeger [this message]
2012-06-12 8:07 ` Wen Congyang
2012-06-12 8:26 ` Wen Congyang
2012-06-12 9:49 ` Gleb Natapov
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=4FD6F488.7090303@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.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 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).