mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: tglx@linutronix.de, linux-mips@linux-mips.org, ralf@linux-mips.org
Cc: linux-kernel@vger.kernel.org, David Daney <ddaney@caviumnetworks.com>
Subject: [PATCH v3 0/4] Add IRQ chip hooks for taking CPUs on/off line.
Date: Fri, 25 Mar 2011 12:38:47 -0700	[thread overview]
Message-ID: <1301081931-11240-1-git-send-email-ddaney@caviumnetworks.com> (raw)

When a CPU is brought on-line, per-CPU interrupts need to be enabled
on the new CPU.  The local timer and things like perf counters that
rely on interrupts don't work if their interrupts are not enabled.

Likewise when a CPU is taken off-line, we may need to clean up the
interrupts.

I solve both of these problems by adding a pair of function pointers
to the irq_chip structure, along with some simple helper functions to
call them.

There are a pair of helper functions, irq_cpu_{on,off}line(), iterate
through all irqs calling the chip.irq_cpu_{on,off}line() for each irq.

For this iteration to work, we must make sure that all active irqs are
in the allocated_irqs set.  To do this we call irq_reserve_irq() from
irq_set_chip().

My chip.irq_cpu_offline() need to adjust the affinity of some irqs, so
I split up irq_set_affinity() in to two parts, one of which I can call
with the irq desc lock held.

Finally I completely rewrite my irq handling code which uses the
changes to the core irq code.

David Daney (4):
  genirq: Reserve the irq when calling irq_set_chip()
  genirq: Add chip hooks for taking CPUs on/off line.
  genirq: Split irq_set_affinity() so it can be called with lock held.
  MIPS: Octeon: Rewrite interrupt handling code.

 arch/mips/cavium-octeon/octeon-irq.c           | 1423 ++++++++++++++----------
 arch/mips/cavium-octeon/setup.c                |   12 -
 arch/mips/cavium-octeon/smp.c                  |   39 +-
 arch/mips/include/asm/mach-cavium-octeon/irq.h |  243 ++---
 arch/mips/include/asm/octeon/octeon.h          |    2 +
 arch/mips/pci/msi-octeon.c                     |   20 +-
 include/linux/interrupt.h                      |    2 +
 include/linux/irq.h                            |    8 +
 kernel/irq/chip.c                              |   68 ++
 kernel/irq/manage.c                            |   40 +-
 10 files changed, 1026 insertions(+), 831 deletions(-)

-- 
1.7.2.3


             reply	other threads:[~2011-03-25 19:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25 19:38 David Daney [this message]
2011-03-25 19:38 ` [PATCH v3 1/4] genirq: Reserve the irq when calling irq_set_chip() David Daney
2011-03-25 22:30   ` Thomas Gleixner
2011-03-27 16:18   ` [tip:irq/urgent] " tip-bot for David Daney
2011-03-25 19:38 ` [PATCH v3 2/4] genirq: Add chip hooks for taking CPUs on/off line David Daney
2011-03-27 16:19   ` [tip:irq/urgent] " tip-bot for David Daney
2011-03-25 19:38 ` [PATCH v3 3/4] genirq: Split irq_set_affinity() so it can be called with lock held David Daney
2011-03-25 22:32   ` Thomas Gleixner
2011-03-27 16:20   ` [tip:irq/urgent] " tip-bot for David Daney
2011-03-25 19:38 ` [PATCH v3 4/4] MIPS: Octeon: Rewrite interrupt handling code David Daney

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=1301081931-11240-1-git-send-email-ddaney@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --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

all inboxes | Powered by JetHome®