From: "Mika Penttilä" <mika.penttila@kolumbus.fi>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.5.68 Fix IO_APIC IRQ assignment bug
Date: Mon, 21 Apr 2003 20:55:12 +0300 [thread overview]
Message-ID: <3EA43080.70204@kolumbus.fi> (raw)
In-Reply-To: Pine.LNX.4.50.0304211314040.2085-100000@montezuma.mastecende.com
yes the current code has the assumption of 1to1 mapping from vector to
irq, but that's a software limitation.
--Mika
Zwane Mwaikambo wrote:
>On Mon, 21 Apr 2003, Mika Penttilä wrote:
>
>
>
>>Why can't we use the same vector for multiple ioapic entrys? After all,
>>we are already sharing irqs, and an irq is just a cookie for a vector.
>>What do you mean with "lost irq routing" ?
>>
>>
>
>Each ioredtbl can take a vector, if you assign another ioredtbl with the
>same vector and different IRQ then you collide with the previous entry and
>wipe it from the IDT. Also irq != vector
>
> Zwane
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
next prev parent reply other threads:[~2003-04-21 17:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 7:48 [PATCH] 2.5.68 Fix IO_APIC IRQ assignment bug Chuck Ebbert
2003-04-21 15:16 ` Zwane Mwaikambo
2003-04-21 16:04 ` Mika Penttilä
2003-04-21 17:22 ` Zwane Mwaikambo
2003-04-21 17:55 ` Mika Penttilä [this message]
2003-04-22 14:59 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2003-04-21 21:48 Chuck Ebbert
2003-04-22 15:02 ` Maciej W. Rozycki
2003-04-21 18:24 Nakajima, Jun
2003-04-21 16:34 Nakajima, Jun
2003-04-21 17:12 ` Zwane Mwaikambo
2003-04-20 22:06 Chuck Ebbert
2003-04-20 22:58 ` Linus Torvalds
2003-04-20 23:05 ` Zwane Mwaikambo
2003-04-20 23:06 ` Linus Torvalds
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=3EA43080.70204@kolumbus.fi \
--to=mika.penttila@kolumbus.fi \
--cc=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linuxpower.ca \
/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