From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Murray <amurray@mpc-data.co.uk>
Date: Thu, 1 Sep 2011 00:25:35 +0100
Subject: [U-Boot] [PATCH 0/7] Bootgraph.pl instrumentation support for
	UBoot
In-Reply-To: <CAPnjgZ2SQd1R51SJKpFMUd7P-zqXvSzNzsC7_SB1a4=L4VZ0JA@mail.gmail.com>
References: <1314829261-13996-1-git-send-email-amurray@theiet.org>
	<201108311847.56266.vapier@gentoo.org>
	<CAPnjgZ2SQd1R51SJKpFMUd7P-zqXvSzNzsC7_SB1a4=L4VZ0JA@mail.gmail.com>
Message-ID: <CAJK_gi62zpnXtXVpdc6HbKZ9=gCwA0EKN7AXgpMvXjAT-ovXfA@mail.gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 1 September 2011 00:12, Simon Glass <sjg@chromium.org> wrote:
> Hi Mike,
>
> On Wed, Aug 31, 2011 at 3:47 PM, Mike Frysinger <vapier@gentoo.org> wrote:
>> On Wednesday, August 31, 2011 18:20:54 Andrew Murray wrote:
>>> This patchset introduces the CONFIG_BOOT_TRACE option which provides
>>> support for boot time instrumentation.
>>>
>>> When enabled printf output is prefixed with timing information (similar to
>>> the kernel's CONFIG_PRINTK_TIME option) and additional output is generated
>>> which instruments functions and commands called (much like the kernel's
>>> initcall_debug functionality).
>>>
>>> The kernel's bootgraph.pl script has been ported to render UBoots
>>> instrumented ouptut into a pretty SVG graph. An example of this can be
>>> found here: http://goo.gl/dX8aR - which shows the boot time of a Beagle
>>> board.
>>>
>>> The patch currently provides support for instrumentation of UBoot commands
>>> (e.g. U_BOOT_CMD) for all platforms but only when the HUSH shell is not in
>>> use. Initialisation instrumentation is only limited to the
>>> arch/arm/lib/board.c file at present but can very easily be extended to
>>> other relevant files.
>>
>> i feel like we've had similar ideas tossed around semi-recently. ?am i just
>> misremembering ?
>> -mike
>>
>
> Yes, for example:
>
> http://patchwork.ozlabs.org/patch/95513/
>
> It got caught up with a big discussion about whether we want a
> microsecond timer. There is now one in Tegra, but not in the generic
> timer API. There was also a request to unify this with the
> boot_progress stuff (i.e. it turned into a big cleanup).
>
> I haven't got back to it yet, but could probably do something next week.
>
> I also have patches to pass the timings to the kernel and have it
> report them to user space through a device. Planning to send an RFC to
> the LKML about that probably next week as well. Could be fun.
>
> Regards,
> Simon
>

Ah - my bad. I only subscribed to the mailing list today (my first
UBoot patch) and didn't notice this previous work.

Is there any cross over between my approach and what is
planned/already been done?

Andrew Murray