- Subject: Re: [PATCH 0/4] Export offsets of VMCS fields as note information for kdump
- From: Avi Kivity <avi@xxxxxxxxxx>
- Date: Wed, 18 Apr 2012 14:56:39 +0300
- Cc: mtosatti@xxxxxxxxxx, ebiederm@xxxxxxxxxxxx, luto@xxxxxxx, joerg.roedel@xxxxxxx, dzickus@xxxxxxxxxx, paul.gortmaker@xxxxxxxxxxxxx, gregkh@xxxxxxx, ludwig.nussel@xxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, kvm@xxxxxxxxxxxxxxx, kexec@xxxxxxxxxxxxxxxxxxx
- In-reply-to: <4F8E8E3D.8040707@cn.fujitsu.com>
- References: <4F84E0DF.8040206@cn.fujitsu.com> <4F8D1F46.3090901@redhat.com> <4F8D4B4C.8070705@cn.fujitsu.com> <4F8D4D1C.4010400@redhat.com> <4F8E6DA5.8030503@cn.fujitsu.com> <4F8E7A5B.5030904@redhat.com> <4F8E8E3D.8040707@cn.fujitsu.com>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120329 Thunderbird/11.0.1
On 04/18/2012 12:49 PM, zhangyanfei wrote:
> >>
> >
> > 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.
Why is it useful? Without a concrete example, it's hard to justify the
code bloat.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[KVM ARM]
[KVM ia64]
[KVM ppc]
[Spice Development]
[Libvirt]
[Libvirt Users]
[Linux USB Devel]
[Video for Linux]
[Linux Audio Users]
[Photo]
[Yosemite News]
[Yosemite Photos]
[Linux Kernel]
[Linux SCSI]
[XFree86]