public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
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 04:49:39 -0800	[thread overview]
Message-ID: <20051209044938.A26619@unix-os.sc.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0512090003460.26307@montezuma.fsmlabs.com>; from zwane@arm.linux.org.uk on Fri, Dec 09, 2005 at 12:06:35AM -0800

On Fri, Dec 09, 2005 at 12:06:35AM -0800, Zwane Mwaikambo wrote:
> On Thu, 8 Dec 2005, Venkatesh Pallipadi wrote:
> 
> > Whenever we see that a CPU is capable of C3 (during ACPI cstate init), we 
> > disable local APIC timer and switch to using a broadcast from external timer
> > interrupt (IRQ 0).
> >
> > +void smp_send_timer_broadcast_ipi(struct pt_regs *regs);
> > +void switch_APIC_timer_to_ipi(void *cpumask);
> > +void switch_ipi_to_APIC_timer(void *cpumask);
> 
> When is this used?

+void smp_send_timer_broadcast_ipi(struct pt_regs *regs);
This is called by the IRQ0 timer interrupt handler, to check whether any CPUs 
have enrolled for this broadcast.

+void switch_APIC_timer_to_ipi(void *cpumask);
Called by acpi processor driver when it find out that a particular CPU can
support C3 state (and it is an Intel CPU).

+void switch_ipi_to_APIC_timer(void *cpumask);
Called by acpi processor driver again to reset to APIC_timer when C3 is not 
supported by the CPU.

The acpi processor driver calls can be at the boot time, or can be at run time
if BIOS enables/disables C3 at run time.

Thanks,
Venki


  reply	other threads:[~2005-12-09 12:50 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 [this message]
2005-12-09 17:35     ` Zwane Mwaikambo
2005-12-09 17:34       ` Andi Kleen
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=20051209044938.A26619@unix-os.sc.intel.com \
    --to=venkatesh.pallipadi@intel.com \
    --cc=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=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