All of lore.kernel.org
 help / color / mirror / Atom feed
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 0/3] timers: Allocate per-cpu tvec_base's statically
Date: Mon, 30 Mar 2015 10:47:16 +0530	[thread overview]
Message-ID: <cover.1427691098.git.viresh.kumar@linaro.org> (raw)

Hi Ingo/Thomas,

Here are few cleanups around timer-core initialization. The first one is
suggested by Peter Zijlstra [1] and the other two make few more changes in order
to simplify it.

Please see if they look fine.

--
viresh

[1] http://lkml.iu.edu/hypermail/linux/kernel/1503.3/04091.html

Peter Zijlstra (1):
  timer: Allocate per-cpu tvec_base's statically

Viresh Kumar (2):
  timer: Limit the scope of __tvec_bases to init_timers_cpu()
  timer: Don't initialize tvec_base on hotplug

 kernel/time/timer.c | 121 +++++++++++++++++++---------------------------------
 1 file changed, 45 insertions(+), 76 deletions(-)

-- 
2.3.0.rc0.44.ga94655d


             reply	other threads:[~2015-03-30  5:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30  5:17 Viresh Kumar [this message]
2015-03-30  5:17 ` [PATCH 1/3] timer: Allocate per-cpu tvec_base's statically Viresh Kumar
2015-03-31  7:45   ` Ingo Molnar
2015-03-31 11:32     ` Viresh Kumar
2015-03-30  5:17 ` [PATCH 2/3] timer: Limit the scope of __tvec_bases to init_timers_cpu() Viresh Kumar
2015-03-30  5:17 ` [PATCH 3/3] timer: Don't initialize tvec_base on hotplug Viresh Kumar
2015-03-30  8:18 ` [PATCH 0/3] timers: Allocate per-cpu tvec_base's statically Peter Zijlstra
2015-03-30  9:55   ` Viresh Kumar
2015-03-30 10:27     ` Peter Zijlstra
2015-03-30 10:33       ` 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=cover.1427691098.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 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.