From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Yinghai Lu <yinghai@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Matthew Wilcox <matthew@wil.cx>
Subject: Re: [PATCH 1/5] sparse irq enabling v5
Date: Tue, 9 Dec 2008 13:08:19 -0800 [thread overview]
Message-ID: <200812091308.23440.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20081208133859.GB29965@elte.hu>
On Monday, December 08, 2008 5:38 am Ingo Molnar wrote:
> * Yinghai Lu <yinghai@kernel.org> wrote:
> > impact: new feature sparseirq
> >
> > add pointers array as Ingo suggesting.
> > remove dyna_array
> >
> > when sparse_irq is used (CONFIG_SPARSE_IRQ), use kzalloc_node to get
> > irq_desc, irq_cfg use desc->chip_data for x86 to store irq_cfg
> >
> > Signed-off-by: Yinghai Lu <yinghai@kernel.org>
>
> thanks Yinghai - i've applied your four patches to tip/irq/sparseirq,
> with the changelogs below.
>
> Jesse, any objections to the MSI IRQ renumbering? It's a much saner
> static numbering scheme counting upwards, independent of NR_CPUS.
No, I like the idea of the sparse stuff. I'd like to get Matthew's ack though
too; he's been working in this area a bit lately.
Jesse
prev parent reply other threads:[~2008-12-09 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-06 2:58 Yinghai Lu
2008-12-06 2:58 ` [PATCH 2/5] use NR_IRQS_LEGACY Yinghai Lu
2008-12-06 2:58 ` [PATCH 3/5] MSI irq start from nr_irqs_gsi Yinghai Lu
2008-12-06 2:58 ` [PATCH 4/5] pass irq_cfg and irq_desc Yinghai Lu
2008-12-06 2:58 ` add back sparseirq v5 Yinghai Lu
2008-12-06 3:02 ` Yinghai Lu
2008-12-08 13:38 ` [PATCH 1/5] sparse irq enabling v5 Ingo Molnar
2008-12-09 21:08 ` Jesse Barnes [this message]
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=200812091308.23440.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai@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®