xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: Tim Deegan <tim@xen.org>, Jan Beulich <JBeulich@suse.com>
Cc: Ian Campbell <ijc@hellion.org.uk>,
	Philippe.Simonet@swisscom.com, 599161@bugs.debian.org,
	mrsanna1@gmail.com, xen-devel@lists.xen.org
Subject: Re: #599161: Xen debug patch for the "clock shifts by 50 minutes" bug.
Date: Thu, 08 Nov 2012 16:53:29 +0000	[thread overview]
Message-ID: <CCC19409.51BE9%keir@xen.org> (raw)
In-Reply-To: <20121108164559.GK76638@ocelot.phlegethon.org>

On 08/11/2012 16:45, "Tim Deegan" <tim@xen.org> wrote:

>>> I wonder whether the overflow handling should just be removed, or made
>>> conditional on a command-line parameter, or on the 32-bit platform counter
>>> being at least somewhat likely to overflow before a softirq occurs -- it
>>> seems lots of systems are using 14MHz HPET, and that gives us a couple of
>>> minutes for the plt_overflow softirq to do its work before overflow occurs.
>>> I think we would notice that outage in other ways. :)
>> 
>> Iirc we added this for a good reason - to cover the, however
>> unlikely, event of Xen running for very long without preemption.
>> Presumably most of the cases got fixed meanwhile, and indeed
>> a wraparound time on the order of minutes should make this
>> superfluous, but as the case here shows that code did spot a
>> severe anomaly (whatever that may turn out to be).
> 
> ISTR when this code went in we were dealing with a timer that had a
> period of about 4 seconds (ACPI PMTIMER?).  It might well be OTT for the
> HPET, but if there's something weird going on I'd like to track it down
> while we have some sort of a handle on it.

It must have been the PMTIMER. It's the only counter narrower than 32 bits
(legacy PIT we simulate as a 32-bit counter behind the scenes).

 -- Keir

  reply	other threads:[~2012-11-08 16:53 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-07 10:10 #599161: Xen debug patch for the "clock shifts by 50 minutes" bug 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 [this message]
2012-11-08 11:43     ` Ian Campbell
2012-11-08 14:20     ` Keir Fraser
2012-11-07 17:07 ` Jan Beulich
     [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
     [not found] <1352375011.12977.95.camel@hastur.hellion.org.uk>
2012-11-08 12:54 ` Keir Fraser
2012-11-08 14:28   ` Ian Campbell
2012-11-08 14:34     ` Keir Fraser
  -- 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=CCC19409.51BE9%keir@xen.org \
    --to=keir@xen.org \
    --cc=599161@bugs.debian.org \
    --cc=JBeulich@suse.com \
    --cc=Philippe.Simonet@swisscom.com \
    --cc=ijc@hellion.org.uk \
    --cc=mrsanna1@gmail.com \
    --cc=tim@xen.org \
    --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).