lkml.org 
[lkml]   [2006]   [Apr]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRE: [(repost) git Patch 1/1] avoid IRQ0 ioapic pin collision
Date
From
> > Len, maybe it sounds dramatic and/or extreme, but how about getting 
> > rid of IRQs and just having GSI-vector pair.
> > I intuitively think that would be possible (not that I have all the
> > details lined up :) And this would probably take away confusing IRQ
> > abstraction out once and for all? I think something like
> that is done
> > in ia64.
>
> x86 users are attached to their interrupt numbers I think
> back from the bad old days with only 16 interrupts and
> interrupt sharing didn't work. We might have a revolt in the
> user base if /proc/interrupts didn't display them anymore @)
>
> But I guess using GSI/vector internally only would be fine.
>
Oh I completely agree there are probably few strings attached that have
to be mimicked and kept (especially those 16), but I think that can be
done.
It feels like not a small change to me, but would probably be
worthwhile. It is such a boring thing trying to fit new chipsets and
system dimensions into old inflexible format...

--Natalie
-
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/

\
 
 \ /
  Last update: 2006-04-27 21:29    [W:0.033 / U:0.832 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site