linux-kernel - Re: [PATCH] sched: Add preempt checks in preempt

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: <20160321103507.3dd01046@gandalf.local.home>
Date:	Mon, 21 Mar 2016 10:35:07 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] sched: Add preempt checks in preempt_schedule() code

On Mon, 21 Mar 2016 15:11:45 +0100
Peter Zijlstra <peterz@...radead.org> wrote:

> So the problem with preempt_enable_trace() is that we just called a
> _notrace(), and while I now know these are two different trace thingies,
> I might have forgotten that in a few days.
> 

What about preempt_latency_start() for the disable, and
preempt_latency_stop() for the enable? Make it more like a stop watch?

-- Steve