linux-kernel - Re: [PATCH] ring-buffer: More precise time stamps for nested writes

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

Message-ID: <20150327181717.7f244cb6@gandalf.local.home>
Date:	Fri, 27 Mar 2015 18:17:17 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Paul Mackerras <paulus@...ba.org>
Cc:	"Suresh E. Warrier" <warrier@...ux.vnet.ibm.com>,
	linux-kernel@...r.kernel.org,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH] ring-buffer: More precise time stamps for nested writes

On Sat, 28 Mar 2015 09:14:30 +1100
Paul Mackerras <paulus@...ba.org> wrote:


> > It can be done cleanly if you encapsulate it properly.
> 
> Sure, but what is the advantage to using a static branch?  When would
> you ever want a single kernel image that could run either way
> depending on what machine it was running on?

For x86 you don't want it, unless you want to see interrupts
serialized, where some times you do.

It's not just an arch thing.

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