linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: johlstei@codeaurora.org (Jeff Ohlstein)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 08/12] ARM: msm: use remapped PPI interrupts for	local timer
Date: Wed, 04 May 2011 11:45:23 -0700	[thread overview]
Message-ID: <4DC19EC3.2070702@codeaurora.org> (raw)
In-Reply-To: <4DC0E886.3010709@codeaurora.org>

Stephen Boyd wrote:
> 
> I took a peek at the APB timer on x86 and I see that apbt_setup_irq()
> does an
> 
>         if (system_state == SYSTEM_BOOTING) {
>                 if (request_irq(adev->irq, apbt_interrupt_handler,
> 
> which is probably exactly what we want to do to handle the crash I'm
> talking about.
> 

This won't work right with the maxcpus commandline option set to
something lower than the number of cpus present on the system. This
option controls how many cpus the system tries to bring up during boot,
while still allowing one to hotplug the rest of them later. If you do
hotplug them later, system_state will no longer be SYSTEM_BOOTING, and
this code won't do what it needs to do.

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2011-05-04 18:45 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20 19:08 [RFC PATCH 00/12] Consolidating GIC per-cpu interrupts Marc Zyngier
2011-04-20 19:08 ` [RFC PATCH 01/12] ARM: gic: add per-cpu interrupt multiplexer Marc Zyngier
2011-04-25 20:17   ` Abhijeet Dharmapurikar
2011-04-26  9:08     ` Marc Zyngier
2011-04-26  4:00   ` Stephen Boyd
2011-04-26  9:12     ` Marc Zyngier
2011-04-20 19:08 ` [RFC PATCH 02/12] ARM: smp_twd: add support for remapped PPI interrupts Marc Zyngier
2011-04-25 17:04   ` Stephen Boyd
2011-04-26  9:05     ` Marc Zyngier
2011-04-26 16:21       ` Stephen Boyd
2011-04-26 16:53         ` Marc Zyngier
2011-04-20 19:08 ` [RFC PATCH 03/12] ARM: omap4: use remapped PPI interrupts for local timer Marc Zyngier
2011-04-29  7:24   ` Santosh Shilimkar
2011-05-03 16:18     ` Marc Zyngier
2011-04-20 19:08 ` [RFC PATCH 04/12] ARM: versatile: " Marc Zyngier
2011-04-20 19:08 ` [RFC PATCH 05/12] ARM: shmobile: " Marc Zyngier
2011-04-20 19:08 ` [RFC PATCH 06/12] ARM: ux500: " Marc Zyngier
2011-04-21  8:44   ` Srinidhi KASAGAR
2011-04-21  8:53     ` Marc Zyngier
2011-04-20 19:08 ` [RFC PATCH 07/12] ARM: tegra: " Marc Zyngier
2011-04-20 19:08 ` [RFC PATCH 08/12] ARM: msm: " Marc Zyngier
2011-04-26 17:13   ` Stephen Boyd
2011-05-03 16:15     ` Marc Zyngier
2011-05-03 17:38       ` Stephen Boyd
2011-05-03 19:04     ` Russell King - ARM Linux
2011-05-04  5:47       ` Stephen Boyd
2011-05-04 18:45         ` Jeff Ohlstein [this message]
2011-05-05  1:17           ` Stephen Boyd
2011-04-20 19:08 ` [RFC PATCH 09/12] ARM: exynos4: " Marc Zyngier
2011-04-20 19:08 ` [RFC PATCH 10/12] ARM: gic: remove previous local timer interrupt handling Marc Zyngier
2011-04-20 19:08 ` [RFC PATCH 11/12] ARM: gic: add compute_irqnr macro for exynos4 Marc Zyngier
2011-04-20 19:08 ` [RFC PATCH 12/12] ARM: SMP: automatically select ARM_GIC_VPPI Marc Zyngier

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=4DC19EC3.2070702@codeaurora.org \
    --to=johlstei@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).