linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@sifive.com>
To: anup@brainfault.org
Cc: aou@eecs.berkeley.edu, Olof Johansson <olof@lixom.net>,
	atish.patra@wdc.com, Christoph Hellwig <hch@infradead.org>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	anup@brainfault.org
Subject: Re: [PATCH v2 2/2] RISC-V: defconfig: Enable printk timestamps
Date: Thu, 01 Nov 2018 10:54:47 -0700 (PDT)	[thread overview]
Message-ID: <mhng-f1ed976f-ca28-42af-bdb2-ee53e4585c2a@palmer-si-x1c4> (raw)
In-Reply-To: <20181101051033.10089-2-anup@brainfault.org>

On Wed, 31 Oct 2018 22:10:33 PDT (-0700), anup@brainfault.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@brainfault.org>
> Acked-by: Olof Johansson <olof@lixom.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.

  reply	other threads:[~2018-11-01 17:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01  5:10 [PATCH v2 1/2] RISC-V: refresh defconfig Anup Patel
2018-11-01  5:10 ` [PATCH v2 2/2] RISC-V: defconfig: Enable printk timestamps Anup Patel
2018-11-01 17:54   ` Palmer Dabbelt [this message]
2018-11-01 17:54 ` [PATCH v2 1/2] RISC-V: refresh defconfig Palmer Dabbelt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=mhng-f1ed976f-ca28-42af-bdb2-ee53e4585c2a@palmer-si-x1c4 \
    --to=palmer@sifive.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=atish.patra@wdc.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=olof@lixom.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).