From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760792AbcAMNq4 (ORCPT ); Wed, 13 Jan 2016 08:46:56 -0500 Received: from www.linutronix.de ([62.245.132.108]:49911 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753277AbcAMNqy (ORCPT ); Wed, 13 Jan 2016 08:46:54 -0500 Date: Wed, 13 Jan 2016 14:45:54 +0100 (CET) From: Thomas Gleixner To: Prarit Bhargava cc: linux-kernel@vger.kernel.org, John Stultz , Xunlei Pang , Baolin Wang , Andrew Morton , Greg Kroah-Hartman , Petr Mladek , Tejun Heo , Peter Hurley , Vasily Averin , Joe Perches Subject: Re: [PATCH 0/2] printk, Add printk.clock kernel parameter [v2] In-Reply-To: <1452688466-14877-1-git-send-email-prarit@redhat.com> Message-ID: References: <1452688466-14877-1-git-send-email-prarit@redhat.com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 13 Jan 2016, Prarit Bhargava wrote: > This patchset introduces additional NMI safe timekeeping functions and the > kernel parameter printk.clock=[local|boot|real|tai] allowing a > user to specify an adjusted clock to use with printk timestamps. The > hardware clock, or the existing functionality, is preserved by default. You still fail to explain WHY we need a gazillion of different clocks here. What's the problem with using the fast monotonic clock instead of local_clock and be done with it? I really don't see the point why we would need boot/real/tai and all the extra churn in the fast clock. Thanks, tglx