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
cmdline parameter and according to Andrew Morton's suggestions.

But on SunFire X4600 it would need to be set to work, correct?
I guess that would make the users of that machine unhappy because
users usually don't want to set weird parameters to make their
system boot.

Actually in theory the HPET driver should ignore the HPET if legacy
replacement is not supported and fall back to PIT. Or are you saying
that PIT doesn't work on that system either?

Anyways I think we need some heuristics to do this all automatically
without user involvement.

-Andi



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

Relevant Pages

  • Re: HPET : Legacy Routing Replacement Enable - 3rd try.
    ... Linux cannot get timer interrupts on INT0, ... What ACPI timer? ... Pin2 on ioapic 0 perhaps? ... This means the systems which you said fixes this would need the command ...
    (Linux-Kernel)
  • Re: why cpu Frequence is Different in windows ce and xp in same pc
    ... With the 845 comes an ACPI timer whose frequency is 3 times the ... now i know that standard CEPC implementation work with timer0 1,193,182 Hz ...
    (microsoft.public.windowsce.embedded)
  • Re: DragonflyBSD kernel clock improvements
    ... No acpi timer. ... No TSC garbage. ...
    (freebsd-current)
  • Re: CreateTimerQueueTimer fails unexpectedly
    ... you should use stateless processing for both your IO completion and timeout logic. ... IOCP + timer queues is a good choice, but a key point is that when the timer runs, calling shutdown with SD_BOTH will abort any pending IO and trigger the cleanup logic you have already written to deal with socket disconnect. ... determine if a command has been responded in the desired time period. ...
    (microsoft.public.win32.programmer.kernel)
  • [patch 15/21] clockevents: drivers for i386
    ... lapic and PIT. ... Update the timer IRQ to call into the PIT driver's event handler ... * of the boot CPU and register the clock event in the framework. ...
    (Linux-Kernel)