linux-kernel - Re: [PATCH v2 2/2] RISC-V: defconfig: Enable printk timestamps

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <mhng-f1ed976f-ca28-42af-bdb2-ee53e4585c2a@palmer-si-x1c4>
Date:   Thu, 01 Nov 2018 10:54:47 -0700 (PDT)
From:   Palmer Dabbelt <palmer@...ive.com>
To:     anup@...infault.org
CC:     aou@...s.berkeley.edu, Olof Johansson <olof@...om.net>,
        atish.patra@....com, Christoph Hellwig <hch@...radead.org>,
        linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
        anup@...infault.org
Subject:     Re: [PATCH v2 2/2] RISC-V: defconfig: Enable printk timestamps

On Wed, 31 Oct 2018 22:10:33 PDT (-0700), anup@...infault.org wrote:
> The printk timestamps are very useful information to visually see
> where kernel is spending time during boot. It also helps us see
> the timing of hotplug events at runtime.
>
> This patch enables printk timestamps in RISC-V defconfig so that
> we have it enabled by default (similar to other architectures
> such as x86_64, arm64, etc).
>
> Signed-off-by: Anup Patel <anup@...infault.org>
> Acked-by: Olof Johansson <olof@...om.net>
> ---
>  arch/riscv/configs/defconfig | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/arch/riscv/configs/defconfig b/arch/riscv/configs/defconfig
> index 07fa9ea75fea..ef4f15df9adf 100644
> --- a/arch/riscv/configs/defconfig
> +++ b/arch/riscv/configs/defconfig
> @@ -76,4 +76,5 @@ CONFIG_NFS_V4_1=y
>  CONFIG_NFS_V4_2=y
>  CONFIG_ROOT_NFS=y
>  CONFIG_CRYPTO_USER_API_HASH=y
> +CONFIG_PRINTK_TIME=y
>  # CONFIG_RCU_TRACE is not set

Thanks.  Since this is a functional change I'm not going to rush it in, but I 
think it's OK to go in after rc1 so I'll include it as part of my 
regularly-scheduled PR next week.