From: Andrew Morton <akpm@linux-foundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
John Stultz <johnstul@us.ibm.com>, Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: [patch 2/3] ACPI: Keep TSC stable, when lapic_timer_c2_ok is set
Date: Sun, 6 May 2007 23:43:56 -0700 [thread overview]
Message-ID: <20070506234356.da324185.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070430102851.987296000@linutronix.de>
On Mon, 30 Apr 2007 10:43:33 -0000 Thomas Gleixner <tglx@linutronix.de> wrote:
> The local apic timer stop in C2 resp. C3 states is coupled with the
> stop of the TSC. When the local apic timer is marked stable in C2
> on the kernel commandline, then keep the TSC marked stable in C2 as well.
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
>
> ---
> drivers/acpi/processor_idle.c | 19 ++++++++-----------
> 1 file changed, 8 insertions(+), 11 deletions(-)
>
> Index: linux-2.6/drivers/acpi/processor_idle.c
> ===================================================================
> --- linux-2.6.orig/drivers/acpi/processor_idle.c
> +++ linux-2.6/drivers/acpi/processor_idle.c
> @@ -305,18 +305,23 @@ static void acpi_state_timer_broadcast(s
> struct acpi_processor_cx *cx,
> int broadcast)
> {
> -#ifdef CONFIG_GENERIC_CLOCKEVENTS
> -
> int state = cx - pr->power.states;
>
> if (state >= pr->power.timer_broadcast_on_state) {
> +
> +#ifdef CONFIG_GENERIC_CLOCKEVENTS
> unsigned long reason;
>
> reason = broadcast ? CLOCK_EVT_NOTIFY_BROADCAST_ENTER :
> CLOCK_EVT_NOTIFY_BROADCAST_EXIT;
> clockevents_notify(reason, &pr->id);
> - }
> #endif
> +
> +#ifdef CONFIG_GENERIC_TIME
> + /* TSC halts in C2/3, so notify users */
> + mark_tsc_unstable();
> +#endif
> + }
> }
>
> #else
> @@ -481,10 +486,6 @@ static void acpi_processor_idle(void)
> /* Get end time (ticks) */
> t2 = inl(acpi_gbl_FADT.xpm_timer_block.address);
>
> -#ifdef CONFIG_GENERIC_TIME
> - /* TSC halts in C2, so notify users */
> - mark_tsc_unstable();
> -#endif
> /* Re-enable interrupts */
> local_irq_enable();
> current_thread_info()->status |= TS_POLLING;
> @@ -523,10 +524,6 @@ static void acpi_processor_idle(void)
> acpi_set_register(ACPI_BITREG_ARB_DISABLE, 0);
> }
>
> -#ifdef CONFIG_GENERIC_TIME
> - /* TSC halts in C3, so notify users */
> - mark_tsc_unstable();
> -#endif
> /* Re-enable interrupts */
> local_irq_enable();
> current_thread_info()->status |= TS_POLLING;
>
> --
I'm now up to the third or fourth time where I need to try to repair this
patch against churn in Len's tree. I'm not sure what I'm doing and that
changelog is of little help to me.
I think I'll drop it. Please work it with Len.
next prev parent reply other threads:[~2007-05-07 6:45 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070430102837.748238000@linutronix.de>
2007-05-02 0:33 ` [patch 0/3] Clocksource / clockevent updates Andrew Morton
2007-05-02 6:09 ` Thomas Gleixner
2007-05-02 6:14 ` Andrew Morton
[not found] ` <20070430102852.042964000@linutronix.de>
2007-05-05 7:34 ` [patch 3/3] clockevents: Fix resume logic Andrew Morton
2007-05-05 11:51 ` Ingo Molnar
2007-05-06 15:03 ` [patch 3/3] clockevents: Fix resume logic - updated version Thomas Gleixner
2007-05-08 10:37 ` Andrew Morton
2007-05-09 5:59 ` Andrew Morton
2007-05-09 7:10 ` Andrew Morton
2007-05-09 8:18 ` Thomas Gleixner
2007-05-09 8:22 ` Andrew Morton
2007-05-09 8:31 ` Andrew Morton
2007-05-09 8:59 ` Thomas Gleixner
2007-05-09 11:45 ` Rafael J. Wysocki
2007-05-09 12:24 ` Thomas Gleixner
2007-05-09 13:12 ` Rafael J. Wysocki
2007-05-09 13:19 ` Thomas Gleixner
2007-05-09 17:09 ` Rafael J. Wysocki
2007-05-09 17:15 ` Thomas Gleixner
2007-05-09 18:36 ` Rafael J. Wysocki
2007-05-09 20:45 ` Thomas Gleixner
2007-05-09 20:53 ` Rafael J. Wysocki
2007-05-09 21:26 ` Thomas Gleixner
2007-05-10 8:46 ` Andrew Morton
2007-05-10 8:55 ` Thomas Gleixner
2007-05-10 9:18 ` Andrew Morton
2007-05-10 9:27 ` Thomas Gleixner
2007-05-10 20:12 ` Rafael J. Wysocki
2007-05-11 16:47 ` Andrew Morton
2007-05-11 20:10 ` Rafael J. Wysocki
2007-05-11 20:28 ` Andrew Morton
2007-05-11 21:02 ` Rafael J. Wysocki
2007-05-11 21:09 ` Rafael J. Wysocki
2007-05-12 6:56 ` Andrew Morton
2007-05-12 8:46 ` Thomas Gleixner
2007-05-12 9:00 ` Andrew Morton
2007-05-12 9:18 ` Thomas Gleixner
2007-05-12 10:07 ` Andrew Morton
2007-05-12 11:44 ` Thomas Gleixner
2007-05-12 16:51 ` Andrew Morton
2007-05-12 17:01 ` Thomas Gleixner
2007-05-12 17:23 ` Andrew Morton
2007-05-12 19:36 ` Thomas Gleixner
2007-05-12 19:56 ` Thomas Gleixner
2007-05-13 1:11 ` Andrew Morton
2007-05-13 8:07 ` Thomas Gleixner
2007-05-13 16:48 ` Thomas Gleixner
2007-05-13 19:09 ` Andrew Morton
2007-05-13 20:07 ` Ingo Molnar
2007-05-13 22:35 ` Andrew Morton
2007-05-12 18:49 ` Thomas Gleixner
2007-05-12 11:52 ` Thomas Gleixner
2007-05-15 16:52 ` Pavel Machek
2007-05-13 16:12 ` Thomas Gleixner
2007-05-14 6:42 ` Andrew Morton
2007-05-14 6:58 ` Thomas Gleixner
2007-05-09 12:52 ` Rafael J. Wysocki
2007-05-09 17:14 ` Andrew Morton
2007-05-09 18:55 ` Rafael J. Wysocki
[not found] ` <20070430102851.987296000@linutronix.de>
2007-05-07 6:43 ` Andrew Morton [this message]
2007-05-07 7:01 ` [patch 2/3] ACPI: Keep TSC stable, when lapic_timer_c2_ok is set Thomas Gleixner
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=20070506234356.da324185.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=johnstul@us.ibm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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