From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andi Kleen <andi@firstfloor.org>, Avi Kivity <avi@qumranet.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: Question about interrupt routing and irq allocation
Date: Tue, 27 May 2008 17:24:10 +0100 [thread overview]
Message-ID: <483C35AA.5060102@goop.org> (raw)
In-Reply-To: <20080527145606.GB24457@elte.hu>
Ingo Molnar wrote:
>> I'm initially targeting 32-bit, though obviously I'd like something
>> that works for both 32 and 64 bit. irq_cfg[] is missing in
>> io_apic_32.c; would I achieve the same effect by setting
>> irq_vector[irq] = 0xff or something?
>>
>
> ok, here comes the next phase of a rather cunning plan: please unify
> these vector allocators first! ;-)
>
Somehow I knew you were going to say that...
> it's nontrivial but would result in rather nice code. I dont know
> whether we want to extend per-CPU vectors to 32-bit as well ... but
> might be worth an attempt and we could give any exploratory patches a
> try in -tip. Eric, what do you think about the general approach?
>
> this would also pave the way towards unified APIC code. Hm
All of that sounds very appealing, particularly as the work on xen-dom0
continues. But in the meantime I'm just using create_irq(), and I'll
wear the wasted vector (after all, it will only happen when booting
under Xen-hvm).
J
next prev parent reply other threads:[~2008-05-27 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 22:08 Question about interrupt routing and irq allocation Jeremy Fitzhardinge
2008-05-27 8:37 ` Ingo Molnar
2008-05-27 9:45 ` Jeremy Fitzhardinge
2008-05-27 14:56 ` Ingo Molnar
2008-05-27 16:24 ` Jeremy Fitzhardinge [this message]
2008-05-28 9:35 ` Eric W. Biederman
2008-05-28 10:40 ` Jeremy Fitzhardinge
2008-05-28 16:04 ` Eric W. Biederman
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=483C35AA.5060102@goop.org \
--to=jeremy@goop.org \
--cc=Keir.Fraser@eu.citrix.com \
--cc=andi@firstfloor.org \
--cc=avi@qumranet.com \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--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