From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>, "Cyrill Gorcunov" <gorcunov@gmail.com>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>,
"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: Thu, 21 Aug 2008 22:06:48 -0700 [thread overview]
Message-ID: <86802c440808212206s66c31203n651ca021c01104ca@mail.gmail.com> (raw)
In-Reply-To: <20080822042610.GA15212@elte.hu>
On Thu, Aug 21, 2008 at 9:26 PM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * 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.
apic_32.c and apic_64.c
irqinit_32.c and irqinit_64.c
irq_32.c and irq_64.c
Cyrill, is still working on merging apic_32.c apic_64.c.?
YH
next prev parent reply other threads:[~2008-08-22 5:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 20:10 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
2008-08-22 5:06 ` Yinghai Lu [this message]
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=86802c440808212206s66c31203n651ca021c01104ca@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=ajm@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=alex.nixon@citrix.com \
--cc=gorcunov@gmail.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®