All of lore.kernel.org
 help / color / mirror / Atom feed
* tick_setup_device in tick_common.c
@ 2011-07-02  9:47 Chao Xie
  2011-07-04  2:29 ` Chao Xie
  0 siblings, 1 reply; 2+ messages in thread
From: Chao Xie @ 2011-07-02  9:47 UTC (permalink / raw)
  To: linux-kernel

hi
I am very strange about this function.
In this function, it has
/*
        * When the device is not per cpu, pin the interrupt to the
        * current cpu:
        */
       if (!cpumask_equal(newdev->cpumask, cpumask))
               irq_set_affinity(newdev->irq, cpumask);

When the clock event device has cpu_mask set to be cpumask_of(1), it
means that the device is bound to cpu1. So above code has covered it,
but why we have "!cpumask_equal(newdev->cpumask, cpumask)"?
if the "newdev->cpumask" equals "cpumask", cpumask_equal will return
1, and at this situation we will set the irq affinity because the
device is bound to the dedicated cpu.

Is there a bug, or i understand wrong about cpumask of clock_event_device?
Thanks.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* tick_setup_device in tick_common.c
  2011-07-02  9:47 tick_setup_device in tick_common.c Chao Xie
@ 2011-07-04  2:29 ` Chao Xie
  0 siblings, 0 replies; 2+ messages in thread
From: Chao Xie @ 2011-07-04  2:29 UTC (permalink / raw)
  To: tglx, mingo; +Cc: linux-kernel

hi
I am very strange about this function.
In this function, it has
/*
        * When the device is not per cpu, pin the interrupt to the
        * current cpu:
        */
       if (!cpumask_equal(newdev->cpumask, cpumask))
               irq_set_affinity(newdev->irq, cpumask);

When the clock event device has cpu_mask set to be cpumask_of(1), it
means that the device is bound to cpu1. So above code has covered it,
but why we have "!cpumask_equal(newdev->cpumask, cpumask)"?
if the "newdev->cpumask" equals "cpumask", cpumask_equal will return
1, and at this situation we will set the irq affinity because the
device is bound to the dedicated cpu.

Is there a bug, or i understand wrong about cpumask of clock_event_device?
Thanks.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-07-04  2:29 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-07-02  9:47 tick_setup_device in tick_common.c Chao Xie
2011-07-04  2:29 ` Chao Xie

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.