From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Len Brown <lenb@kernel.org>, Mark Hounschell <markh@compro.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Alain Knaff <alain@knaff.lu>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Li, Shaohua" <shaohua.li@intel.com>
Subject: Re: [patch 2/4] x86: Do not use hpet MSI as clockevent broadcast device
Date: Thu, 14 Jan 2010 18:07:03 -0800 [thread overview]
Message-ID: <1263521223.16916.176.camel@localhost.localdomain> (raw)
In-Reply-To: <4B4FCC33.2010100@zytor.com>
On Thu, 2010-01-14 at 18:00 -0800, H. Peter Anvin wrote:
> On 01/14/2010 05:39 PM, Venkatesh Pallipadi wrote:
> > Current kernel uses hpet MSI interrupts as both percpu clockevent device
> > and also as clockevent broadcast device in place of IRQ0 timer.
> > There seems to be issues with HPET MSI usage on some platforms. So,
> > restrict it to be only used as a percpu clockevent device.
>
> Any ideas of which platforms? It would help avoiding "cargo cult
> programming" in the future.
>
> Other than that, I presume this is a .33 patch?
>
> -hpa
>
The problem reported by Mark has only been on (AMD) 790x series chip
sets.
I am not quite sure what the quick-fix for .33 would be.
- Either use dmi to stop using HPET MSI on this chipset
- or stop using HPET MSI altogether, until this complete patchset
provides a better alternative for .34.
I think it should be first option.
Thanks,
Venki
next prev parent reply other threads:[~2010-01-15 2:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 1:39 [patch 0/4] Only use HPET MSI timers on systems with deep C-state support Venkatesh Pallipadi
2010-01-15 1:39 ` [patch 1/4] acpi: acpi_cpu_soft_notify() not getting called on resume Venkatesh Pallipadi
2010-01-15 1:39 ` [patch 2/4] x86: Do not use hpet MSI as clockevent broadcast device Venkatesh Pallipadi
2010-01-15 2:00 ` H. Peter Anvin
2010-01-15 2:07 ` Pallipadi, Venkatesh [this message]
2010-01-15 1:40 ` [patch 3/4] clockevent: Add tick_check_fallback_timer to look for fallback timer Venkatesh Pallipadi
2010-01-15 1:40 ` [patch 4/4] x86: Adjust HPET MSI timer rating to work with tick_check_fallback_timer Venkatesh Pallipadi
2010-01-15 21:53 ` [patch 0/4] Only use HPET MSI timers on systems with deep C-state support Mark Hounschell
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=1263521223.16916.176.camel@localhost.localdomain \
--to=venkatesh.pallipadi@intel.com \
--cc=alain@knaff.lu \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=shaohua.li@intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
Powered by JetHome