| 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: <4BCE41D2.5020005@redhat.com> Date: Tue, 20 Apr 2010 14:07:46 -1000 From: Zachary Amsden <zamsden@...hat.com> To: Jeremy Fitzhardinge <jeremy@...p.org> CC: Avi Kivity <avi@...hat.com>, Peter Zijlstra <peterz@...radead.org>, Glauber Costa <glommer@...hat.com>, kvm@...r.kernel.org, linux-kernel@...r.kernel.org, Marcelo Tosatti <mtosatti@...hat.com> Subject: Re: [PATCH 1/5] Add a global synchronization point for pvclock On 04/20/2010 09:42 AM, Jeremy Fitzhardinge wrote: > On 04/20/2010 11:54 AM, Avi Kivity wrote: > >> On 04/20/2010 09:23 PM, Jeremy Fitzhardinge wrote: >> >>> On 04/20/2010 02:31 AM, Avi Kivity wrote: >>> >>> >>>> btw, do you want this code in pvclock.c, or shall we keep it kvmclock >>>> specific? >>>> >>>> >>> I think its a pvclock-level fix. I'd been hoping to avoid having >>> something like this, but I think its ultimately necessary. >>> >>> >> Did you observe drift on Xen, or is this "ultimately" pointing at the >> future? >> > People are reporting weirdnesses that "clocksource=jiffies" apparently > resolves. Xen and KVM are faced with the same hardware constraints, and > it wouldn't surprise me if there were small measurable > non-monotonicities in the PV clock under Xen. May as well be safe. > Does the drift only occur on SMP VMs? -- 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