From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Pratyush Brahma <quic_pbrahma@quicinc.com>,
"danielwa@cisco.com" <danielwa@cisco.com>
Cc: Pavan Kondeti <quic_pkondeti@quicinc.com>,
"tomas.mudrunka@gmail.com" <tomas.mudrunka@gmail.com>,
"quic_vjitta@quicinc.com" <quic_vjitta@quicinc.com>,
"xe-linux-external@cisco.com" <xe-linux-external@cisco.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"quic_guptap@quicinc.com" <quic_guptap@quicinc.com>,
"maksym.kokhan@globallogic.com" <maksym.kokhan@globallogic.com>,
"dwalker@fifo99.com" <dwalker@fifo99.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 1/4] add generic builtin command line
Date: Wed, 8 Nov 2023 11:33:37 +0000 [thread overview]
Message-ID: <3d127abf-abdc-02e3-7c8b-a39b901ea641@csgroup.eu> (raw)
In-Reply-To: <4c420081-fe57-d036-ded7-2899c13738ee@quicinc.com>
Hi Pratyush,
Le 17/10/2023 à 12:40, Pratyush Brahma a écrit :
> Hi Daniel
>
> We have a usecase which requires this patch necessarily. For android
> usecases, we have two different build variants
> differentiated by defconfigs - production and debug. However, we only
> have a single dts for both these variants.
>
>
> We want to enable certain features like page owner and slub debug which
> require cmdline params in addition to
> their respective configs to be enabled. Enabling page_owner and
> slub_debug options in dts file enables it for both
> production and debug variants. These features have significant memory
> overhead which are undesirable for
> our production environment. However, these are necessary for debug
> environment to enable internal testing and debug.
> Currently, android uses out-of-tree configs like CONFIG_CMDLINE_EXTEND
> to do so in gki_defconfig [1].
> One option is to use CMDLINE_FORCE option which would enable these
> cmdline params but this disables the bootloader to add
> any additional cmdline params which may be necessary.
>
>
> For such a usecase, the CONFIG_CMDLINE_PREPEND seems to be quite useful
> as it would help to stitch bootloader
> and the desired build variant's configs together. Can you please help to
> merge this patch?
As far as I remember, Daniel's proposal had some weaknesses that were
never addressed. At that time I proposed an alternative series that was
addressing most weaknesses, and my series was considered more mature
that Daniel's one by several maintainers. But I never got enough
feedback on it in order to finalise and merge it.
Could you have a look at it and tell if it fits your need ? See
https://patchwork.ozlabs.org/project/linuxppc-dev/list/?state=*&series=237158
If it does, I can then rebase it on latest kernel and restart
discussions in order to get it merged.
Thanks
Christophe
>
>
> [1]
> https://android.googlesource.com/kernel/common/+/refs/heads/android14-6.1-lts/arch/arm64/configs/gki_defconfig#62
>
next prev parent reply other threads:[~2023-11-08 11:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 23:24 [PATCH 1/4] add generic builtin command line Daniel Walker
2019-03-20 22:53 ` Andrew Morton
2019-03-20 23:23 ` Daniel Walker
2019-03-21 3:14 ` Andrew Morton
2019-03-21 15:13 ` Daniel Walker
2019-03-21 22:15 ` Andrew Morton
2021-02-15 19:32 ` Daniel Gimpelevich
2021-02-16 17:42 ` Christophe Leroy
2021-02-16 21:20 ` Daniel Gimpelevich
2021-02-16 19:02 ` Daniel Walker
2021-02-17 21:16 ` Andrew Morton
2023-04-17 16:18 ` Tomas Mudrunka
2023-04-17 16:24 ` Daniel Walker (danielwa)
2023-10-17 10:40 ` Pratyush Brahma
2023-10-17 14:21 ` Daniel Walker (danielwa)
2023-10-19 6:43 ` Pratyush Brahma
2023-11-08 11:33 ` Christophe Leroy [this message]
2023-11-08 16:23 ` Daniel Walker (danielwa)
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=3d127abf-abdc-02e3-7c8b-a39b901ea641@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=akpm@linux-foundation.org \
--cc=danielwa@cisco.com \
--cc=dwalker@fifo99.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maksym.kokhan@globallogic.com \
--cc=quic_guptap@quicinc.com \
--cc=quic_pbrahma@quicinc.com \
--cc=quic_pkondeti@quicinc.com \
--cc=quic_vjitta@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=tomas.mudrunka@gmail.com \
--cc=xe-linux-external@cisco.com \
/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).