* David Miller ([email protected]) wrote:
> From: Zachary Amsden <[email protected]>
> 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
