From: Dave Jones <davej@redhat.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: ak@suse.de
Subject: Re: [PATCH] x86_64: Force broadcast timer on AMD systems with C3 too.
Date: Sat, 25 Mar 2006 19:51:58 -0500 [thread overview]
Message-ID: <20060326005158.GC30480@redhat.com> (raw)
In-Reply-To: <200603251813.k2PID0xC014763@hera.kernel.org>
On Sat, Mar 25, 2006 at 06:13:00PM +0000, Linux Kernel wrote:
> commit bd6633476922b7b51227f7f704c2546e763ae5ed
> tree 4e9844781419fe600c3e9f3e9dab8207f8dd12dd
> parent 7682968b7d4d42bb076051b962c3926b4c98539a
> author Andi Kleen <ak@suse.de> Sat, 25 Mar 2006 16:31:07 +0100
> committer Linus Torvalds <torvalds@g5.osdl.org> Sun, 26 Mar 2006 01:10:56 -0800
>
> [PATCH] x86_64: Force broadcast timer on AMD systems with C3 too.
this breaks ia64.
drivers/acpi/processor_idle.c: In function 'acpi_processor_power_verify':
drivers/acpi/processor_idle.c:919: error: 'switch_APIC_timer_to_ipi' undeclared (first use in this function)
drivers/acpi/processor_idle.c:919: error: (Each undeclared identifier is reported only once
drivers/acpi/processor_idle.c:919: error: for each function it appears in.)
> #ifdef ARCH_APICTIMER_STOPS_ON_C3
> - if (cx->valid && c->x86_vendor == X86_VENDOR_INTEL) {
> - on_each_cpu(switch_APIC_timer_to_ipi,
> - &mask, 1, 1);
> - }
> + if (cx->valid)
> + timer_broadcast++;
> #endif
> break;
> }
> @@ -913,6 +915,9 @@ static int acpi_processor_power_verify(s
> working++;
> }
>
> + if (timer_broadcast)
> + on_each_cpu(switch_APIC_timer_to_ipi, &mask, 1, 1);
> +
Looks like it needs wrapping in that ifdef ?
Dave
--
http://www.codemonkey.org.uk
parent reply other threads:[~2006-03-26 0:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200603251813.k2PID0xC014763@hera.kernel.org>]
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=20060326005158.GC30480@redhat.com \
--to=davej@redhat.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.