mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2025-01-08 12:19:37 +03:00
b32e961a84
The kernel now supports basic profiling of all the threads in a process
by calling profiling_enable(pid_t). You finish the profiling by calling
profiling_disable(pid_t).
This all works by recording thread stacks when the timer interrupt
fires and the current thread is in a process being profiled.
Note that symbolication is deferred until profiling_disable() to avoid
adding more noise than necessary to the profile.
A simple "/bin/profile" command is included here that can be used to
start/stop profiling like so:
$ profile 10 on
... wait ...
$ profile 10 off
After a profile has been recorded, it can be fetched in /proc/profile
There are various limits (or "bugs") on this mechanism at the moment:
- Only one process can be profiled at a time.
- We allocate 8MB for the samples, if you use more space, things will
not work, and probably break a bit.
- Things will probably fall apart if the profiled process dies during
profiling, or while extracing /proc/profile
31 lines
641 B
C++
31 lines
641 B
C++
#include <Kernel/Syscall.h>
|
|
#include <errno.h>
|
|
#include <serenity.h>
|
|
|
|
extern "C" {
|
|
|
|
int module_load(const char* path, size_t path_length)
|
|
{
|
|
int rc = syscall(SC_module_load, path, path_length);
|
|
__RETURN_WITH_ERRNO(rc, rc, -1);
|
|
}
|
|
|
|
int module_unload(const char* name, size_t name_length)
|
|
{
|
|
int rc = syscall(SC_module_unload, name, name_length);
|
|
__RETURN_WITH_ERRNO(rc, rc, -1);
|
|
}
|
|
|
|
int profiling_enable(pid_t pid)
|
|
{
|
|
int rc = syscall(SC_profiling_enable, pid);
|
|
__RETURN_WITH_ERRNO(rc, rc, -1);
|
|
}
|
|
|
|
int profiling_disable(pid_t pid)
|
|
{
|
|
int rc = syscall(SC_profiling_disable, pid);
|
|
__RETURN_WITH_ERRNO(rc, rc, -1);
|
|
}
|
|
}
|