From: Thomas Gleixner <tglx@linutronix.de>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
"Lists linaro-kernel" <linaro-kernel@lists.linaro.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Tejun Heo" <tj@kernel.org>, "Ingo Molnar" <mingo@kernel.org>
Subject: Re: [PATCH 2/2] timer: Make sure TIMER_FLAG_MASK bits are free in allocated base
Date: Wed, 19 Mar 2014 21:32:09 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.02.1403192125260.18573@ionos.tec.linutronix.de> (raw)
In-Reply-To: <CAKohpo=g4nhRUN7wJY-fpE1TiQWEDExKpZ1p4C8gUEDK8mXZ_Q@mail.gmail.com>
On Tue, 18 Mar 2014, Viresh Kumar wrote:
> On 11 March 2014 15:56, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> >
> > Now, I was looking to migrate away the timers first but I
> > obviously shouldn't migrate the pinned timers. One way out to
> > identify PINNED timers is to mark them PINNED with the flag bits,
> > which you wouldn't allow. Can you give some other idea with which
> > I can get this solved.
Sigh, I really hoped to find some time to finish the rework, but then
you get to debug bugs, solve the problem and are rewarded with a full
inbox. Lather, rinse, repeat...
Go ahead and make the timer base aligned with more room for some bits
to tweak. The new stuff will have a flags field where stuff like
pinned is stored.
Thanks,
tglx
next prev parent reply other threads:[~2014-03-19 20:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 8:45 [PATCH 1/2] timer: check failure of timer_cpu_notify() before calling init_timer_stats() Viresh Kumar
2014-02-28 8:45 ` [PATCH 2/2] timer: Make sure TIMER_FLAG_MASK bits are free in allocated base Viresh Kumar
2014-02-28 10:52 ` Thomas Gleixner
2014-02-28 16:51 ` Viresh Kumar
2014-03-11 10:26 ` Viresh Kumar
2014-03-18 8:09 ` Viresh Kumar
2014-03-19 20:32 ` Thomas Gleixner [this message]
2014-03-04 11:33 ` [tip:timers/core] " tip-bot for Viresh Kumar
2014-03-04 11:33 ` [tip:timers/core] timer: Check failure of timer_cpu_notify() before calling init_timer_stats() tip-bot for 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=alpine.DEB.2.02.1403192125260.18573@ionos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=fweisbec@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tj@kernel.org \
--cc=viresh.kumar@linaro.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 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.