Messages in this thread | | | From | Geert Uytterhoeven <> | Date | Fri, 7 Feb 2020 09:59:27 +0100 | Subject | Re: [for-next][PATCH 04/26] bootconfig: Add Extra Boot Config support |
| |
Hi Steven,
On Thu, Feb 6, 2020 at 11:40 PM Steven Rostedt <rostedt@goodmis.org> wrote: > On Thu, 6 Feb 2020 10:10:28 -0800 > Randy Dunlap <rdunlap@infradead.org> wrote: > > old news: some Kconfig symbols are Special & Important. ;) > > Well, to me its as important as the kernel command line itself, and > printk(). I know printk() can be disabled, should that be default 'n'? > > What I really like about this, is that you can have custom kernel > configs for each initrd. My fear is if this is default off, an initrd
s/configs/command lines/?
> that use to boot may no longer boot, because of a forgotten enabling of > this.
I may be missing something here, but 12 KiB for extra command line support sounds a bit excessive to me. Currently the maximum value of COMMAND_LINE_SIZE is 4096, while many architectures still use 256 or 512. How much data do you want to pass? What kind of configuration do you want to pass? Is there some existing data structure you can use to hold this?
Thanks!
Gr{oetje,eeting}s,
Geert
-- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
| |