From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751789AbdHGNdw (ORCPT ); Mon, 7 Aug 2017 09:33:52 -0400 Received: from mail-pg0-f68.google.com ([74.125.83.68]:33576 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751375AbdHGNdt (ORCPT ); Mon, 7 Aug 2017 09:33:49 -0400 Date: Mon, 7 Aug 2017 22:34:03 +0900 From: Sergey Senozhatsky To: Prarit Bhargava Cc: Mark Salyzyn , linux-kernel@vger.kernel.org, Jonathan Corbet , Petr Mladek , Sergey Senozhatsky , Steven Rostedt , John Stultz , Thomas Gleixner , Stephen Boyd , Andrew Morton , Greg Kroah-Hartman , "Paul E. McKenney" , Christoffer Dall , Deepa Dinamani , Ingo Molnar , Joel Fernandes , Kees Cook , Peter Zijlstra , Geert Uytterhoeven , "Luis R. Rodriguez" , Nicholas Piggin , "Jason A. Donenfeld" , Olof Johansson , Josh Poimboeuf , linux-doc@vger.kernel.org Subject: Re: [PATCH v3] printk: Add boottime and real timestamps Message-ID: <20170807133403.GA405@jagdpanzerIV.localdomain> References: <1501809524-496-1-git-send-email-prarit@redhat.com> <3e0a0734-60ae-59b9-30bf-25cc966013da@android.com> <8aa07623-22ca-bf49-e81d-7cb9ec4e67fb@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8aa07623-22ca-bf49-e81d-7cb9ec4e67fb@redhat.com> User-Agent: Mutt/1.8.3 (2017-05-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (08/07/17 08:41), Prarit Bhargava wrote: [..] > >> +static int printk_time_set(const char *val, const struct kernel_param *kp) > >> +{ > >> + char *param = strstrip((char *)val); > >> + int _printk_time; > >> + > >> + if (strlen(param) != 1) > >> + return -EINVAL; > > (see below) strlen is so restrictive, wouldn't it be nice(tm) to allow "boot", > > "monotonic" or "realtime" strings? Certainly KISS can handle the first letters > > for next to zero cost. (switch statement optimization) > > Thanks Mark, > > I had asked this question before and didn't get an answer: Do I need to > worry about the ABI of /sys/modules/printk/parameters/time. Since it hasn't > been explicitly added to the stable ABI files, I'm going to assume it wasn't > important enough to add it. Looking at google, however, leads to a lot > of hits for 'printk.time' kernel parameters settings so I think I better > maintain the legacy boolean settings. yes, please. we have to preserve it. > I'm going to do: 0/n/N/1/y/Y to maintain the existing ABI, and add (as you > suggest above 'disable|local|boottime|monotonic|realtime' as valid > parameters. > > >> + > >> + switch (param[0]) { > >> + case '0': > >> + case 'n': > >> + case 'N': > > I would wish for a few more 'convenience' cases: > > > > case 'd': case 'D': /* Disable */ > > It would be trivial then to add only the lower case options (I dislike upper > case settings ...) by adding yes, please. lower case only. -ss