From: Masami Hiramatsu <mhiramat@kernel.org>
To: Padmanabha Srinivasaiah <treasure4paddy@gmail.com>
Cc: rostedt@goodmis.org, linux-kernel@vger.kernel.org
Subject: Re: tracing : bootconfig : Early boot config for non intrd systems
Date: Tue, 8 Mar 2022 16:36:00 +0900 [thread overview]
Message-ID: <20220308163600.3109f19854c7b051924f262b@kernel.org> (raw)
In-Reply-To: <20220307184011.GA2570@pswork>
Hello Padmanabha,
On Mon, 7 Mar 2022 19:40:11 +0100
Padmanabha Srinivasaiah <treasure4paddy@gmail.com> wrote:
> Hello Masami Hiramatsu,
>
> Thanks for detailed explanation on boot time tracing using early boot configuration file.
> https://linuxfoundation.org/wp-content/uploads/boottrace-LF-live-2021-update.pdf
>
> Also for https://lwn.net/Articles/806002/.
>
> Latter link also states we can embed boot config into the kernel image for non intrd based system.
Ah, that was an original plan, but since no one interested in, I didn't implement it.
So we still need the initrd for bootconfig.
>
> I tried searching mailing lists not able to find pointer for same.
>
> A hint/pointer on how-to will be very helpful.
BTW, what is your problem, could you share your use-case?
Thank you,
>
> Thanks and Regards,
> Padmanabha.S
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2022-03-08 7:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 18:40 tracing : bootconfig : Early boot config for non intrd systems Padmanabha Srinivasaiah
2022-03-08 7:36 ` Masami Hiramatsu [this message]
2022-03-08 17:48 ` Padmanabha Srinivasaiah
2022-03-09 8:01 ` Masami Hiramatsu
2022-03-09 19:06 ` Padmanabha Srinivasaiah
2022-03-12 6:53 ` Masami Hiramatsu
2022-03-12 15:15 ` Steven Rostedt
2022-03-12 15:16 ` Steven Rostedt
2022-03-13 7:48 ` Masami Hiramatsu
2022-03-13 9:40 ` Masami Hiramatsu
2022-03-16 14:06 ` Padmanabha Srinivasaiah
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=20220308163600.3109f19854c7b051924f262b@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=treasure4paddy@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.