From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, santosh.shilimkar@ti.com,
linux-pm@vger.kernel.org, fweisbec@gmail.com,
john.stultz@linaro.org, linaro-kernel@lists.linaro.org
Subject: Re: [PATCH 2/2][RFC] time : set broadcast irq affinity
Date: Fri, 22 Feb 2013 09:55:30 -0800 [thread overview]
Message-ID: <20130222095530.377fd218@chromoly> (raw)
In-Reply-To: <1361484083-5906-2-git-send-email-daniel.lezcano@linaro.org>
On Thu, 21 Feb 2013 23:01:23 +0100
Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
> +/*
> + * Set broadcast interrupt affinity
> + */
> +static void tick_broadcast_set_affinity(struct clock_event_device
> *bc, int cpu) +{
> + struct cpumask cpumask;
> +
> + if (!(bc->features & CLOCK_EVT_FEAT_DYNIRQ))
> + return;
> +
> + cpumask_clear(&cpumask);
> + cpumask_set_cpu(cpu, &cpumask);
> + irq_set_affinity(bc->irq, &cpumask);
would it be more efficient to keep track of the current bc->irq affinity
via cpumask then set it only if it is different?
--
Thanks,
Jacob
WARNING: multiple messages have this Message-ID (diff)
From: jacob.jun.pan@linux.intel.com (Jacob Pan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2][RFC] time : set broadcast irq affinity
Date: Fri, 22 Feb 2013 09:55:30 -0800 [thread overview]
Message-ID: <20130222095530.377fd218@chromoly> (raw)
In-Reply-To: <1361484083-5906-2-git-send-email-daniel.lezcano@linaro.org>
On Thu, 21 Feb 2013 23:01:23 +0100
Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
> +/*
> + * Set broadcast interrupt affinity
> + */
> +static void tick_broadcast_set_affinity(struct clock_event_device
> *bc, int cpu) +{
> + struct cpumask cpumask;
> +
> + if (!(bc->features & CLOCK_EVT_FEAT_DYNIRQ))
> + return;
> +
> + cpumask_clear(&cpumask);
> + cpumask_set_cpu(cpu, &cpumask);
> + irq_set_affinity(bc->irq, &cpumask);
would it be more efficient to keep track of the current bc->irq affinity
via cpumask then set it only if it is different?
--
Thanks,
Jacob
next prev parent reply other threads:[~2013-02-22 17:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 18:02 [resend] Timer broadcast question Daniel Lezcano
2013-02-19 18:10 ` Thomas Gleixner
2013-02-19 18:21 ` Daniel Lezcano
2013-02-19 22:46 ` Andy Lutomirski
2013-02-20 10:09 ` Thomas Gleixner
2013-02-21 6:19 ` Santosh Shilimkar
2013-02-21 6:19 ` Santosh Shilimkar
2013-02-21 9:01 ` Daniel Lezcano
2013-02-21 9:01 ` Daniel Lezcano
2013-02-21 9:14 ` Santosh Shilimkar
2013-02-21 9:14 ` Santosh Shilimkar
2013-02-21 22:01 ` [PATCH 1/2] time : pass broadcast device parameter Daniel Lezcano
2013-02-21 22:01 ` Daniel Lezcano
2013-02-21 22:01 ` [PATCH 2/2][RFC] time : set broadcast irq affinity Daniel Lezcano
2013-02-21 22:01 ` Daniel Lezcano
2013-02-22 17:55 ` Jacob Pan [this message]
2013-02-22 17:55 ` Jacob Pan
2013-02-22 18:45 ` Thomas Gleixner
2013-02-22 18:45 ` Thomas Gleixner
2013-02-25 22:50 ` Daniel Lezcano
2013-02-25 22:50 ` Daniel Lezcano
2013-02-25 23:00 ` Jacob Pan
2013-02-25 23:00 ` Jacob Pan
2013-02-26 8:45 ` [PATCH 1/2] time : pass broadcast device parameter Viresh Kumar
2013-02-26 8:45 ` Viresh Kumar
2013-02-26 11:30 ` Daniel Lezcano
2013-02-26 11:30 ` Daniel Lezcano
2013-02-26 11:31 ` Daniel Lezcano
2013-02-26 11:31 ` Daniel Lezcano
2013-02-26 12:14 ` Viresh Kumar
2013-02-26 12:14 ` Viresh Kumar
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=20130222095530.377fd218@chromoly \
--to=jacob.jun.pan@linux.intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=fweisbec@gmail.com \
--cc=john.stultz@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=tglx@linutronix.de \
/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 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.