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] [day] [month] [year] [list]

Date:	Sat, 28 Oct 2006 19:49:58 +0200
From:	Andi Kleen <ak@....de>
To:	Om Narasimhan <om.turyx@...il.com>
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.

On Thu, Oct 26, 2006 at 11:11:49PM -0700, Om Narasimhan wrote:
> 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 

But they don't.

> cmdline parameter and according to Andrew Morton's suggestions.

What was that suggestion again? (sorry can't find it)

Anyways the goal is really to just work everywhere without command line
parameters. Can we somehow detect the SunFire condition and only enable 
it there?

-Andi (who must admit he still doesn't quite understand why the Sun machine
needs this anyways)


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