Profiling

[Amjad50]

Summary

Add profiling support for the kernel through qemu and qmp protocl

This works by attacking to qmp socket and fetching the current stack by using gdb commands through qemu.
Then we get a stack.folded file where we can generate flamegraph with or use it in https://www.speedscope.app/

This now will make profiling and optimizing the OS so much simpler

Related issue

• Kernel Profiling #118 (even though this wasn't the intended way, but this works so well)
• Userspace profiling #119 (this kinda implements userspace profiling as well, but I don't like it so much so I won't make it finished)
  • actually, turns out, we can implement very robust and nice userspace profiling, I would say userspace profiling is also done, but maybe for the future, let's make a profiler in our kernel that will profile userspace processes only.

Changes

• Add xtask profile command where it will attach to ./qmp-socket that was created by xtask --profile run and gives
  a summary or stack.folded (with -o parameter)
• Right now we made xtask run as --release by default because tracing require a bit of performance.
• Fixed unwinding in rust

Checklist

• The changes are tested and works as expected (mention if not)
• Tests if applicable (new features, regression tests, etc...)
• Documentation
• Needed README changes