Re: [Request for review] Profiling the FreeBSD kernel boot

2017-12-22 Thread Colin Percival
On 12/22/17 09:08, Mark Johnston wrote: > On Fri, Dec 22, 2017 at 09:44:46AM +, Colin Percival wrote: >> For the past few months I've been working on code for profiling the FreeBSD >> "kernel boot", i.e., everything between when kernel code starts running and >> when we first enter userland as

Re: [Request for review] Profiling the FreeBSD kernel boot

2017-12-22 Thread Mark Johnston
On Fri, Dec 22, 2017 at 09:44:46AM +, Colin Percival wrote: > Hi everyone, > > For the past few months I've been working on code for profiling the FreeBSD > "kernel boot", i.e., everything between when kernel code starts running and > when we first enter userland as init(8). This is not

Re: [Request for review] Profiling the FreeBSD kernel boot

2017-12-22 Thread blubee blubeeme
On Fri, Dec 22, 2017 at 5:44 PM, Colin Percival wrote: > Hi everyone, > > For the past few months I've been working on code for profiling the FreeBSD > "kernel boot", i.e., everything between when kernel code starts running and > when we first enter userland as init(8).

Re: [Request for review] Profiling the FreeBSD kernel boot

2017-12-22 Thread Hans Petter Selasky
On 12/22/17 10:44, Colin Percival wrote: track down the places where we're wasting time during the boot, and then to fix them. Hi, The USB stack will try to enumerate all USB controllers simultaneously. DELAY() is frequently a problem having to wait for chips to reset during enumeration as

[Request for review] Profiling the FreeBSD kernel boot

2017-12-22 Thread Colin Percival
Hi everyone, For the past few months I've been working on code for profiling the FreeBSD "kernel boot", i.e., everything between when kernel code starts running and when we first enter userland as init(8). This is not trivial since it's impossible to use tools like dtrace to monitor things prior