linux-kernel - Re: [RFC PATCH 18/33] Subarch support for CPUID instruction

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] [day] [month] [year] [list]

Date:	Tue, 18 Jul 2006 14:00:25 -0700
From:	Chris Wright <chrisw@...s-sol.org>
To:	David Miller <davem@...emloft.net>
Cc:	zach@...are.com, arjan@...radead.org, chrisw@...s-sol.org,
	linux-kernel@...r.kernel.org, virtualization@...ts.osdl.org,
	xen-devel@...ts.xensource.com, jeremy@...p.org, ak@...e.de,
	akpm@...l.org, rusty@...tcorp.com.au, ian.pratt@...source.com,
	Christian.Limpach@...cam.ac.uk
Subject: Re: [RFC PATCH 18/33] Subarch support for CPUID instruction

* David Miller (davem@...emloft.net) wrote:
> From: Zachary Amsden <zach@...are.com>
> Date: Tue, 18 Jul 2006 04:33:52 -0700
> 
> > You really need a CPUID hook.  The instruction is non-virtualizable, and 
> > anything claiming to be a hypervisor really has to support masking and 
> > flattening the cpuid namespace for the instruction itself.  It is used 
> > in assembler code and very early in boot.  The alternative is injecting 
> > a bunch of Xen-specific code to filter feature bits into the i386 layer, 
> > which is both bad for Linux and bad for Xen - and was quite ugly in the 
> > last set of Xen patches.
> 
> Userspace will still see the full set of cpuid bits, since
> it can still execute cpuid unimpeded, is this ok?

Yup, it's for the kernel (things like systenter vs int 80 in vdso).

thanks,
-chris
-
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/