mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Nix <nix@esperi.org.uk>
Cc: Artur Skawina <art.08.09@gmail.com>,
	Venkatesh Pallipadi <venki@google.com>,
	Damien Wyart <damien.wyart@free.fr>,
	John Drescher <drescherjm@gmail.com>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (HPET)
Date: Tue, 14 Sep 2010 12:09:57 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1009141207310.2416@localhost6.localdomain6> (raw)
In-Reply-To: <alpine.LFD.2.00.1009101022400.2477@localhost6.localdomain6>

On Fri, 10 Sep 2010, Thomas Gleixner wrote:
> On Fri, 10 Sep 2010, Nix wrote:
> > 
> > I suspect current_clocksource doesn't do what we think it does, or the
> > clocksource and 'clock event device' are not the same.)
> 
> Right, they are not the same. clocksource provides us a read out
> device for timekeeping (usually a simple increasing counter). clock
> event device is used to generate timer interrupts.
> 
> HPET provides both functionalities.
> 
> The patch you bisected is affecting the clock events part of the
> HPET. So yes, it's not a clock source problem.

Another question. If you add hpet=verbose (or revert that commit) does
the printk_once in hpet_set_next_event() show up in dmesg ?

    "hpet: compare register read back failed."

Thanks,

	tglx

  parent reply	other threads:[~2010-09-14 10:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-05  0:51 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (ACPI idle?) Nix
2010-09-06  5:32 ` Damien Wyart
2010-09-06 20:27   ` Nix
2010-09-07  5:36     ` Damien Wyart
2010-09-08 21:24   ` Nix
2010-09-08 21:35     ` John Drescher
2010-09-08 22:25       ` Nix
2010-09-09 22:34     ` [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (HPET) Nix
2010-09-09 23:44       ` John Drescher
2010-09-09 23:57         ` Nix
2010-09-10  0:08           ` John Drescher
2010-09-10  0:14             ` John Drescher
2010-09-10  0:59       ` Artur Skawina
2010-09-10  5:36         ` Damien Wyart
2010-09-10  7:42         ` Nix
2010-09-10  7:47           ` Damien Wyart
2010-09-10  8:37           ` Thomas Gleixner
2010-09-10  9:41             ` Jiri Slaby
2010-09-10 13:22               ` Artur Skawina
2010-09-10 20:13                 ` Nix
2010-09-10 20:12               ` Nix
2010-09-14 10:09             ` Thomas Gleixner [this message]
2010-09-14 20:17               ` Nix
2010-09-14 22:18                 ` Thomas Gleixner
2010-09-14 22:23                 ` Artur Skawina

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=alpine.LFD.2.00.1009141207310.2416@localhost6.localdomain6 \
    --to=tglx@linutronix.de \
    --cc=art.08.09@gmail.com \
    --cc=damien.wyart@free.fr \
    --cc=drescherjm@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nix@esperi.org.uk \
    --cc=suresh.b.siddha@intel.com \
    --cc=venki@google.com \
    /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
all inboxes | Powered by JetHome®