From: Michael Ellerman <mpe@ellerman.id.au>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@lists.ozlabs.org, linuxppc-dev@ozlabs.org, thuth@redhat.com
Subject: Re: [PATCH 1/6] powerpc/kconfig: Move NR_IRQS into "Kernel Options"
Date: Tue, 13 Oct 2015 11:28:06 +1100 [thread overview]
Message-ID: <1444696086.5383.3.camel@ellerman.id.au> (raw)
In-Reply-To: <5354986.Emc3ODSKdL@wuerfel>
On Mon, 2015-10-12 at 13:50 +0200, Arnd Bergmann wrote:
> On Monday 12 October 2015 22:07:45 Michael Ellerman wrote:
> > Yeah, this builds and boots at least on pseries KVM.
> >
> > diff --git a/arch/powerpc/include/asm/irq.h b/arch/powerpc/include/asm/irq.h
> > index e8e3a0a04eb0..35fba282b7f9 100644
> > --- a/arch/powerpc/include/asm/irq.h
> > +++ b/arch/powerpc/include/asm/irq.h
> > @@ -23,11 +23,8 @@ extern atomic_t ppc_n_lost_interrupts;
> > /* This number is used when no interrupt has been assigned */
> > #define NO_IRQ (0)
> >
> > -/* Total number of virq in the platform */
> > -#define NR_IRQS CONFIG_NR_IRQS
> > -
> > -/* Same thing, used by the generic IRQ code */
> > #define NR_IRQS_LEGACY NUM_ISA_INTERRUPTS
> > +#define NR_IRQS NR_IRQS_LEGACY
> >
> > extern irq_hw_number_t virq_to_hw(unsigned int virq);
> >
>
> This looks like the way it's intended.
Hmm, though IRQ_BITMAP_BITS is still a hard limit, and by default it's set to
NR_IRQS + 8196.
So we'd be relying on the + 8196 to get us up to a reasonable number. That
looks like it was added as a bit of a hack/bug-fix, so I'm not sure we want to
rely on it. (c1ee6264280e ("genirq: Prevent access beyond allocated_irqs
bitmap"))
All the distros seem to run with NR_IRQS=512, so it seems no one has needed
more than that or we would have heard about it presumably.
At the same time if we're only spending a single bit for each interrupt number
maybe we should just set it to min(512, NR_CPUS) or something like that to make
sure it's always reasonably big.
> I've also checked that no powerpc platform defines a static IRQ larger than
> NUM_ISA_INTERRUPTS, and only two files do it at all
> (arch/powerpc/platforms/chrp/pegasos_eth.c and arch/powerpc/sysdev/rtc_cmos_setup.c).
Thanks. You clearly have better grep fu than me :)
cheers
next prev parent reply other threads:[~2015-10-13 0:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 21:09 [PATCH 1/6] powerpc/kconfig: Move NR_IRQS into "Kernel Options" Michael Ellerman
2015-10-08 21:09 ` [PATCH 2/6] powerpc/kconfig: Move sysdev Kconfig later Michael Ellerman
2015-10-09 5:54 ` Thomas Huth
2015-10-08 21:09 ` [PATCH 3/6] powerpc/kconfig: Move bitness & endian options to the top Michael Ellerman
2015-10-08 21:09 ` [PATCH 4/6] powerpc/kconfig: Move SCOM_DEBUGFS into "Kernel Hacking" Michael Ellerman
2015-10-08 21:09 ` [PATCH 5/6] powerpc/kconfig: Move cpu options after platform options Michael Ellerman
2015-10-09 5:47 ` Thomas Huth
2015-10-12 21:47 ` Scott Wood
2015-10-13 0:11 ` Michael Ellerman
2015-10-08 21:09 ` [PATCH 6/6] powerpc/kconfig: Cell CPU options should depend on PPC_CELL Michael Ellerman
2015-10-09 5:48 ` Thomas Huth
2015-10-08 21:30 ` [PATCH 1/6] powerpc/kconfig: Move NR_IRQS into "Kernel Options" Arnd Bergmann
2015-10-12 10:00 ` Michael Ellerman
2015-10-12 10:30 ` Arnd Bergmann
2015-10-12 11:07 ` Michael Ellerman
2015-10-12 11:50 ` Arnd Bergmann
2015-10-13 0:28 ` Michael Ellerman [this message]
2015-10-13 12:07 ` Arnd Bergmann
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=1444696086.5383.3.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=arnd@arndb.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=thuth@redhat.com \
/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).