mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Tom Zanussi <zanussi@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [GIT PULL] tracing: Changes for 5.6
Date: Tue, 4 Feb 2020 08:46:42 -0500	[thread overview]
Message-ID: <20200204084642.450b6ebd@oasis.local.home> (raw)
In-Reply-To: <CAHk-=wg2Wk9ZgVBDCBHa3-b0fSfByiRJnGA_F8snMy=3HHg_gw@mail.gmail.com>

On Tue, 4 Feb 2020 13:19:06 +0000
Linus Torvalds <torvalds@linux-foundation.org> wrote:

> 
> Because it strikes me that the bootconfig should be the special case
> (ie "bootconfig does setup for boot-time tracing"), and that you
> should explicitly say "I want you to read the extended config" on the
> regular kernel command line.
> 
> So from looking at this, I do have to say that I'd have a slight
> preference for simply making this be an option like
> "config=bootconfig" that says "extend cmdline with the data from the
> 'bootconfig' file".

OK, I like this idea. As the current approach "silently" adds the boot
config, it may be surprising to someone that the configs are changing
(if they don't know to look for /proc/bootconfig).

Having a "config=bootconfig" required for reading makes it implicit
that a bootconfig is added to the existing command line, from just
looking at /proc/cmdline, and removing an added "config=bootconfig" 

> 
> Would that be horribly painful for your uses?
> 

I have no problem with this approach. Masami, are you OK with this?

I'll send a v2 implementing this change shortly.

-- Steve

  reply	other threads:[~2020-02-04 13:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 10:31 Steven Rostedt
2020-02-04 11:54 ` Linus Torvalds
2020-02-04 12:28   ` Steven Rostedt
2020-02-04 12:43     ` [PATCH] bootconfig: Add "disable_bootconfig" cmdline option to disable bootconfig Steven Rostedt
2020-02-04 13:19     ` [GIT PULL] tracing: Changes for 5.6 Linus Torvalds
2020-02-04 13:46       ` Steven Rostedt [this message]
2020-02-04 14:25         ` [PATCH v2] bootconfig: Only load bootconfig if "config=bootconfig" is on the kernel cmdline (was: bootconfig: Add "disable_bootconfig" cmdline option to disable bootconfig) Steven Rostedt
2020-02-04 14:33           ` Steven Rostedt
2020-02-04 15:43             ` Linus Torvalds

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=20200204084642.450b6ebd@oasis.local.home \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=zanussi@kernel.org \
    /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

all inboxes | Powered by JetHome®