linux-kernel - Re: HPET : Legacy Routing Replacement Enable

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:	Thu, 26 Oct 2006 23:11:49 -0700
From:	Om Narasimhan <om.turyx@...il.com>
To:	Andi Kleen <ak@....de>
CC:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>,
	linux-kernel@...r.kernel.org, randy.dunlap@...cle.com,
	clemens@...isch.de, vojtech@...e.cz, bob.picco@...com
Subject: Re: HPET : Legacy Routing Replacement Enable - 3rd try.

Andi Kleen wrote:
>> 1. HW is LRR capable, HPET ACPI it is 1, timer interrupt is on INT2.
>> Before the fix: Linux cannot get timer interrupts on INT0, goes for ACPI 
>> timer.
> 
> What ACPI timer?  I don't think we have any fallback for int 0.
Sorry, Mea Culpa, I should have written APIC timer.
> 
> Not sure what you mean with INT2. Pin2 on ioapic 0 perhaps?
Yes. PIN2 on IOAPIC #0.
> 
>> After the fix : Works fine. This is according to hpet spec.
> 
> On what exact motherboard was that?
SunFire X4600
> 
>> To handle case 3, I removed all references to acpi_hpet_lrr, explained
>> this case in the code and decided to solely rely on the command line
>> parameter for LRR capability. Rational for this approach is ,
> 
> This means the systems which you said fixes this would need the command
> line parameter to work? 
I feel I do not make things clear enough.
The command line parameter can be avoided entirely if majority of the BIOSes implement LRR routing correctly. I would rewrite the patch to avoid cmdline parameter and according to Andrew Morton's suggestions.

Thanks,
Om.
-
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/