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=-3.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no 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 D787BC63697 for ; Thu, 19 Nov 2020 18:09:01 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 4F04E2225B for ; Thu, 19 Nov 2020 18:09:01 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="NU01fAl1"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=linux.microsoft.com header.i=@linux.microsoft.com header.b="P5ksUOWc" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4F04E2225B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.microsoft.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=dkEs/Kf9rFNtyosH5pxaQ9enF0YaB9FZNe09eKNCYKA=; b=NU01fAl1nXVwjsVSp6IQRK8U1 9xXmLg287DMxa0+vlobenbZazBGeAk4SIxlz2LxhViAnmdoipkYvY8yFyNVXEYDUqzHhry8QyDnV6 nfEXMmqeUZ6RZoxxJUHjVD+rL5r5HPS2nlr4iQl+on/8vKN+y7Lo0prhNABzvYJr6JLsA1TvQI7bV KpJ/HGWqkhTZs9NskNx8lpXLuxr5noLxXgffcs+BAOzM3Dhptw+xAZE01LVqaJ3MHCy1NsUR3OsT9 kwZT7Fa4YNpSpnh0Cs0Vu6JAD/cp3FvJaKJgIM/0/YoCvGYuwHxiHzpS9fzyfUJAybyVJcuOai/+J ch+qiSHxg==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kfoLd-0003xn-8R; Thu, 19 Nov 2020 18:07:57 +0000 Received: from linux.microsoft.com ([13.77.154.182]) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kfnEH-0005Dn-Ke for linux-arm-kernel@lists.infradead.org; Thu, 19 Nov 2020 16:56:40 +0000 Received: from sequoia (162-237-133-238.lightspeed.rcsntx.sbcglobal.net [162.237.133.238]) by linux.microsoft.com (Postfix) with ESMTPSA id 8ABEE20B717A; Thu, 19 Nov 2020 08:56:14 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 8ABEE20B717A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1605804975; bh=ToNxDyfGA4wixS43zJTeceyWT80apD0yIIOjKTZu5rE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=P5ksUOWchJroHHytE3K+6dqWBFzXYVxjICKBXfBV6SRBRhc+v1WETY5j8vacFlpz8 V7I/1mwfrfXx/DQFN52nQD4CrSoedHaaOdYeTiXkXLNMIQLOYt0h9o4jtUglbkbDiU YAY1kUGNZNcd3uDvxnybPt8ipohfRPLHaVRxbKPA= Date: Thu, 19 Nov 2020 10:56:12 -0600 From: Tyler Hicks To: Will Deacon Subject: Re: [PATCH 0/2] arm64: Implement CONFIG_CMDLINE_EXTEND Message-ID: <20201119165612.GB3973@sequoia> References: <20200921191557.350256-1-tyhicks@linux.microsoft.com> <20201103155952.GA4335@sequoia> <20201104120812.GA6632@willie-the-truck> <20201105054009.GA4472@sequoia> <20201105095853.GA7952@willie-the-truck> <20201105152836.GB4472@sequoia> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20201105152836.GB4472@sequoia> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20201119_115618_009902_50F97A98 X-CRM114-Status: GOOD ( 36.02 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Catalin Marinas , Rob Herring , Pavel Tatashin , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 2020-11-05 09:28:38, Tyler Hicks wrote: > On 2020-11-05 09:58:54, Will Deacon wrote: > > On Wed, Nov 04, 2020 at 11:40:09PM -0600, Tyler Hicks wrote: > > > On 2020-11-04 12:08:12, Will Deacon wrote: > > > > On Tue, Nov 03, 2020 at 09:59:52AM -0600, Tyler Hicks wrote: > > > > > On 2020-09-21 14:15:55, Tyler Hicks wrote: > > > > > > Provide the CONFIG_CMDLINE_EXTEND config option for arm64 kernels. This > > > > > > config option can be used to extend the kernel command line parameters, > > > > > > specified by the bootloader, with additional command line parameters > > > > > > specified in the kernel configuration. > > > > > > > > > > Hi Catalin and Will - Friendly ping on this series now that we're > > > > > on the other side of the 5.10 merge window. I hope it can be considered > > > > > for 5.10+1. Let me know if I need to rebase/resubmit. Thanks! > > > > > > > > Can you use bootconfig to achieve what you need? > > > > > > Thanks for mentioning bootconfig. I hadn't considered it. > > > > > > After reading the docs and code, I see a few reasons why I can't use it > > > out of the box: > > > > > > 1) It requires "bootconfig" to be appended to the kernel command line. > > > My proposed patch series makes it possible to append new options to > > > the kernel command line in situations where the bootloader is not > > > interactive. This presents a circular dependency problem for my use > > > case. > > > > > > A new config option could be added to force the enablement of > > > bootconfig but that would sort of be a single-use duplicate of > > > CONFIG_CMDLINE_EXTEND's functionality. > > > > > > 2) Not all kernel command line options can be configured using > > > bootconfig. For example, the "nokaslr" and "crashkernel=" parameters > > > are parsed/handled before setup_boot_config() is called. KASLR can > > > be disabled via a kernel config change but there's no config option > > > equivalent for "crashkernel=". Changing the "crashkernel=" command > > > line option is something that I need to support because a > > > development/debug kernel build often requires a larger reservation > > > and we find ourselves adjusting the "crashkernel=" value fairly > > > often. > > > > > > 3) External FIT image build systems do not yet support bootconfig since > > > it is so new. It is completely fair if you file this away in your > > > not-my-problem folder but simple kernel config modifications, as > > > needed for CONFIG_CMDLINE_EXTEND, are something that every image > > > build system is likely to support today. > > > > > > All that said, I do really like the look of bootconfig. Unfortunately, > > > it doesn't let me achieve everything I need. > > > > Ok, well thanks for having a look. A follow-up question I have is how is > > this handled on x86? They don't appear to have CONFIG_CMDLINE_EXTEND either > > afaict. Is it because their bootloader story tends to be more uniform? > > x86's equivalent was implemented by commit 516cbf3730c4 ("x86, bootup: > add built-in kernel command line for x86 (v2)"). To summarize, you have > to enable CONFIG_CMDLINE_BOOL and then that lets you define built-in > command line parameters in CONFIG_CMDLINE. However, it is backwards in > that the command line provided by the bootloader is appended onto the > end of CONFIG_CMDLINE. > > This doesn't seem as useful to me because, using the crashkernel= > example from above, the bootloader provided crashkernel= value may need > to be overridden by the built-in command line to provide a different > crashkernel= value for the particular kernel build being booted. Most > kernel command line parameter parsers are implemented in a way that > supports multiple instances of the parameter while only honoring the > last instance. Hey Will - Do you any additional concerns that I should look into? Thanks! Tyler > > Tyler > > > > > Will > > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel