On 23/05/2015 01:23, Kevin O'Connor wrote: > Hi Paolo, > > I'm curious if you've tried profiling SeaBIOS to see where it is > spending unnecessary time? No, I really wanted to get the absolute minimum time needed to get to the kernel. I announced it publicly because I think it's also instructive. > I wonder if a stripped down SeaBIOS could > obtain sufficient performance. It most likely could. However, some of the features (e.g. booting vmlinuz from parallel flash or, in the future, from persistent memory) probably do not fit SeaBIOS very well. One would have to redo them otherwise, for example using a DMA interface in fw_cfg. Paolo > The page at http://seabios.org/Debugging#Timing_debug_messages > describes how to do basic profiling via timing of debug messages. > > The default SeaBIOS build takes ~180ms on my (old AMD) system. But, > by removing drivers and options via Kconfig I was able to bring it > down to ~25ms. I suspect some additional Kconfig settings and a few > optimizations would make it possible to significantly reduce this > time. > > Cheers, > -Kevin > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
