From: Andreas Herrmann <andreas.herrmann3@amd.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Alistair John Strachan <alistair@devzero.co.uk>,
Andrew Morton <akpm@linux-foundation.org>,
mingo@elte.hu, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: enable hpet=force for AMD SB400
Date: Tue, 24 Jun 2008 18:00:41 +0200 [thread overview]
Message-ID: <20080624160041.GB4167@alberich.amd.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0805111059190.3197@apollo.tec.linutronix.de>
On Sun, May 11, 2008 at 11:03:16AM +0200, Thomas Gleixner wrote:
> On Sun, 11 May 2008, Alistair John Strachan wrote:
> > > Well we don't have to auto-enable the hpet. Simply adding a loud "you
> > > should try the hpet=force option" printk would help a lot of people.
> >
> > I'm a bit confused about the policy here: if we look at the Intel chipset
> > overrides for HPET, they conditionally enable the HPET _without_ the
> > hpet=force option if you have a chipset on the whitelist.
> >
> > If Intel can do this on their chipsets, why is this not being done for the ATI
> > chipsets for which (presumably) AMD have specs?
>
> Well, we have no confirmation for the correctness of the non Intel
> quirks so far. I'm happy to move them into unconditional mode once
> AMD/ATI/NVidia tell us that the HPET is indeed discoverable this way.
>
> > One thing I'd considered was that HPET isn't actually used very often on Intel
> > chipsets because on most recent Intel CPUs the TSC is stable, but I think
>
> Well, stable except for the C-States. We still need a backup clock
> source as TSC is stopping in C3.
>
> > either the Intel quirk should be consistent with the hpet=force usage,
> > or "known correct" HPET overrides should just always be applied.
>
> That's what we do. We have "known correct" for Intel and those which
> work on the patch submitters box w/o confirmation of the
> correctness. I guess the SB400 one can move into the "is correct"
> category, Andreas ???
Sorry for the late reply, but I had to look for the spec in the first
place ;-) and I have done some coding and testing since then.
(Well, the patch was written as a quick hack to get HPET working on my
private laptop.)
The point is that at least some revisions of IXP400/IXP450 have indeed
hardware issues regarding HPET. Thus HPET works only for certain
chip revisions.
Currently I am internally discussing whether it makes sense to enable
(and properly configure) HPET for those chipset revisions.
BTW, if outcome of this discussion is that HPET on IXP400/IXP450
shouldn't be used then IMHO a quirk is needed to reliably disable it.
I.e. disable it even if a system provides an ACPI HPET table.
Thanks for your patience.
Regards,
Andreas
next prev parent reply other threads:[~2008-06-24 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 9:49 Andreas Herrmann
2008-05-09 23:37 ` Andrew Morton
2008-05-09 23:42 ` Thomas Gleixner
2008-05-09 23:55 ` Andrew Morton
2008-05-10 0:02 ` Thomas Gleixner
2008-05-10 20:40 ` Thomas Gleixner
2008-05-11 3:02 ` Alistair John Strachan
2008-05-11 9:03 ` Thomas Gleixner
2008-06-24 16:00 ` Andreas Herrmann [this message]
2008-07-04 18:55 ` Andreas Herrmann
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=20080624160041.GB4167@alberich.amd.com \
--to=andreas.herrmann3@amd.com \
--cc=akpm@linux-foundation.org \
--cc=alistair@devzero.co.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®