Dong, Eddie wrote:
> This is not necessary, vector doesn;t mean priority.
>
> Remember I ever had a talk with Avi that user level irqchip could only support
> one vector pending in kernel like you mentioned too. On the other hand,
> if we have multiple pending vectors, we will lose priority. The point here
> is that vector doesn;t stand for priority for example slave PIC has higher
> priority
> than IRQ3-7 of master PIC. Using ffs or fls doesn;t matter here.
>
>
Yes.
> But I think we'd better clean the code to just use pending_vector instead
> of bitmap to reduce those kind of unnecessary bit scan/set/clear etc.
>
That's my plan; use a pending vector and put it in subarch independent code.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel