linux-kernel - Re: [PATCH] x86: enable hpet=force for AMD SB400

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 11 May 2008 11:03:16 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Alistair John Strachan <alistair@...zero.co.uk>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	andreas.herrmann3@....com, mingo@...e.hu, hpa@...or.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: enable hpet=force for AMD SB400

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 ???

Thanks,

	tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/