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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 14 Nov 2006 10:06:37 -0800
From:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
To:	"Andreas Mohr" <andi@...x01.fht-esslingen.de>
Cc:	"Len Brown" <lenb@...nel.org>, "Ingo Molnar" <mingo@...e.hu>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	<linux-kernel@...r.kernel.org>,
	"Van De Ven, Arjan" <arjan.van.de.ven@...el.com>
Subject: RE: CONFIG_NO_HZ: missed ticks, stall (keyb IRQ required) [2.6.18-rc4-mm1]

 

>-----Original Message-----
>From: Andreas Mohr [mailto:andi@...x01.fht-esslingen.de] 
>Sent: Tuesday, November 14, 2006 9:31 AM
>To: Pallipadi, Venkatesh
>Cc: Len Brown; Ingo Molnar; Andreas Mohr; Thomas Gleixner; 
>linux-kernel@...r.kernel.org; Van De Ven, Arjan
>Subject: Re: CONFIG_NO_HZ: missed ticks, stall (keyb IRQ 
>required) [2.6.18-rc4-mm1]
>
>Hi,
>
>On Tue, Nov 14, 2006 at 09:21:02AM -0800, Pallipadi, Venkatesh wrote:
>> >I belive that Venki has looked at some of the HPET 
>enumeration issues,
>> >and maybe he has some suggestions.  Is there an example system
>> >on-hand where we know Windows works and Linux does not?
>> >
>> 
>> There are two things that can be happening when OS does not 
>see HPET in
>> ACPI.
>> - BIOS did enable HPET in chipset and did not communicate it to OS.
>> - BIOS did nothing to enable HPET in chipset.
>
>I'm sure you've already seen
>http://semthex.freeflux.net/blog/archive/2006/10/21/hpet-to-be-
>or-not-to-be.html
>... or not?

Hmmm.. I hadn't seen this before..

>
>Hmm, hopefully it's easy to research where to enable HPET
>(if there is one at all!) on an el-cheapo VIA chipset...
>
>Many thanks for your patch! (even though currently Intel-only)

Yes. This should be easy to do for any chipset. It should be documented
somewhere in the chipset documentation. Atleast it is documented on ICH
specification :).

Thanks,
Venki
-
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/

Powered by blists - more mailing lists