All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ijc@hellion.org.uk>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	Glauber Costa <glommer@redhat.com>,
	"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
	kvm-devel <kvm@vger.kernel.org>,
	Eelco Dolstra <e.dolstra@tudelft.nl>,
	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>
Subject: Re: [Xen-devel] Re: [PATCH] x86/pvclock-xen: zero last_value on resume
Date: Wed, 03 Nov 2010 12:46:34 +0000	[thread overview]
Message-ID: <1288788394.9309.2.camel@cthulhu.hellion.org.uk> (raw)
In-Reply-To: <95805e88-b6d5-4ae2-9351-9e458656cfb8@email.android.com>

On Wed, 2010-10-27 at 13:59 -0700, H. Peter Anvin wrote:
> I'll check it this evening when I'm at a working network again :(

Did this get applied? It seems to affect 2.6.32.x too
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602273) so can we tag
it for stable as well?

Thanks,
Ian.

> 
> "Jeremy Fitzhardinge" <jeremy@goop.org> wrote:
> 
> > On 10/26/2010 10:48 AM, Glauber Costa wrote:
> >> On Tue, 2010-10-26 at 09:59 -0700, 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.
> >>>
> >>> [ I don't know if kvm needs an analogous fix or not. ]
> >> After migration, save/restore, etc, we issue an ioctl where we tell
> >> the host the last clock value. That (in theory) guarantees
> >monotonicity.
> >>
> >> I am not opposed to this patch in any way, however.
> >
> >Thanks.
> >
> >HPA, do you want to take this, or shall I send it on?
> >
> >Thanks,
> >    J
> 

-- 
Ian Campbell

BOFH excuse #191:

Just type 'mv * /dev/null'.


WARNING: multiple messages have this Message-ID (diff)
From: Ian Campbell <ijc@hellion.org.uk>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
	kvm-devel <kvm@vger.kernel.org>, Dolstra <e.dolstra@tudelft.nl>,
	the arch/x86 maintainers <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Virtualization <virtualization@lists.linux-foundation.org>,
	Hanesse <olivier.hanesse@gmail.com>,
	Eelco, Olivier, Linux, Glauber Costa <glommer@redhat.com>,
	Avi Kivity <avi@redhat.com>
Subject: Re: Re: [PATCH] x86/pvclock-xen: zero last_value on resume
Date: Wed, 03 Nov 2010 12:46:34 +0000	[thread overview]
Message-ID: <1288788394.9309.2.camel@cthulhu.hellion.org.uk> (raw)
In-Reply-To: <95805e88-b6d5-4ae2-9351-9e458656cfb8@email.android.com>

On Wed, 2010-10-27 at 13:59 -0700, H. Peter Anvin wrote:
> I'll check it this evening when I'm at a working network again :(

Did this get applied? It seems to affect 2.6.32.x too
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602273) so can we tag
it for stable as well?

Thanks,
Ian.

> 
> "Jeremy Fitzhardinge" <jeremy@goop.org> wrote:
> 
> > On 10/26/2010 10:48 AM, Glauber Costa wrote:
> >> On Tue, 2010-10-26 at 09:59 -0700, 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.
> >>>
> >>> [ I don't know if kvm needs an analogous fix or not. ]
> >> After migration, save/restore, etc, we issue an ioctl where we tell
> >> the host the last clock value. That (in theory) guarantees
> >monotonicity.
> >>
> >> I am not opposed to this patch in any way, however.
> >
> >Thanks.
> >
> >HPA, do you want to take this, or shall I send it on?
> >
> >Thanks,
> >    J
> 

-- 
Ian Campbell

BOFH excuse #191:

Just type 'mv * /dev/null'.

WARNING: multiple messages have this Message-ID (diff)
From: Ian Campbell <ijc@hellion.org.uk>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
	kvm-devel <kvm@vger.kernel.org>, Dolstra <e.dolstra@tudelft.nl>,
	the arch/x86 maintainers <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Virtualization <virtualization@lists.linux-foundation.org>,
	Hanesse <olivier.hanesse@gmail.com>,
	Eelco, OlivierLinux, Glauber Costa <glommer@redhat.com>,
	Avi Kivity <avi@redhat.com>
Subject: Re: Re: [PATCH] x86/pvclock-xen: zero last_value on resume
Date: Wed, 03 Nov 2010 12:46:34 +0000	[thread overview]
Message-ID: <1288788394.9309.2.camel@cthulhu.hellion.org.uk> (raw)
In-Reply-To: <95805e88-b6d5-4ae2-9351-9e458656cfb8@email.android.com>

On Wed, 2010-10-27 at 13:59 -0700, H. Peter Anvin wrote:
> I'll check it this evening when I'm at a working network again :(

Did this get applied? It seems to affect 2.6.32.x too
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602273) so can we tag
it for stable as well?

Thanks,
Ian.

> 
> "Jeremy Fitzhardinge" <jeremy@goop.org> wrote:
> 
> > On 10/26/2010 10:48 AM, Glauber Costa wrote:
> >> On Tue, 2010-10-26 at 09:59 -0700, 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.
> >>>
> >>> [ I don't know if kvm needs an analogous fix or not. ]
> >> After migration, save/restore, etc, we issue an ioctl where we tell
> >> the host the last clock value. That (in theory) guarantees
> >monotonicity.
> >>
> >> I am not opposed to this patch in any way, however.
> >
> >Thanks.
> >
> >HPA, do you want to take this, or shall I send it on?
> >
> >Thanks,
> >    J
> 

-- 
Ian Campbell

BOFH excuse #191:

Just type 'mv * /dev/null'.

  parent reply	other threads:[~2010-11-03 13:26 UTC|newest]

Thread overview: 21+ 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 [this message]
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
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

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=1288788394.9309.2.camel@cthulhu.hellion.org.uk \
    --to=ijc@hellion.org.uk \
    --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=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.