[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101126104047.GA9798@elte.hu>
Date: Fri, 26 Nov 2010 11:40:47 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Jeremy Fitzhardinge <jeremy@...p.org>
Cc: "H. Peter Anvin" <hpa@...or.com>,
"Xen-devel@...ts.xensource.com" <Xen-devel@...ts.xensource.com>,
kvm-devel <kvm@...r.kernel.org>,
Glauber Costa <glommer@...hat.com>,
the arch/x86 maintainers <x86@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Virtualization <virtualization@...ts.linux-foundation.org>,
Olivier Hanesse <olivier.hanesse@...il.com>,
Avi Kivity <avi@...hat.com>,
Eelco Dolstra <e.dolstra@...elft.nl>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] x86/pvclock-xen: zero last_value on resume
* Jeremy Fitzhardinge <jeremy@...p.org> wrote:
> On 10/26/2010 09:59 AM, Jeremy Fitzhardinge wrote:
> >
> > If the guest domain has been suspend/resumed or migrated, then the
> > system clock backing the pvclock clocksource may revert to a smaller
> > value (ie, can be non-monotonic across the migration/save-restore).
> > Make sure we zero last_value in that case so that the domain
> > continues to see clock updates.
>
> Ping? Looks like this fell through the gaps.
Does not apply cleanly here - mind resending the latest version?
Thanks,
Ingo
--
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