Re: [PATCH 0/4] Export offsets of VMCS fields as note information for kdump

From: zhangyanfei <zhangyanfei@cn.fujitsu.com>
To: Avi Kivity <avi@redhat.com>
Cc: dzickus@redhat.com, luto@mit.edu, gregkh@suse.de,
	kvm@vger.kernel.org, joerg.roedel@amd.com, mtosatti@redhat.com,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	paul.gortmaker@windriver.com, ludwig.nussel@suse.de,
	ebiederm@xmission.com
Subject: Re: [PATCH 0/4] Export offsets of VMCS fields as note information for kdump
Date: Wed, 18 Apr 2012 17:49:49 +0800	[thread overview]
Message-ID: <4F8E8E3D.8040707@cn.fujitsu.com> (raw)
In-Reply-To: <4F8E7A5B.5030904@redhat.com>

于 2012年04月18日 16:24, Avi Kivity 写道:
> On 04/18/2012 10:30 AM, zhangyanfei wrote:
>>>
>>> Okay.  Do you expect it to help in debugging the crash?  Did you have
>>> cases where it would help?
>>>
>>
>> Yes, I do expect it to help in debugging the crash.
>> Looking into host machine's crash dump, if we figure out the fact that the crash
>> had happend when some host's resource was requested and used by some guset machine.
>> Then, we surely want to look into the situation from guest machine's view.
>>
>>
> 
> What type of resource?  Can you give an example?
> 
Sorry. No concrete example for now.

We are developing this on a conservative policy and I have put the vmcs processing
in a new module in patch set v2 as you required. The new module is auto-loaded when
the vmx cpufeature is detected and it depends on module kvm-intel. Loading and unloading
this module will have no side effect on the running guests.

And one thing I have to stress is that, we can see guest image as crash dump from
guest machine's view if we have the vmcsinfo, this itself is useful.

Thanks
Zhang Yanfei

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec