KERNEL_GS_BASE, true);
> @@ -7265,6 +7270,10 @@ static void __exit vmx_exit(void)
> free_page((unsigned long)vmx_io_bitmap_b);
> free_page((unsigned long)vmx_io_bitmap_a);
>
> +#ifdef CONFIG_KEXEC
> + crash_clear_loaded_vmcss = NULL;
> +#endif
> +
>
exactly the number of vmcs fields exported; here 153.
Thanks.
HATAYAMA, Daisuke
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Wen Congyang
Subject: Re: [PATCH v4 2/3] KVM-INTEL: Add new module vmcsinfo-intel to fill
VMCSINFO
Date: Fri, 6 Jul 2012 16:25:23 +0800
> At 07/06/2012 04:04 PM, HATAYAMA Daisuke Wrote:
>> From: Yanfei Zhang
>> Subject: [PATCH v4 2/3] KVM-INTEL: Add new module vmcsinf
From: Wen Congyang
Subject: Re: [PATCH v4 2/3] KVM-INTEL: Add new module vmcsinfo-intel to fill
VMCSINFO
Date: Fri, 6 Jul 2012 16:25:23 +0800
> At 07/06/2012 04:04 PM, HATAYAMA Daisuke Wrote:
>> From: Yanfei Zhang
>> Subject: [PATCH v4 2/3] KVM-INTEL: Add new module vmcsinf
evices/cpu/cpu1/vmcs/0800
...
/sys/devices/cpu/cpuN/vmcs/0800
Also, processing of vmcsinfo initialization needs to be done per cpu,
and can be triggered when cpu is added not when kvm module is loaded.
Thanks.
HATAYAMA, Daisuke
--
To unsubscribe from this list: send the line "unsubscribe kvm"
T_RIP + 1];
HOST_RIP is so large that this array becomes large. Also there are
unused elements in this array because field encoding is not indexed
constantly.
Instead, how about defining the numbr of vmcs fields, 152?, as a
specific constant, indexing each fields using integers and newly
preparing i
fields are different each
other.
- Field size remains 8 bytes, 16 bytes, 32 bytes even on vmcs region.
- Each field is 8 byte alighed on vmcs region.
- Some fields may be big endition on vmcs region.
- We found this fact under development. We give up if the data is
modified mo
From: Avi Kivity
Subject: Re: [PATCH 0/4] Export offsets of VMCS fields as note information for
kdump
Date: Thu, 19 Apr 2012 15:08:00 +0300
> On 04/19/2012 03:01 PM, HATAYAMA Daisuke wrote:
>> >> It would be not helpful for the qemu crash case you are concerned
>> >>
From: Avi Kivity
Subject: Re: [PATCH 0/4] Export offsets of VMCS fields as note information for
kdump
Date: Thu, 19 Apr 2012 14:31:56 +0300
> On 04/19/2012 02:27 PM, HATAYAMA Daisuke wrote:
>> >> The reason why we want to retrieve guest machine's memory image as
>> >
From: Avi Kivity
Subject: Re: [PATCH 0/4] Export offsets of VMCS fields as note information for
kdump
Date: Thu, 19 Apr 2012 13:42:42 +0300
> On 04/19/2012 01:36 PM, HATAYAMA Daisuke wrote:
>> From: Avi Kivity
>> Subject: Re: [PATCH 0/4] Export offsets of VMCS fields as n
bugger such as gdb and crash utility.
This is very useful. Please consider the situation where engineers are
forced to look into guest machine's memory image through qemu-kvm's
process core dump using gdb without any symbolic information. It's
very inefficient.
Thanks.
11 matches
Mail list logo
