From: Grant Likely <grant.likely@secretlab.ca>
To: benh@kernel.crashing.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de
Subject: [RFC PATCH v2 0/4] Switch to core code for irq allocation
Date: Wed, 20 Apr 2011 22:03:48 -0600 [thread overview]
Message-ID: <20110421040036.30579.53752.stgit@ponder> (raw)
Hey Ben,
Can you take a look at this series and let me know what you think.
The only functional change is in the last patch which uses the core
irq_alloc_desc*() infrastructure to allocating irqs.
I know I've left race conditions in the code; specifically the
unlikely case of two threads trying to map the same interrupt at the
same time. Both will see that it isn't allocated, and both will do
the allocation (I think). I need to hack on it more, but I wanted to
get your feedback.
Ultimately I'm hoping to be rid of the irq_map table entirely.
g.
---
Grant Likely (4):
powerpc: stop exporting irq_map
powerpc: make irq_{alloc,free}_virt private and remove count argument
powerpc: move irq_alloc_descs_at() call into irq_alloc_virt()
powerpc: use irq_alloc_desc() to manage irq allocations
arch/microblaze/kernel/setup.c | 2
arch/powerpc/include/asm/irq.h | 47 ------
arch/powerpc/kernel/irq.c | 162 +++++++++++-----------
arch/powerpc/platforms/512x/mpc5121_ads_cpld.c | 4 -
arch/powerpc/platforms/52xx/media5200.c | 4 -
arch/powerpc/platforms/52xx/mpc52xx_pic.c | 79 ++---------
arch/powerpc/platforms/82xx/pq2ads-pci-pic.c | 4 -
arch/powerpc/platforms/85xx/socrates_fpga_pic.c | 26 +---
arch/powerpc/platforms/86xx/gef_pic.c | 10 -
arch/powerpc/platforms/8xx/m8xx_setup.c | 2
arch/powerpc/platforms/cell/axon_msi.c | 2
arch/powerpc/platforms/cell/spider-pic.c | 10 +
arch/powerpc/platforms/embedded6xx/flipper-pic.c | 8 +
arch/powerpc/platforms/embedded6xx/hlwd-pic.c | 8 +
arch/powerpc/platforms/iseries/irq.c | 10 +
arch/powerpc/platforms/powermac/pic.c | 12 +-
arch/powerpc/platforms/pseries/ras.c | 4 -
arch/powerpc/platforms/pseries/xics.c | 14 +-
arch/powerpc/sysdev/cpm1.c | 8 +
arch/powerpc/sysdev/cpm2_pic.c | 10 +
arch/powerpc/sysdev/ipic.c | 16 +-
arch/powerpc/sysdev/mpc8xx_pic.c | 10 +
arch/powerpc/sysdev/mpc8xxx_gpio.c | 12 +-
arch/powerpc/sysdev/mpic.c | 28 ++--
arch/powerpc/sysdev/mv64x60_pic.c | 14 +-
arch/powerpc/sysdev/qe_lib/qe_ic.c | 6 -
arch/powerpc/sysdev/uic.c | 12 +-
arch/powerpc/sysdev/xilinx_intc.c | 8 +
28 files changed, 206 insertions(+), 326 deletions(-)
--
Signature
next reply other threads:[~2011-04-21 4:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 4:03 Grant Likely [this message]
2011-04-21 4:03 ` [RFC PATCH v2 1/4] powerpc: stop exporting irq_map Grant Likely
2011-04-21 4:03 ` [RFC PATCH v2 2/4] powerpc: make irq_{alloc, free}_virt private and remove count argument Grant Likely
2011-04-21 4:04 ` [RFC PATCH v2 3/4] powerpc: move irq_alloc_descs_at() call into irq_alloc_virt() Grant Likely
2011-04-21 4:04 ` [RFC PATCH v2 4/4] powerpc: use irq_alloc_desc() to manage irq allocations Grant Likely
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=20110421040036.30579.53752.stgit@ponder \
--to=grant.likely@secretlab.ca \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).