[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpom5w=ZERxjkAyTkJFrGFu7SUMs27jHm=9dSB1dYYk-1Tg@mail.gmail.com>
Date: Wed, 7 May 2014 18:50:47 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: John Stultz <john.stultz@...aro.org>,
Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
Linaro Networking <linaro-networking@...aro.org>,
Arvind Chauhan <Arvind.Chauhan@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Fengguang Wu <fengguang.wu@...el.com>,
Jet Chen <jet.chen@...el.com>
Subject: Re: [PATCH V2] clocksource: register cpu notifier to remove timer
from dying CPU
On 7 May 2014 16:06, Viresh Kumar <viresh.kumar@...aro.org> wrote:
> And if that's the case what do we want should we do with these
> timers (i.e. ones added with add_timer_on or mod_timer_pinned)
> when we try to quiesce a cpu using cpuset.quiesce [1]?
Okay, I thought again and above looked stupid :) .. During isolation
we can't migrate any pinned timers and so these will stay as is.
But we shouldn't change the code (which I changed in my initial
patchset), which migrates away pinned timers as well..
Probably just add a pr_warn() there and mention we are migrating
a pinned timer. That's it.
--
viresh
--
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