linux-kernel - Re: AMD X2 unsynced TSC fix?

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:	Sat, 28 Oct 2006 15:54:14 -0700
From:	thockin@...kin.org
To:	Vojtech Pavlik <vojtech@...e.cz>
Cc:	Lee Revell <rlrevell@...-job.com>, Andi Kleen <ak@...e.de>,
	Jiri Bohac <jbohac@...e.cz>,
	Luca Tettamanti <kronos.it@...il.com>,
	linux-kernel@...r.kernel.org, john stultz <johnstul@...ibm.com>
Subject: Re: AMD X2 unsynced TSC fix?

On Sat, Oct 28, 2006 at 09:57:39PM +0200, Vojtech Pavlik wrote:
> > > No we don't -- most BIOS still don't give us the HPET table 
> > > even when it is there in hardware. In the future this will change sure
> > > but people will still run a lot of older motherboards. 
> > 
> > I have exactly such a system (see thread "x86-64 with nvidia MCP51
> > chipset: kernel does not find HPET").  Is there anything at all I can do
> > to make the kernel see the HPET?  Can I try to guess the address?  BIOS
> > upgrade?
>  
> In most cases where the HPET is present but not reported, it's not
> configured. Usually, you need to write a chipset-specific register to
> configure the address.
> 
> Finding the register, finding some free MMIO space, writing the address
> to the register and telling the address to the kernel is enough.

Do we want to establish a precedent for chipsets that we can find the HPET
and configure ourselves?  Register them all as PCI quirks...
-
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/