From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-11.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 18A92C2D0A8 for ; Wed, 23 Sep 2020 13:56:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id A9FCE20C09 for ; Wed, 23 Sep 2020 13:56:39 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=suse.com header.i=@suse.com header.b="JUDBeM1B" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726582AbgIWN4i (ORCPT ); Wed, 23 Sep 2020 09:56:38 -0400 Received: from mx2.suse.de ([195.135.220.15]:49094 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726156AbgIWN4i (ORCPT ); Wed, 23 Sep 2020 09:56:38 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1600869397; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=KBx+gik6NBNzI5P+pAz4fybhKo40AHUvEejBWLTvCVg=; b=JUDBeM1BuLX57DzG2o7IYxSrOR9dLJ+1hVyxGOR9RuJKyWnFpMnggp0yXTFkxahayOREOL fHU3ytWzKkmWH3qIMwseDbMEkRoaDf1PSsJQcm4D7GokSlcNxozE8aLLmj+p1fsUF9LgvD B4VeW4eYb/vECDKEQLHvjAZTZyTjzog= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 9D081AC26; Wed, 23 Sep 2020 13:57:14 +0000 (UTC) From: Petr Mladek To: Sergey Senozhatsky , Steven Rostedt , John Ogness Cc: Linus Torvalds , Thomas Gleixner , Prarit Bhargava , Mark Salyzyn , Chunyan Zhang , Orson Zhai , Changki Kim , Sergey Senozhatsky , linux-kernel@vger.kernel.org, Petr Mladek Subject: [RFC 0/2] printk: Add more metadata for each record Date: Wed, 23 Sep 2020 15:56:15 +0200 Message-Id: <20200923135617.27149-1-pmladek@suse.com> X-Mailer: git-send-email 2.26.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org There have been repeated requests to store and print more metadata for each line, see the two patches for more details. This patchset handles the storing part so that we could do it together with the other changes of the ring buffer structure. It would be nice to get it into the same kernel release to reduce pain on the crash tools side. My proposal is to make this information available via /dev/kmsg as dictionary values. The console output would probably need to be configurable. I would ignore syslog syscall that is hard to extend and is basically obsoleted by /dev/kmsg. The patchset applies on top of the current printk/linux.git, branch printk-rework (after the dict ring removal). You also need to merge "timekeeping-for-printk-2020-08-23" tag from tip.git. It provides "struct ktime_timestamps" and ktime_get_fast_timestamps(). I still need to add the gdb-related changes if there is not a strong opposition to these changes. I just wanted to send what I had before starting review of the logbuf_lock removal patchset. Petr Mladek (2): printk: Store all three timestamps printk: Add more information about the printk caller kernel/printk/printk.c | 129 ++++++++++++++++++++---------- kernel/printk/printk_ringbuffer.c | 43 +++++----- kernel/printk/printk_ringbuffer.h | 42 +++++++++- 3 files changed, 148 insertions(+), 66 deletions(-) -- 2.26.2