[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F8E8E3D.8040707@cn.fujitsu.com>
Date: Wed, 18 Apr 2012 17:49:49 +0800
From: zhangyanfei <zhangyanfei@...fujitsu.com>
To: Avi Kivity <avi@...hat.com>
CC: mtosatti@...hat.com, ebiederm@...ssion.com, luto@....edu,
joerg.roedel@....com, dzickus@...hat.com,
paul.gortmaker@...driver.com, gregkh@...e.de,
ludwig.nussel@...e.de, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, kexec@...ts.infradead.org
Subject: Re: [PATCH 0/4] Export offsets of VMCS fields as note information
for kdump
于 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
--
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/
Powered by blists - more mailing lists