linux-kernel - [PATCH V2 0/3] timers: Allocate per-cpu tvec

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 31 Mar 2015 20:48:59 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Ingo Molnar <mingo@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>
Cc:	linaro-kernel@...ts.linaro.org, linux-kernel@...r.kernel.org,
	Viresh Kumar <viresh.kumar@...aro.org>
Subject: [PATCH V2 0/3] timers: Allocate per-cpu tvec_base's statically

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

--
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/