From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
kvm-devel <kvm@vger.kernel.org>,
Glauber Costa <glommer@redhat.com>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Virtualization <virtualization@lists.linux-foundation.org>,
Olivier Hanesse <olivier.hanesse@gmail.com>,
Avi Kivity <avi@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Eelco Dolstra <e.dolstra@tudelft.nl>
Subject: Re: [PATCH] x86/pvclock-xen: zero last_value on resume
Date: Fri, 26 Nov 2010 11:40:47 +0100 [thread overview]
Message-ID: <20101126104047.GA9798__17280.1987770528$1290768274$gmane$org@elte.hu> (raw)
In-Reply-To: <4CEACFAB.90503@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.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
next prev parent reply other threads:[~2010-11-26 10:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 16:59 [PATCH] x86/pvclock-xen: zero last_value on resume Jeremy Fitzhardinge
2010-10-26 16:59 ` Jeremy Fitzhardinge
2010-10-26 17:48 ` Glauber Costa
2010-10-26 17:48 ` Glauber Costa
2010-10-27 18:53 ` [Xen-devel] " Jeremy Fitzhardinge
2010-10-27 18:53 ` Jeremy Fitzhardinge
2010-10-27 20:59 ` H. Peter Anvin
2010-10-27 20:59 ` H. Peter Anvin
2010-11-03 12:46 ` Ian Campbell
2010-11-03 12:46 ` Ian Campbell
2010-11-03 12:46 ` Ian Campbell
2010-11-03 12:46 ` Ian Campbell
2010-10-26 17:48 ` Glauber Costa
2010-11-22 20:16 ` Jeremy Fitzhardinge
2010-11-22 20:16 ` Jeremy Fitzhardinge
2010-11-26 10:40 ` Ingo Molnar [this message]
2010-11-26 10:40 ` Ingo Molnar
2010-11-26 10:40 ` Ingo Molnar
2010-11-26 22:29 ` Jeremy Fitzhardinge
2010-11-26 22:29 ` Jeremy Fitzhardinge
2010-11-26 22:29 ` Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2010-10-26 16:59 Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='20101126104047.GA9798__17280.1987770528$1290768274$gmane$org@elte.hu' \
--to=mingo@elte.hu \
--cc=Xen-devel@lists.xensource.com \
--cc=avi@redhat.com \
--cc=e.dolstra@tudelft.nl \
--cc=glommer@redhat.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olivier.hanesse@gmail.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.