[lkml]   [2010]   [Jan]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] x86, apic: use 0x20 for the IRQ_MOVE_CLEANUP_VECTOR instead of 0x1f
On 01/11/2010 04:06 PM, Suresh Siddha wrote:
>> Yes, that's what I said. My question was to Suresh what enforces that
>> in the case of his patch, which moves the legacy range into the middle
>> of the device vectors.
> It's not the used_vector bitmap. That range will appear as used on all
> the cpu's and hence we won't be allocating it for anything else.

OK, fair enough.

> Now the question is: for non-legacy (io-apic) case, instead of reserving
> this range for all the cpu's, does it make sense to generalize like any
> other vector?

It sounds like something that we could experiment with -- after
switching an IRQ to ioapic mode, make it a movable interrupt. It
*seems* it should work, but it's scary stuff to muck with.

Eric, do you see any reason why it wouldn't work? I truly couldn't
understand your previous remark, especially the bit about "it is
dangerous to play lowest priority irq games in that range".


 \ /
  Last update: 2010-01-12 01:17    [W:0.049 / U:13.940 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site