public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andreas Herrmann <andreas.herrmann3@amd.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, Mark Hounschell <markh@compro.net>,
	Borislav Petkov <borislav.petkov@amd.com>
Subject: Re: [PATCH 0/3] x86: dish of assorted hpet patches
Date: Sun, 22 Feb 2009 18:04:40 +0100	[thread overview]
Message-ID: <20090222170440.GA8343@elte.hu> (raw)
In-Reply-To: <20090220230729.GK4834@alberich.amd.com>


* Andreas Herrmann <andreas.herrmann3@amd.com> wrote:

> - to print HPET registers during setup,
> - to fix a real issue with HZ_1000 kernels on an SB400 system
>  (and to potentially fix a similar issue with SB600).
> 
> Tested on ICH7 and on AMD SB400, AMD SB600.

applied to tip:timers/hpet, thanks Andreas!

Btw, maybe the HZ_1000 bugfix could be the fix for a weirdness 
i'm seeing very rarely on one of my testsystems:

[    8.850706] bus: 'pci': driver_probe_device: matched device 0000:04:00.0 with driver e1000e
[    8.850706] bus: 'pci': really_probe: probing driver e1000e with device 0000:04:00.0
[  177.308165] e1000e 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[  177.668182] e1000e 0000:04:00.0: setting latency timer to 64

there's almost 3 minutes between those lines printed, although 
it should have taken milliseconds!

	Ingo

      parent reply	other threads:[~2009-02-22 17:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20 23:07 [PATCH 0/3] x86: dish of assorted hpet patches Andreas Herrmann
2009-02-20 23:09 ` [PATCH 1/3] x86: hpet: print HPET registers during setup (if hpet=verbose is used) Andreas Herrmann
2009-02-20 23:10 ` [PATCH 2/3] x86: hpet: provide separate functions to stop and start the counter Andreas Herrmann
2009-02-20 23:16 ` [PATCH 3/3] x86: hpet: stop HPET_COUNTER when programming periodic mode Andreas Herrmann
2009-02-24  6:25   ` Andreas Herrmann
2009-02-22 17:04 ` Ingo Molnar [this message]

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=20090222170440.GA8343@elte.hu \
    --to=mingo@elte.hu \
    --cc=andreas.herrmann3@amd.com \
    --cc=borislav.petkov@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markh@compro.net \
    --cc=tglx@linutronix.de \
    /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