From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Alex Nixon <alex.nixon@citrix.com>,
Alan Mayer <ajm@sgi.com>
Subject: Re: [PATCH] x86: fix probe_nr_irqs for xen
Date: Fri, 22 Aug 2008 06:26:10 +0200 [thread overview]
Message-ID: <20080822042610.GA15212@elte.hu> (raw)
In-Reply-To: <48AE022F.6030100@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> > hope we can kill nr_irqs/NR_IRQS
>
> When irqs are truely dynamically allocated?
they in essence already are truly dynamic in tip/master. Not yet
unconditionally so on x86, we chose to also have a !SPARSEIRQ build
model to make sure dense IRQ arrays still work fine as well. (that's far
easier to test and validate than to keep a farm of cross compilers to
other arches alive.)
But by all means SPARSEIRQ is the primary and only model on x86.
We could even plug in the dynamic vector allocator from Alan Mayer now,
both on 32-bit and on 64-bit x86: Yinghai, any complications expected
there? I guess we need to unify the local APIC code first.
Ingo
next prev parent reply other threads:[~2008-08-22 4:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 20:10 [PATCH] x86: fix probe_nr_irqs for xen Yinghai Lu
2008-08-21 23:33 ` Jeremy Fitzhardinge
2008-08-21 23:49 ` Yinghai Lu
2008-08-21 23:52 ` Jeremy Fitzhardinge
2008-08-21 23:56 ` Yinghai Lu
2008-08-22 0:02 ` Jeremy Fitzhardinge
2008-08-22 0:27 ` Yinghai Lu
2008-08-22 4:26 ` Ingo Molnar [this message]
2008-08-22 5:06 ` Yinghai Lu
2008-08-22 5:16 ` Ingo Molnar
2008-08-22 13:44 ` Cyrill Gorcunov
2008-08-22 4:28 ` Ingo Molnar
2008-08-22 9:07 ` Alex Nixon
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=20080822042610.GA15212@elte.hu \
--to=mingo@elte.hu \
--cc=ajm@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=alex.nixon@citrix.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.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