On Wed, May 16, 2012 at 12:50 AM, zhangyanfei <zhangyan...@cn.fujitsu.com> wrote: > > This patch set exports offsets of VMCS fields as note information for > kdump. We call it VMCSINFO. The purpose of VMCSINFO is to retrieve > runtime state of guest machine image, such as registers, in host > machine's crash dump as VMCS format. The problem is that VMCS internal > is hidden by Intel in its specification. So, we slove this problem > by reverse engineering implemented in this patch set. The VMCSINFO > is exported via sysfs to kexec-tools just like VMCOREINFO.
Perhaps I'm wrong, but this solution seems much, much more dynamic than it needs to be. The VMCS offsets aren't going to change between different boots on the same CPU, unless perhaps the microcode has been updated. So you can have the VMCS offset dumping be a manually-loaded module. Build a database mapping from (CPUID, microcode revision) -> (VMCSINFO). There's no need for anything beyond the (CPUID, microcode revision) to be put in the kdump, since your offline processing of a kdump can then look up the rest. It means you don't have to interact with the vmx module at all, and no extra modules or code have to be loaded on the millions of Linux machines that won't need the functionality. -- 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
