From: Pavel Machek <pavel@ucw.cz>
To: abelay@novell.com, len.brown@intel.com,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@dominikbrodowski.net, arjan@linux.intel.com
Subject: Re: [RFC][PATCH 2/2] ACPI: handle timer ticks proactively
Date: Tue, 5 Sep 2006 10:28:57 +0200 [thread overview]
Message-ID: <20060905082855.GC5082@elf.ucw.cz> (raw)
In-Reply-To: <20060904131027.GD6279@ucw.cz>
Hi!
> This patch takes advantage of the infrastructure introduced in the last
> patch, and allows the processor idle algorithm to proactively choose a
> c-state based on the time the next timer interrupt is expected to occur.
> It preserves the residency metric, so the algorithm should, in theory,
> remain effective against bursts of activity from other interrupt
> sources.
>
> This patch is mostly intended to be illustrative. There may be some
> "#ifdef CONFIG_ACPI" issues, and I would appreciate any advice on
> implementing this more cleanly.
>
> Cheers,
> Adam
> --- a/kernel/timer.c 2006-08-03 13:39:22.000000000 -0400
> +++ b/kernel/timer.c 2006-08-28 17:16:36.000000000 -0400
> @@ -41,6 +41,9 @@
> #include <asm/timex.h>
> #include <asm/io.h>
>
> +#include <acpi/acpi_bus.h>
> +#include <acpi/processor.h>
> +
I sense a problem here, like broken compilation for all non-x86
platforms.
> @@ -1175,6 +1178,10 @@
> {
> struct task_struct *p = current;
> int cpu = smp_processor_id();
> + struct acpi_processor *pr = processors[cpu];
> +
> + if (pr)
> + pr->power.timer_tick = inl(acpi_fadt.xpm_tmr_blk.address);
>
This probably needs to be encapsulated, somehow.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next parent reply other threads:[~2006-09-05 8:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060904131027.GD6279@ucw.cz>
2006-09-05 8:28 ` Pavel Machek [this message]
2006-09-05 8:53 ` [RFC][PATCH 2/2] ACPI: handle timer ticks proactively Pavel Machek
2006-09-05 9:03 ` Pavel Machek
2006-09-05 15:16 ` Adam Belay
2006-09-06 10:54 ` Pavel Machek
2006-08-29 20:51 Adam Belay
2006-10-16 4:59 ` Len Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060905082855.GC5082@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=abelay@novell.com \
--cc=arjan@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox