Re: [PATCH] Prevent clockevent event_handler ending uphandler_noop

[Thomas Gleixner]

On Wed, 3 Sep 2008, Andreas Mohr wrote:
> On Wed, Sep 03, 2008 at 07:15:16PM +0200, Thomas Gleixner wrote:
> > On Wed, 3 Sep 2008, Andreas Mohr wrote:
> > > See what such highres-deprived people as myself (PIT, acpi_pm,
> > > _no_ HPET and thus no IRQed highres timer) are doing now,
> > 
> > Err. PIT + acpi_pm works with highres. acpi_pm is a stable clocksource
> > and PIT is not a good, but a usable oneshot timer.
> 
> Hmm. What I'm interested in is longer wakeup timeouts (ACPI C2/C3
> stuff), which would be a problem with PIT (~20 forced wakeups per second)
> but with my new timer that would work.
> Oh, side question: it _is_ easily possible to then disable PIT IRQs
> once my event device is registered, right? Otherwise I could forget
> about power management benefits...

When you register something better than PIT, then the PIT is
disabled completely. No more interrupts from there.

> So as I see it, the most beneficial thing I can do is to provide
> a clock_event_device only.

Right.
 
> Out of interest: how big would you believe the benefit to be?
> (overall system performance gains and ACPI PM benefits)

Hard to tell, your milage can vary.

     tglx

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