how about this patch, do we really need this patch
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
how about this patch, do we really need this patch
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
I have a few answers for you.
> >>root@ME:/ cat /sys/kernel/debug/boottime/bootgraph
> >>[0.185254] calling splash+0x0/0x0
> >>[2.984335] initcall splash+0x0/0x0 returned 0 after 2799 msecs.
> >>[2.984335] calling autoboot_delay+0x0/0x0
> >>[4.089513]
I have a few answers for you.
root@ME:/ cat /sys/kernel/debug/boottime/bootgraph
[0.185254] calling splash+0x0/0x0
[2.984335] initcall splash+0x0/0x0 returned 0 after 2799 msecs.
[2.984335] calling autoboot_delay+0x0/0x0
[4.089513] initcall autoboot_delay+0x0/0x0 returned 0
> >>root@ME:/ cat /sys/kernel/debug/boottime/bootgraph
> >>[0.185254] calling splash+0x0/0x0
> >>[2.984335] initcall splash+0x0/0x0 returned 0 after 2799 msecs.
> >>[2.984335] calling autoboot_delay+0x0/0x0
> >>[4.089513] initcall autoboot_delay+0x0/0x0
root@ME:/ cat /sys/kernel/debug/boottime/bootgraph
[0.185254] calling splash+0x0/0x0
[2.984335] initcall splash+0x0/0x0 returned 0 after 2799 msecs.
[2.984335] calling autoboot_delay+0x0/0x0
[4.089513] initcall autoboot_delay+0x0/0x0 returned 0 after 1105
msecs.
[
On 10/12/2012 11:42 AM, Lee Jones wrote:
On Fri, 12 Oct 2012, Dan Murphy wrote:
On 10/12/2012 09:01 AM, Lee Jones wrote:
On Fri, 12 Oct 2012, Arnd Bergmann wrote:
On Friday 12 October 2012, Russell King - ARM Linux wrote:
root@ME:/ cat /sys/kernel/debug/boottime/bootgraph
[0.185254]
On 10/12/2012 11:42 AM, Lee Jones wrote:
On Fri, 12 Oct 2012, Dan Murphy wrote:
On 10/12/2012 09:01 AM, Lee Jones wrote:
On Fri, 12 Oct 2012, Arnd Bergmann wrote:
On Friday 12 October 2012, Russell King - ARM Linux wrote:
root@ME:/ cat /sys/kernel/debug/boottime/bootgraph
[0.185254]
On Fri, 12 Oct 2012, Dan Murphy wrote:
>
> On 10/12/2012 09:01 AM, Lee Jones wrote:
> >On Fri, 12 Oct 2012, Arnd Bergmann wrote:
> >
> >>On Friday 12 October 2012, Russell King - ARM Linux wrote:
> root@ME:/ cat /sys/kernel/debug/boottime/bootgraph
> [0.185254] calling
On 10/12/2012 09:01 AM, Lee Jones wrote:
On Fri, 12 Oct 2012, Arnd Bergmann wrote:
On Friday 12 October 2012, Russell King - ARM Linux wrote:
root@ME:/ cat /sys/kernel/debug/boottime/bootgraph
[0.185254] calling splash+0x0/0x0
[2.984335] initcall splash+0x0/0x0 returned 0 after 2799
On Fri, 12 Oct 2012, Arnd Bergmann wrote:
> On Friday 12 October 2012, Russell King - ARM Linux wrote:
> > > root@ME:/ cat /sys/kernel/debug/boottime/bootgraph
> > > [0.185254] calling splash+0x0/0x0
> > > [2.984335] initcall splash+0x0/0x0 returned 0 after 2799 msecs.
> > > [
On Friday 12 October 2012, Russell King - ARM Linux wrote:
> > root@ME:/ cat /sys/kernel/debug/boottime/bootgraph
> > [0.185254] calling splash+0x0/0x0
> > [2.984335] initcall splash+0x0/0x0 returned 0 after 2799 msecs.
> > [2.984335] calling autoboot_delay+0x0/0x0
> > [4.089513]
On Fri, Oct 12, 2012 at 02:45:42PM +0100, Lee Jones wrote:
> That's odd. I get:
>
> root@ME:/ cat sys/boottime/bootloader
> 0
>
> root@ME:/ cat sys/boottime/kernel
> 4276
>
> root@ME:/ cat /sys/kernel/debug/boottime/summary
> kernel: 4276 msecs
> total: 4276 msecs
>
> root@ME:/ cat
On Fri, 12 Oct 2012, Dan Murphy wrote:
> On a note on testing.
>
> OK this at least compiles on my system with 3.4.
>
> The weird thing is that I get the same exact kernel boot time for
> two different machines.
> When I cat the summary for the kernel.
> I am not profiling the bootloader time
On a note on testing.
OK this at least compiles on my system with 3.4.
The weird thing is that I get the same exact kernel boot time for two
different machines.
When I cat the summary for the kernel.
I am not profiling the bootloader time here as it is neglible so no ATAG
argument.
kernel:
Okay, please disgard the last patch. Lots of fixups since.
Author: Lee Jones
Date: Wed Jun 30 14:00:40 2010 +0200
Boottime: A tool for automatic measurement of kernel/bootloader boot time
The overhead is very low and the results will be found under
sysfs/bootime, as well as
On Thu, 11 Oct 2012, Nishanth Menon wrote:
> On 15:42-20121011, Lee Jones wrote:
> > From: Jonas Aaberg
> >
> > The overhead is very low and the results will be found under
> > sysfs/bootime, as well as detailed results in debugfs under
> > boottime/. The bootgraph* files are compatible with
>
On Thu, 11 Oct 2012, Nishanth Menon wrote:
On 15:42-20121011, Lee Jones wrote:
From: Jonas Aaberg jonas.ab...@stericsson.com
The overhead is very low and the results will be found under
sysfs/bootime, as well as detailed results in debugfs under
boottime/. The bootgraph* files are
Okay, please disgard the last patch. Lots of fixups since.
Author: Lee Jones lee.jo...@linaro.org
Date: Wed Jun 30 14:00:40 2010 +0200
Boottime: A tool for automatic measurement of kernel/bootloader boot time
The overhead is very low and the results will be found under
On a note on testing.
OK this at least compiles on my system with 3.4.
The weird thing is that I get the same exact kernel boot time for two
different machines.
When I cat the summary for the kernel.
I am not profiling the bootloader time here as it is neglible so no ATAG
argument.
kernel:
On Fri, 12 Oct 2012, Dan Murphy wrote:
On a note on testing.
OK this at least compiles on my system with 3.4.
The weird thing is that I get the same exact kernel boot time for
two different machines.
When I cat the summary for the kernel.
I am not profiling the bootloader time here as
On Fri, Oct 12, 2012 at 02:45:42PM +0100, Lee Jones wrote:
That's odd. I get:
root@ME:/ cat sys/boottime/bootloader
0
root@ME:/ cat sys/boottime/kernel
4276
root@ME:/ cat /sys/kernel/debug/boottime/summary
kernel: 4276 msecs
total: 4276 msecs
root@ME:/ cat
On Friday 12 October 2012, Russell King - ARM Linux wrote:
root@ME:/ cat /sys/kernel/debug/boottime/bootgraph
[0.185254] calling splash+0x0/0x0
[2.984335] initcall splash+0x0/0x0 returned 0 after 2799 msecs.
[2.984335] calling autoboot_delay+0x0/0x0
[4.089513] initcall
On Fri, 12 Oct 2012, Arnd Bergmann wrote:
On Friday 12 October 2012, Russell King - ARM Linux wrote:
root@ME:/ cat /sys/kernel/debug/boottime/bootgraph
[0.185254] calling splash+0x0/0x0
[2.984335] initcall splash+0x0/0x0 returned 0 after 2799 msecs.
[2.984335] calling
On 10/12/2012 09:01 AM, Lee Jones wrote:
On Fri, 12 Oct 2012, Arnd Bergmann wrote:
On Friday 12 October 2012, Russell King - ARM Linux wrote:
root@ME:/ cat /sys/kernel/debug/boottime/bootgraph
[0.185254] calling splash+0x0/0x0
[2.984335] initcall splash+0x0/0x0 returned 0 after 2799
On Fri, 12 Oct 2012, Dan Murphy wrote:
On 10/12/2012 09:01 AM, Lee Jones wrote:
On Fri, 12 Oct 2012, Arnd Bergmann wrote:
On Friday 12 October 2012, Russell King - ARM Linux wrote:
root@ME:/ cat /sys/kernel/debug/boottime/bootgraph
[0.185254] calling splash+0x0/0x0
[2.984335]
On 15:42-20121011, Lee Jones wrote:
> From: Jonas Aaberg
>
> The overhead is very low and the results will be found under
> sysfs/bootime, as well as detailed results in debugfs under
> boottime/. The bootgraph* files are compatible with
> scripts/bootgraph.pl. The reason for this patch is to
On Thu, 11 Oct 2012, Christian Gmeiner wrote:
> 2012/10/11 Lee Jones :
> > From: Jonas Aaberg
> >
> > The overhead is very low and the results will be found under
> > sysfs/bootime, as well as detailed results in debugfs under
> > boottime/. The bootgraph* files are compatible with
> >
From: Jonas Aaberg
The overhead is very low and the results will be found under
sysfs/bootime, as well as detailed results in debugfs under
boottime/. The bootgraph* files are compatible with
scripts/bootgraph.pl. The reason for this patch is to provide
data (sysfs/boottime) suitable for
From: Jonas Aaberg jonas.ab...@stericsson.com
The overhead is very low and the results will be found under
sysfs/bootime, as well as detailed results in debugfs under
boottime/. The bootgraph* files are compatible with
scripts/bootgraph.pl. The reason for this patch is to provide
data
On Thu, 11 Oct 2012, Christian Gmeiner wrote:
2012/10/11 Lee Jones lee.jo...@linaro.org:
From: Jonas Aaberg jonas.ab...@stericsson.com
The overhead is very low and the results will be found under
sysfs/bootime, as well as detailed results in debugfs under
boottime/. The bootgraph*
On 15:42-20121011, Lee Jones wrote:
From: Jonas Aaberg jonas.ab...@stericsson.com
The overhead is very low and the results will be found under
sysfs/bootime, as well as detailed results in debugfs under
boottime/. The bootgraph* files are compatible with
scripts/bootgraph.pl. The reason for
32 matches
Mail list logo
