From: Andi Kleen <ak@suse.de>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Andi Kleen <ak@suse.de>, Rohit Seth <rohit.seth@intel.com>,
Len Brown <len.brown@intel.com>
Subject: Re: [RFC][PATCH 2/3]i386,x86-64 Handle missing local APIC timer interrupts on C3 state
Date: Fri, 9 Dec 2005 18:34:01 +0100 [thread overview]
Message-ID: <20051209173401.GG11190@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0512090933540.26307@montezuma.fsmlabs.com>
>
> zwane@montezuma linux-2.6-hg-x86_64 {0:1} grep switch_ipi_to_APIC_timer /tmp/patch[1234]
> /tmp/patch2:+void switch_ipi_to_APIC_timer(void *cpumask);
> /tmp/patch2:+void switch_ipi_to_APIC_timer(void *cpumask)
> /tmp/patch2:+EXPORT_SYMBOL(switch_ipi_to_APIC_timer);
> /tmp/patch4:+void switch_ipi_to_APIC_timer(void *cpumask)
> /tmp/patch4:+EXPORT_SYMBOL(switch_ipi_to_APIC_timer);
> /tmp/patch4:+void switch_ipi_to_APIC_timer(void *cpumask);
>
> Or will it only be used in future?
It should be used in drivers/acpi/processor_* before enabling C3.
Or at least it was that way in some earlier patches Venki sent
around.
-Andi
next prev parent reply other threads:[~2005-12-09 17:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 2:10 [RFC][PATCH 2/3]i386,x86-64 Handle missing local APIC timer interrupts on C3 state Venkatesh Pallipadi
2005-12-09 8:06 ` Zwane Mwaikambo
2005-12-09 12:49 ` Venkatesh Pallipadi
2005-12-09 17:35 ` Zwane Mwaikambo
2005-12-09 17:34 ` Andi Kleen [this message]
2005-12-09 17:52 ` Venkatesh Pallipadi
2005-12-09 18:07 ` Andi Kleen
2005-12-09 23:06 ` Venkatesh Pallipadi
2005-12-09 18:27 ` Zwane Mwaikambo
2005-12-13 1:47 ` [PATCH 0/3]i386,x86-64 (take 2) " Venkatesh Pallipadi
2005-12-13 3:08 ` Andi Kleen
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=20051209173401.GG11190@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rohit.seth@intel.com \
--cc=torvalds@osdl.org \
--cc=venkatesh.pallipadi@intel.com \
--cc=zwane@arm.linux.org.uk \
/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