WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [PATCH v2 1/2] x86: skip migrating IRQF_PER_CPU irq in f

>>> On 09.05.11 at 14:39, Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote:
> On Fri, 6 May 2011, Konrad Rzeszutek Wilk wrote:
>> On Fri, May 06, 2011 at 02:43:36PM +0800, Tian, Kevin wrote:
>> > because Xen event chip silently fails the set_affinity ops, and
>> > logically IRQF_PER_CPU should be recognized here.
>> 
>> OK, so what if the set_affinity ops was implemented?
> 
> An interrupt chip which has a set_affinity op should not mark
> something per cpu, which implies that the irq CANNOT be moved.

Why shouldn't it be possible o use the same "chip" for both per-CPU
and "normal" IRQs?

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel