[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.9999.1912041128400.186402@viisi.sifive.com>
Date: Wed, 4 Dec 2019 11:38:49 -0800 (PST)
From: Paul Walmsley <paul.walmsley@...ive.com>
To: Alistair Francis <Alistair.Francis@....com>
cc: "anup@...infault.org" <anup@...infault.org>,
"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
Atish Patra <Atish.Patra@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"hch@....de" <hch@....de>
Subject: Re: [GIT PULL] Second set of RISC-V updates for v5.5-rc1
Alistair, Anup,
On Wed, 4 Dec 2019, Alistair Francis wrote:
> On Wed, 2019-12-04 at 18:22 +0530, Anup Patel wrote:
>
> > I had commented on your patch but my comments are still
> > not addressed.
> >
> > Various debug options enabled by this patch have performance
> > impact. Instead of enabling these debug options in primary
> > defconfigs, I suggest to have separate debug defconfigs with
> > these options enabled.
>
> +1
>
> OE uses the defconfig (as I'm sure other distros do) and slowing down
> users seems like a bad idea.
While I respect your points of view, our defconfigs are oriented towards
kernel developers. This is particularly important when right now the only
RISC-V hardware on the market are test chips. Our expectation is that
distros and benchmarkers will create their own Kconfigs for their needs.
Going forward, we'll probably add a few more validation and debug options,
as Palmer suggested during the patch discussion.
- Paul
Powered by blists - more mailing lists