haiku/headers/private/kernel/system_profiler.h

/*
 * Copyright 2009, Ingo Weinhold, ingo_weinhold@gmx.de.
 * Distributed under the terms of the MIT License.
 */
#ifndef _KERNEL_SYSTEM_PROFILER_H
#define _KERNEL_SYSTEM_PROFILER_H

#include <sys/cdefs.h>

#include <OS.h>

#include "kernel_debug_config.h"


struct system_profiler_parameters;


__BEGIN_DECLS

#if SYSTEM_PROFILER
status_t start_system_profiler(size_t areaSize, uint32 stackDepth,
			bigtime_t interval);
void stop_system_profiler();
#endif

status_t _user_system_profiler_start(
			struct system_profiler_parameters* parameters);
status_t _user_system_profiler_next_buffer(size_t bytesRead,
			uint64* _droppedEvents);
status_t _user_system_profiler_stop();
status_t _user_system_profiler_recorded(
			struct system_profiler_parameters* parameters);

__END_DECLS


#endif	/* _KERNEL_SYSTEM_PROFILER_H */
The kernel side of a new system-wide sampling-based profiling mechanism. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@30127 a95241bf-73f2-0310-859d-f6bbb57e9c96 2009-04-12 02:20:51 +04:00			`/*`
			`* Copyright 2009, Ingo Weinhold, ingo_weinhold@gmx.de.`
			`* Distributed under the terms of the MIT License.`
			`*/`
			`#ifndef _KERNEL_SYSTEM_PROFILER_H`
			`#define _KERNEL_SYSTEM_PROFILER_H`

			`#include <sys/cdefs.h>`

			`#include <OS.h>`

kernel: profile system when SYSTEM_PROFILER is defined. * This enables a mechanism to profile almost the complete boot process (starting with main2()), if SYSTEM_PROFILER is defined to 1. * You can access the profiling data using "profile -r". 2015-04-15 18:06:51 +03:00			`#include "kernel_debug_config.h"`

The kernel side of a new system-wide sampling-based profiling mechanism. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@30127 a95241bf-73f2-0310-859d-f6bbb57e9c96 2009-04-12 02:20:51 +04:00
* Changed the interface of _kern_system_profiler_start(). The parameters are passed in a structure now, so it is easier to extend it and ignore unused parameters. * One can now select which system profiling events one is interested in. * Added scheduling events to the system profiling interface. Those are pretty much the ones recorded when scheduler tracing is enabled. Still missing are the "wait object" events that allow to interpret what a thread is waiting for. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@30243 a95241bf-73f2-0310-859d-f6bbb57e9c96 2009-04-18 21:35:28 +04:00			`struct system_profiler_parameters;`


The kernel side of a new system-wide sampling-based profiling mechanism. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@30127 a95241bf-73f2-0310-859d-f6bbb57e9c96 2009-04-12 02:20:51 +04:00			`__BEGIN_DECLS`

kernel: profile system when SYSTEM_PROFILER is defined. * This enables a mechanism to profile almost the complete boot process (starting with main2()), if SYSTEM_PROFILER is defined to 1. * You can access the profiling data using "profile -r". 2015-04-15 18:06:51 +03:00			`#if SYSTEM_PROFILER`
* It seems we always have to specify all flags to make it work; removed "flags" parameter from start_system_profiler(). * Added stack depth, and interval parameters to it, though. * Profiling the boot process is now possible. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@31671 a95241bf-73f2-0310-859d-f6bbb57e9c96 2009-07-21 16:09:15 +04:00			`status_t start_system_profiler(size_t areaSize, uint32 stackDepth,`
			`bigtime_t interval);`
* Work-in-progress on a kernel profile service that can be evaluated from userland afterwards. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@31621 a95241bf-73f2-0310-859d-f6bbb57e9c96 2009-07-17 20:21:06 +04:00			`void stop_system_profiler();`
kernel: profile system when SYSTEM_PROFILER is defined. * This enables a mechanism to profile almost the complete boot process (starting with main2()), if SYSTEM_PROFILER is defined to 1. * You can access the profiling data using "profile -r". 2015-04-15 18:06:51 +03:00			`#endif`
* Work-in-progress on a kernel profile service that can be evaluated from userland afterwards. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@31621 a95241bf-73f2-0310-859d-f6bbb57e9c96 2009-07-17 20:21:06 +04:00
* Changed the interface of _kern_system_profiler_start(). The parameters are passed in a structure now, so it is easier to extend it and ignore unused parameters. * One can now select which system profiling events one is interested in. * Added scheduling events to the system profiling interface. Those are pretty much the ones recorded when scheduler tracing is enabled. Still missing are the "wait object" events that allow to interpret what a thread is waiting for. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@30243 a95241bf-73f2-0310-859d-f6bbb57e9c96 2009-04-18 21:35:28 +04:00			`status_t _user_system_profiler_start(`
			`struct system_profiler_parameters* parameters);`
* Scheduler/wait object listener: - Moved scheduler listening interface to <listeners.h> and added more convenient to use templatized notification functions. - Added a listener mechanism for the wait objects (semaphores, condition variables, mutex, rw_lock). * system profiler: - Hopefully fixed locking issues related to notifying the profiler thread for good. We still had an inconsistent locking order, since the scheduler notification callbacks are invoked with the thread lock held and have to acquire the object lock then, while the other callbacks acquired the object lock first and as a side effect of ConditionVariable::NotifyOne() acquired the thread lock. Now we make sure the object lock is the innermost lock. - Track the number of dropped events due to a full buffer. _user_system_profiler_next_buffer() returns this count now. - When scheduling profiling events are requested also listen to wait objects and generate the respective profiling events. We send those events lazily and cache the infos to avoid resending an event for the same wait object. - When starting profiling we do now generate "thread scheduled" events for the already running threads. - _user_system_profiler_start(): Check whether the parameters pointer is a userland address at all. - The system_profiler_team_added event does now also contain the team's name. * Added a sem_get_name_unsafe() returning a semaphore's name. It is "unsafe", since the caller has to ensure that the semaphore exists and continues to exist as long as the returned name is used. * Adjusted the "profile" and "scheduling_recorder" according to the system profiling changes. The latter prints the number of dropped events, now. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@30345 a95241bf-73f2-0310-859d-f6bbb57e9c96 2009-04-23 17:47:52 +04:00			`status_t _user_system_profiler_next_buffer(size_t bytesRead,`
			`uint64* _droppedEvents);`
The kernel side of a new system-wide sampling-based profiling mechanism. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@30127 a95241bf-73f2-0310-859d-f6bbb57e9c96 2009-04-12 02:20:51 +04:00			`status_t _user_system_profiler_stop();`
* Work-in-progress on a kernel profile service that can be evaluated from userland afterwards. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@31621 a95241bf-73f2-0310-859d-f6bbb57e9c96 2009-07-17 20:21:06 +04:00			`status_t _user_system_profiler_recorded(`
			`struct system_profiler_parameters* parameters);`
The kernel side of a new system-wide sampling-based profiling mechanism. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@30127 a95241bf-73f2-0310-859d-f6bbb57e9c96 2009-04-12 02:20:51 +04:00
			`__END_DECLS`


			`#endif /* _KERNEL_SYSTEM_PROFILER_H */`