Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
Date:   Tue, 8 Mar 2022 16:36:00 +0900
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
Message-Id: <20220308163600.3109f19854c7b051924f262b@kernel.org>
In-Reply-To: <20220307184011.GA2570@pswork>
References: <20220307184011.GA2570@pswork>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

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>