From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752742AbdKVMi1 (ORCPT <rfc822;w@1wt.eu>);
        Wed, 22 Nov 2017 07:38:27 -0500
Received: from mail-pf0-f169.google.com ([209.85.192.169]:45977 "EHLO
        mail-pf0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752370AbdKVMi0 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 22 Nov 2017 07:38:26 -0500
X-Google-Smtp-Source: AGs4zMb2eIeCsdtCP843fVhIDnqUZe9fh00cSpdQcpEvDCnzTLfZ77wsJslCtOmEfTRNf/1R0jTjpg==
Date: Wed, 22 Nov 2017 21:38:21 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
        Kevin Hilman <khilman@baylibre.com>, Mark Brown <broonie@kernel.org>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        LKML <linux-kernel@vger.kernel.org>,
        Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
        Steven Rostedt <rostedt@goodmis.org>,
        Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: kernel CI: printk loglevels in kernel boot logs?
Message-ID: <20171122123821.GA697@jagdpanzerIV>
References: <CAOi56cVORdyjTXK4QGYRfyD1Q=QBgsU3B__gZT0xj6OBKaasLQ@mail.gmail.com>
 <20171122015610.x3kgzqgtwywlurmz@wfg-t540p.sh.intel.com>
 <20171122032702.zd5ouuugrxyemqbh@wfg-t540p.sh.intel.com>
 <20171122113448.sllaehmlqae7telk@pathway.suse.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20171122113448.sllaehmlqae7telk@pathway.suse.cz>
User-Agent: Mutt/1.9.1 (2017-09-22)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On (11/22/17 12:34), Petr Mladek wrote:
[..]
> > > > This is espeically useful when ingesting kernel logs into advanced
> > > > search/analytics frameworks (I'm playing with and ELK stack: Elastic
> > > > Search, Logstash, Kibana).
[..]
> To make it clear. I understand that "show_loglevel" command line argument
> would be useful for you. But I am afraid that it is not worth changing
> the format. There would need to be wide interest into the change.
> Also there would need to be evidence that the existing solutions
> (dmesg --raw, console_loglevel) are not enough in many real life
> scenarios.

well, I think that that "consoles_format=syslog" command line parameter
will be enabled only by those who actually want to have it - Fengguang's
build robot and kernelCI (+ may be more setups).  so I'd probably assume
there are low risks here. may be I'm wrong.

I think it makes sense to have syslog's format "<%u>[timestamp] text\n"
on serial consoles (time stamp when PRINTK_TIME set; <%u> when
consoles_format=syslog set).

	-ss