Hi Frank,
On Mon, 15 Jul 2019 06:55:40 -0700
Frank Rowand <frowand.list@xxxxxxxxx> wrote:
> > Hmm, it's a kind of communication with the operator of the boot loader, since there
> > is an admin or developer behind it. I think the comminication is to communicate
> > with that human. Then if they intend to trace boot process, that is a kind of
> > communication.
>
> The quote from the plumbers 2016 devicetree etherpad ("Operating points are OK ...)
> conveniently ignores a sentence just a few lines later:
>
> "If firmware is deciding the operating point, then it's OK to convey it via DT."
>
> The operating points example is clearly communicating boot loader information to
> the kernel.
>
> Something the admin or developer wants to communicate is not boot loader
> information.
But the cmdline (bootargs) is already supported, I think this is a kind of bootargs.
> > [...]
> >>>>> - Can we use devicetree for configuring kernel dynamically?
> >>>>
> >>>> No. Sorry.
> >>>>
> >>>> My understanding of this proposal is that it is intended to better
> >>>> support boot time kernel and driver debugging. As an alternate
> >>>> implementation, could you compile the ftrace configuration information
> >>>> directly into a kernel data structure? It seems like it would not be
> >>>> very difficult to populate the data structure data via a few macros.
> >>>
> >>> No, that is not what I intended. My intention was to trace boot up
> >>> process "without recompiling kernel", but with a structured data.
> >>
> >> That is debugging. Or if you want to be pedantic, a complex performance
> >> measurement of the boot process (more than holding a stopwatch in your
> >> hand).
> >
> > Yeah, that's right.
> >
> >> Recompiling a single object file (containing the ftrace command data)
> >> and re-linking the kernel is not a big price in that context).
> >
> > No, if I can use DT, I can choose one of them while boot up.
> > That will be a big difference.
> > (Of course for that purpose, I should work on boot loader to support
> > DT overlay)
>
> This is debugging kernel drivers. I do not think that it is a big cost for
> a kernel developer to re-link the kernel. On any reasonable modern
> development system this should be a matter of seconds, not minutes.
Tracing is not only debugging the kernel drivers, but also measures
performance or behavior and compare with different settings.
Also, in some case, we can not change the binary, like distro kernel.
> Compiling a devicetree source is not significantly less time. (To be
> fair, you imply that you would have various compiled devicetrees to
> choose from at boot time. It may be realistic to have a library of
> ftrace commands, or it may be more realistic that someone debugging
> a kernel driver will create a unique ftrace command set for the
> particular case they are debugging.)
Yeah, devicetree build time may not be matter, decoupling from the
kernel image is, I think, the key point.
Thank you,
--
Masami Hiramatsu <mhiramat@xxxxxxxxxx>
