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: Wed, 16 Jun 2010 10:24:37 -0300 From: Glauber Costa <glommer@...hat.com> To: Zachary Amsden <zamsden@...hat.com> Cc: avi@...hat.com, mtosatti@...hat.com, kvm@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 04/17] Fix deep C-state TSC desynchronization On Mon, Jun 14, 2010 at 09:34:06PM -1000, Zachary Amsden wrote: > When CPUs with unstable TSCs enter deep C-state, TSC may stop > running. This causes us to require resynchronization. Since > we can't tell when this may potentially happen, we assume the > worst by forcing re-compensation for it at every point the VCPU > task is descheduled. can't we just compensate everytime check_tsc_unstable() is true? -- 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