linux-kernel - Re: [PATCH 0/2 v3] kvm: notify host when guest panicked

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4F5DBC26.7060204@cn.fujitsu.com>
Date:	Mon, 12 Mar 2012 17:04:38 +0800
From:	Wen Congyang <wency@...fujitsu.com>
To:	Avi Kivity <avi@...hat.com>
CC:	kvm list <kvm@...r.kernel.org>, qemu-devel <qemu-devel@...gnu.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Daniel P. Berrange" <berrange@...hat.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Jan Kiszka <jan.kiszka@...mens.com>,
	Gleb Natapov <gleb@...hat.com>
Subject: Re: [PATCH 0/2 v3] kvm: notify host when guest panicked

At 03/09/2012 09:21 AM, Wen Congyang Wrote:
> At 03/08/2012 07:13 PM, Avi Kivity Wrote:
>> On 03/08/2012 09:57 AM, Wen Congyang wrote:
>>> We can know the guest is paniced when the guest runs on xen.
>>> But we do not have such feature on kvm.
>>>
>>> Another purpose of this feature is: management app(for example:
>>> libvirt) can do auto dump when the guest is crashed. If management
>>> app does not do auto dump, the guest's user can do dump by hand if
>>> he sees the guest is paniced.
>>>
>>> I touch the hypervisor instead of using virtio-serial, because
>>> 1. it is simple
>>> 2. the virtio-serial is an optional device, and the guest may
>>>    not have such device.
>>>
>>> Changes from v2 to v3:
>>> 1. correct spelling
>>>
>>> Changes from v1 to v2:
>>> 1. split up host and guest-side changes
>>> 2. introduce new request flag to avoid changing return values.
>>
>> I see no Documentation/ changes.

Do you have any other comments about this patch?

> 
> What shoude be writen into Documentation/? I read the documents under
> Documentation/virtual/kvm, not all KVM_EXIT_* are writen in api.txt.
> In this patch set, I introduce a new exit_reason: KVM_EXIT_GUEST_PANICKED,
> but I donot know where I should write.

What about this?

Thanks
Wen Congyang

> 
> Thanks
> Wen Congyang
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/