[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20120710.102832.104908620.d.hatayama@jp.fujitsu.com>
Date: Tue, 10 Jul 2012 10:28:32 +0900 (JST)
From: HATAYAMA Daisuke <d.hatayama@...fujitsu.com>
To: zhangyanfei@...fujitsu.com
Cc: avi@...hat.com, mtosatti@...hat.com, dzickus@...hat.com,
luto@....edu, kvm@...r.kernel.org, joerg.roedel@....com,
kexec@...ts.infradead.org, linux-kernel@...r.kernel.org,
paul.gortmaker@...driver.com, ludwig.nussel@...e.de,
ebiederm@...ssion.com, gregkh@...uxfoundation.org
Subject: Re: [PATCH v4 2/3] KVM-INTEL: Add new module vmcsinfo-intel to
fill VMCSINFO
From: Yanfei Zhang <zhangyanfei@...fujitsu.com>
Subject: [PATCH v4 2/3] KVM-INTEL: Add new module vmcsinfo-intel to fill VMCSINFO
Date: Wed, 4 Jul 2012 18:05:19 +0800
>
> Besides, this patch also exports vmcs revision identifier via
> /sys/devices/system/cpu/vmcs_id and offsets of fields via
> /sys/devices/system/cpu/vmcs/.
I think /sys/devices/system/cpu/vmcs/id is more natural, which also
belongs to vmcs.
<cut>
> +/*
> + * vmcs field offsets.
> + */
> +static struct vmcsinfo {
> + u32 vmcs_revision_id;
> + u16 vmcs_field_to_offset_table[HOST_RIP + 1];
> +} vmcsinfo;
This is what I said previously. HOST_RIP is 0x00006c16 => 27670. This
means sizeof (struct vmcsinfo) => 55346 bytes == 54 kbytes. But
actually exported fields are only 153, so 4 + 2 * 153 => 310 bytes are
enough.
How about getting the number of attributes from vmcs_attrs array? I
guess this is exactly the number of vmcs fields exported; here 153.
Thanks.
HATAYAMA, Daisuke
--
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