[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.02.1302221945170.22263@ionos>
Date: Fri, 22 Feb 2013 19:45:32 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Jacob Pan <jacob.jun.pan@...ux.intel.com>
cc: Daniel Lezcano <daniel.lezcano@...aro.org>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
santosh.shilimkar@...com, linux-pm@...r.kernel.org,
fweisbec@...il.com, john.stultz@...aro.org,
linaro-kernel@...ts.linaro.org
Subject: Re: [PATCH 2/2][RFC] time : set broadcast irq affinity
On Fri, 22 Feb 2013, Jacob Pan wrote:
> On Thu, 21 Feb 2013 23:01:23 +0100
> Daniel Lezcano <daniel.lezcano@...aro.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?
You beat me :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists