well as u can see, boottime isn't detailed enough: http://puu.sh/gdRXp/fc8fc176ce.png
Maybe I can hack printf to act a boottime. On Thu, Feb 26, 2015 at 6:16 PM, Vladimir 'φ-coder/phcoder' Serbinenko <phco...@gmail.com> wrote: > On 26.02.2015 18:10, Michael Zimmermann wrote: >> >> Is there a way to create a performance profile so I can see what >> exactly needs so much time? I don't have JTAG but maybe UART+GDB could >> help with that. >> > Have a look at boot_time. > >> adding prints is kind of annoying :D >> >> On Thu, Feb 26, 2015 at 5:44 PM, Vladimir 'φ-coder/phcoder' Serbinenko >> <phco...@gmail.com> wrote: >>> >>> On 25.02.2015 19:46, Michael Zimmermann wrote: >>>> >>>> >>>> I'm still questioning the efficiency >>>> math operations because on slow devices there are other bottlenecks of >>>> the same kind(like de/compression). >>> >>> >>> That's pure speculation at that point. GRUB has 3 compression algorithms: >>> - minilzo. Has some divisions in parts which GRUB doesn't use. Those >>> parts >>> are easily disablable and I'll just do so. >>> - gzip. Uses division only in zlib header check. I'll optimise it a >>> little >>> but it's only one division in header check, not in compressed data body. >>> - xz. No divisions >>> >>> >>> _______________________________________________ >>> Grub-devel mailing list >>> Grub-devel@gnu.org >>> https://lists.gnu.org/mailman/listinfo/grub-devel >> >> >> _______________________________________________ >> Grub-devel mailing list >> Grub-devel@gnu.org >> https://lists.gnu.org/mailman/listinfo/grub-devel >> > > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/grub-devel _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
