mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Thompson <set.mailinglist@gmail.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: SPARSE_IRQ
Date: Wed, 19 Dec 2012 02:22:11 -0500	[thread overview]
Message-ID: <20121219072211.GE2939@squish.home.loc> (raw)

	Hi;

	Perhaps Im being an idiot, but it looks to me like the
menu-item for SPARSE_IRQ (under General setup -> IRQ subsystem)
depends solely on MAY_HAVE_SPARSE_IRQ, but I only see *one* user
for that in the kernel now, the SuperH arch (arch/sh/Kconfig). It
looks like everyone else explicitly sets SPARSE_IRQ. However the
menu-items description implies it is a more generic option...
	It seems like this menu item used to appear, in a forced
on state, then this condition made it disapear, leaving a blank
IRQ subsystem menu for me. I was trying to work around that, but
now, I am not sure exactly what is supposed to be going on here...

Paul

(from kernel/irq/Kconfig)
config SPARSE_IRQ
        bool "Support sparse irq numbering" if MAY_HAVE_SPARSE_IRQ
        ---help---

          Sparse irq numbering is useful for distro kernels that want
          to define a high CONFIG_NR_CPUS value but still want to have
          low kernel memory footprint on smaller machines.

          ( Sparse irqs can also be beneficial on NUMA boxes, as they spread
            out the interrupt descriptors in a more NUMA-friendly way. )

          If you don't know what to do here, say N.


                 reply	other threads:[~2012-12-19  7:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20121219072211.GE2939@squish.home.loc \
    --to=set.mailinglist@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®