Re: [GIT pull] printk updates for 4.15

From: Mark Salyzyn <salyzyn@android.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: Petr Mladek <pmladek@suse.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Prarit Bhargava <prarit@redhat.com>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [GIT pull] printk updates for 4.15
Date: Tue, 14 Nov 2017 13:16:14 -0800	[thread overview]
Message-ID: <7d23f705-1479-7874-7918-f2af9ec02c86@android.com> (raw)
In-Reply-To: <CA+55aFwNo9CDzuDWue7QJYd_iip4bgEqduVjNAHjxwdxjiur1g@mail.gmail.com>

On 11/14/2017 01:07 PM, Linus Torvalds wrote:
> But all of this is entirely separate from the "changing from one clock
> that has small issues for good reasons to FOUR DIFFERENT CLOCKS THAT
> THE USER CHOOSES RANDOMLY".

User is _root_ (assuming default perms for nodes), not some random user.

At least on an embedded Android platform, the only root user is init(8), 
so it can becomes a system boot time decision only.
> See my objection?
>
> One is "let's improve the clock".
>
> The other is "let's do something crazy and idiotic".

If configured and enabled, let's allow an embedded device the rights to 
chose the clock timebase for the ultimate in synchronization to other 
activities on the system (correlate with user space log timebase).

-- Mark