From: Viresh Kumar <viresh.kumar@linaro.org>
To: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH V2 0/3] timers: Allocate per-cpu tvec_base's statically
Date: Tue, 31 Mar 2015 20:48:59 +0530 [thread overview]
Message-ID: <cover.1427814611.git.viresh.kumar@linaro.org> (raw)
Hi Ingo/Thomas,
This is V2 of the cleanups around timer-core initialization sent earlier.
These make initialization of tvec_base's simpler by statically allocating memory
for them, and removing the need of initializing them again on CPU hotplug.
V1->V2:
- Dropped 2/3 from earlier set, which moved definition of __tvec_bases within a
function, as that caused wreckage on xtensa and tile.
- A new patch from Peter is added, 3/3.
- Few changes in 1/3 on Ingo's suggestions:
- Add explanatory comment around boot_tvec_bases and __tvec_bases.
- s/boot_done/boot_cpu_skipped
--
viresh
Peter Zijlstra (2):
timer: Allocate per-cpu tvec_base's statically
timer: Further simplify SMP and HOTPLUG logic
Viresh Kumar (1):
timer: Don't initialize tvec_base on hotplug
kernel/time/timer.c | 143 ++++++++++++++++++++++------------------------------
1 file changed, 61 insertions(+), 82 deletions(-)
--
2.3.0.rc0.44.ga94655d
next reply other threads:[~2015-03-31 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 15:18 Viresh Kumar [this message]
2015-03-31 15:19 ` [PATCH V2 1/3] timer: Allocate per-cpu tvec_base's statically Viresh Kumar
2015-04-02 18:47 ` [tip:timers/core] " tip-bot for Peter Zijlstra
2015-04-14 14:13 ` Eric Dumazet
2015-03-31 15:19 ` [PATCH V2 2/3] timer: Don't initialize tvec_base on hotplug Viresh Kumar
2015-04-02 18:47 ` [tip:timers/core] timer: Don't initialize 'tvec_base' " tip-bot for Viresh Kumar
2015-03-31 15:19 ` [PATCH V2 3/3] timer: Further simplify SMP and HOTPLUG logic Viresh Kumar
2015-04-02 18:48 ` [tip:timers/core] timer: Further simplify the " tip-bot for Peter Zijlstra
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=cover.1427814611.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox