Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 4 Dec 2019 19:03:19 -0800 (PST)
From:   Paul Walmsley <paul.walmsley@sifive.com>
To:     Anup Patel <Anup.Patel@wdc.com>
cc:     Palmer Dabbelt <palmer@dabbelt.com>,
        Albert Ou <aou@eecs.berkeley.edu>,
        Atish Patra <Atish.Patra@wdc.com>,
        Alistair Francis <Alistair.Francis@wdc.com>,
        Christoph Hellwig <hch@lst.de>,
        Anup Patel <anup@brainfault.org>,
        "linux-riscv@lists.infradead.org" <linux-riscv@lists.infradead.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] RISC-V: Add debug defconfigs
In-Reply-To: <20191205005601.1559-1-anup.patel@wdc.com>
Message-ID: <alpine.DEB.2.21.9999.1912041859070.215427@viisi.sifive.com>
References: <20191205005601.1559-1-anup.patel@wdc.com>
User-Agent: Alpine 2.21.9999 (DEB 301 2018-08-15)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, 5 Dec 2019, Anup Patel wrote:

> Various Linux kernel DEBUG options have big performance impact
> so these should not be enabled in RISC-V normal defconfigs.
> 
> Instead we should have separate RISC-V debug defconfigs having
> these DEBUG options enabled. This way Linux RISC-V can build both
> non-debug and debug kernels separately.

I respect your point of view, but until the RISC-V kernel port is more 
mature, I personally am not planning to merge this patch, for reasons 
discussed in the defconfig patch descriptions and the subsequent pull 
request threads.

I'm sure we'll revisit this in the future to realign with the defconfig 
debug settings for more mature architecture ports - but my guess is that 
we'll probably avoid creating debug_defconfigs, since only S390 does that.


- Paul