From: chao xie <xiechao.linux@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: tick_setup_device in tick-common.c
Date: Fri, 1 Jul 2011 17:49:52 +0800 [thread overview]
Message-ID: <BANLkTimGAuyMP43eDUet7Ts0XU9WQRYbyQ@mail.gmail.com> (raw)
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.
next reply other threads:[~2011-07-01 9:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 9:49 chao xie [this message]
2011-07-02 0:06 ` chao xie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTimGAuyMP43eDUet7Ts0XU9WQRYbyQ@mail.gmail.com \
--to=xiechao.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®