| 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
| ||
|
Message-ID: <4D6BA377.8070305@redhat.com> Date: Mon, 28 Feb 2011 15:30:31 +0200 From: Avi Kivity <avi@...hat.com> To: Glauber Costa <glommer@...hat.com> CC: kvm@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] expose kvmclock upper msr set. On 02/28/2011 03:30 PM, Avi Kivity wrote: > On 02/28/2011 03:24 PM, Glauber Costa wrote: >> On Sun, 2011-02-27 at 14:16 +0200, Avi Kivity wrote: >> > On 02/23/2011 07:44 PM, Glauber Costa wrote: >> > > We've been supporting kvmclock MSRs in the 0x4b564d00-0x4b564dff >> range >> > > for a while now, but we're not exposing it yet, meaning nobody >> is using it. >> > > This simple patch takes care of that. >> > >> > We're exposing them via KVM_GET_SUPPORTED_CPUID, leaf >> KVM_CPUID_FEATURES. >> > >> Our userspace does not really use it, and rely on the capability list. >> Historically, we've been relying on the capabilities mechanism to >> indicate what exists and what does not. > > Yes. I believe this bit marked the change point. > > Anyway, it's exposed, and it's a lot better for userspace to make use > of KVM_GET_SUPPORTED_CPUID since it will work on more kernels. > btw, it should work with -cpu host as well, no? -- 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