lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FD9E574.90800@redhat.com>
Date:	Thu, 14 Jun 2012 16:21:56 +0300
From:	Avi Kivity <avi@...hat.com>
To:	zhangyanfei <zhangyanfei@...fujitsu.com>
CC:	mtosatti@...hat.com, ebiederm@...ssion.com, luto@....edu,
	Joerg Roedel <joerg.roedel@....com>, dzickus@...hat.com,
	paul.gortmaker@...driver.com, ludwig.nussel@...e.de,
	linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
	kexec@...ts.infradead.org, Greg KH <gregkh@...uxfoundation.org>
Subject: Re: [PATCH v2 5/5] Documentation: Add ABI entry for sysfs file vmcsinfo
 and vmcsinfo_maxsize

On 05/16/2012 10:57 AM, zhangyanfei wrote:
> We create two new sysfs files, vmcsinfo and vmcsinfo_maxsize. And
> here we add an Documentation/ABI entry for them.
> 
> 
> diff --git a/Documentation/ABI/testing/sysfs-kernel-vmcsinfo b/Documentation/ABI/testing/sysfs-kernel-vmcsinfo
> new file mode 100644
> index 0000000..adbf866
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-kernel-vmcsinfo
> @@ -0,0 +1,16 @@
> +What:		/sys/kernel/vmcsinfo
> +Date:		April 2012
> +KernelVersion:	3.4.0
> +Contact:	Zhang Yanfei <zhangyanfei@...fujitsu.com>
> +Description
> +		Shows physical address of VMCSINFO. VMCSINFO contains
> +		the VMCS revision identifier and encoded offsets of fields
> +		in VMCS data on Intel processors equipped with the VT
> +		extensions.
> +
> +What:		/sys/kernel/vmcsinfo_maxsize
> +Date:		April 2012
> +KernelVersion:	3.4.0
> +Contact:	Zhang Yanfei <zhangyanfei@...fujitsu.com>
> +Description
> +		Shows max size of VMCSINFO.
> 

This describes the cpu, so maybe /sys/devices/cpu is a better place for
these files.

Would it make sense to expose the actual fields?

that is, have /sys/devices/cpu/vmcs/0806 contain the offset of
GUEST_DS_SELECTOR.

-- 
error compiling committee.c: too many arguments to function


--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ