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
| ||
|
Date: Tue, 15 Jun 2010 11:44:38 +0300 From: Avi Kivity <avi@...hat.com> To: Zachary Amsden <zamsden@...hat.com> CC: mtosatti@...hat.com, glommer@...hat.com, kvm@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 13/17] Add TSC offset tracking On 06/15/2010 10:34 AM, Zachary Amsden wrote: > Track the last TSC offset set for each VM and ensure that the storing of > the offset and the reading of the TSC are never preempted by taking a > spinlock. > > Totally missing the point - tsc is per vcpu, why do we need per-vm tracking? -- 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