xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ijc@hellion.org.uk>
To: Keir Fraser <keir@xen.org>
Cc: "Philippe.Simonet@swisscom.com" <Philippe.Simonet@swisscom.com>,
	"599161@bugs.debian.org" <599161@bugs.debian.org>,
	"mrsanna1@gmail.com" <mrsanna1@gmail.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: #599161: Xen debug patch for the "clock shifts by 50 minutes" bug.
Date: Thu, 08 Nov 2012 15:28:44 +0100	[thread overview]
Message-ID: <1352384924.12977.103.camel@hastur.hellion.org.uk> (raw)
In-Reply-To: <CCC15BF9.51B87%keir@xen.org>

On Thu, 2012-11-08 at 12:54 +0000, Keir Fraser wrote:
> On 08/11/2012 11:43, "Ian Campbell" <ijc@hellion.org.uk> wrote:
> 
> >>> I'll leave this to Keir (who wrote the debugging patch) to answer but it
> >>> looks to me like it should be useful!
> >> 
> >> I'm scratching my head. plt_wrap is earlier than plt_now, which should be
> >> impossible.
> > 
> > impossible due to guarantees made by the h/w or by construction in Xen.
> 
> That's a question, right? 

Yes, sorry.

> By construction in Xen.
> 
> > There appears to be a certain amount of hardware-specificness to the
> > issue -- so I'm wondering if maybe there are some platforms whose tsc is
> > not as monotonically increasing as it needs to be...
> 
> plt_* timestamps are not derived from TSC at all.

I see, rather it is derived from the platform_timesource which could be
HPET, pmtimer, pit etc but in this case (according to the provided xm
dmesg) appears to be a 14MHz HPET.

So I guess s/tsc/HPET/ in my original thought...

> >>  plt_stamp64 oddly has low 32 bits identical to new_stamp. That
> >> seems very very improbable!
> > 
> > Does this code run on all cpus or just one? Is it always the same one?
> 
> Always cpu0.

So it's not cross cpu drift then.

Ian.

  reply	other threads:[~2012-11-08 14:28 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1352375011.12977.95.camel@hastur.hellion.org.uk>
2012-11-08 12:54 ` #599161: Xen debug patch for the "clock shifts by 50 minutes" bug Keir Fraser
2012-11-08 14:28   ` Ian Campbell [this message]
2012-11-08 14:34     ` Keir Fraser
     [not found] <CAE17a0XdxhaoCZaDDT6RXm1DPnabf2hWXAnzU5NukHeXX45grA@mail.gmail.com>
     [not found] ` <CCCD845A.44DB0%keir.xen@gmail.com>
     [not found]   ` <CAE17a0Xit58cLiJ+pE7uKuCDq3Xn+7-5+iDpV2+5S+TX3yuT+Q@mail.gmail.com>
2012-11-26 10:20     ` Jan Beulich
2012-11-26 10:28       ` Mauro
2012-11-26 10:40         ` Ian Campbell
2012-11-26 12:18           ` Jan Beulich
2012-11-26 13:08             ` Philippe.Simonet
2012-11-26 14:15               ` Sylvain Munaut
2012-11-26 14:29               ` Jan Beulich
2012-11-07 10:10 Philippe.Simonet
2012-11-07 13:22 ` Ian Campbell
2012-11-07 17:40   ` Keir Fraser
2012-11-08  9:39     ` Jan Beulich
2012-11-08 10:38       ` Keir Fraser
2012-11-08 13:53         ` Jan Beulich
2012-11-08 14:04           ` Keir Fraser
2012-11-08 13:47       ` Philippe.Simonet
2012-11-08 14:29         ` Ian Campbell
2012-11-08 15:21         ` Mauro
     [not found]         ` <1352384968.12977.104.camel@hastur.hellion.org.uk>
2012-11-09  9:05           ` Philippe.Simonet
     [not found]           ` <FF93AF260AC2BB499A119CC65B092CF73151901D@sg000713.corproot.net>
2012-11-09  9:47             ` Jan Beulich
2012-11-09  9:54               ` Mauro
2012-11-13 10:14             ` Jan Beulich
2012-11-08 16:45       ` Tim Deegan
2012-11-08 16:53         ` Keir Fraser
2012-11-08 11:43     ` Ian Campbell
2012-11-08 14:20     ` Keir Fraser
2012-11-07 17:07 ` Jan Beulich
  -- strict thread matches above, loose matches on Subject: below --
2012-10-26 12:59 Ian Campbell
2012-10-26 18:25 ` Mauro
     [not found] ` <CAE17a0WfpKHxN=3iF6F+P0nT4UbyF9Lbpm8R5+JJEquQOmudXw@mail.gmail.com>
2012-10-26 18:40   ` Ian Campbell

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=1352384924.12977.103.camel@hastur.hellion.org.uk \
    --to=ijc@hellion.org.uk \
    --cc=599161@bugs.debian.org \
    --cc=Philippe.Simonet@swisscom.com \
    --cc=keir@xen.org \
    --cc=mrsanna1@gmail.com \
    --cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).