linux-kernel - Re: [PATCH 13/41] percpu: Add raw_cpu

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131210155546.GD1995@gmail.com>
Date:	Tue, 10 Dec 2013 16:55:46 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Tejun Heo <tj@...nel.org>
Cc:	Christoph Lameter <cl@...ux.com>, akpm@...uxfoundation.org,
	rostedt@...dmis.org, linux-kernel@...r.kernel.org,
	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 13/41] percpu: Add raw_cpu_ops


* Tejun Heo <tj@...nel.org> wrote:

> On Tue, Dec 10, 2013 at 04:45:06PM +0100, Ingo Molnar wrote:
> > 
> > * Tejun Heo <tj@...nel.org> wrote:
> > 
> > > On Tue, Dec 03, 2013 at 05:32:45PM -0600, Christoph Lameter wrote:
> > > > The patches following this one will add preemption checks to __this_cpu
> > > > ops so we need to have an alternative way to use this_cpu operations
> > > > without preemption checks.
> > > > 
> > > > raw_cpu_ops will be the basis for all other ops since these will be the
> > > > operations that do not implement any checks. 
> > > > 
> > > > Primitive operations are renamed by this patch from __this_cpu_xxx to
> > > > raw_cpu_xxxx.
> > > > 
> > > > Signed-off-by: Christoph Lameter <cl@...ux.com>
> > > 
> > > Applied to percpu/for-3.14.
> > 
> > Please also pick up the related debugging bits:
> > 
> >    [PATCH 18/41] percpu: Add preemption checks to __this_cpu ops
> > 
> > as we don't want to expand percpu ops without doing proper debugging.
> 
> Yeah, trying to figure out which should go through which tree. 
> Christoph, should I also pickup 14?  Or can that go through x86?

Well, it appears to have dependencies so I doubt it can be kept 
separate. In any case, provided all debugging is properly productized:

Acked-by: Ingo Molnar <mingo@...nel.org>

Thanks,

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