rtems - RTEMS Kernel, file-systems, drivers, BSPs, samples, and testsuite.

	Commit message (Collapse)	Author	Age	Files	Lines
*	record: Add data size to client	Sebastian Huber	2019-08-27	1	-0/+1
\| \| \| \| \| \| \|	This is necessary to get the thread names properly on 32-bit and 64-bit targets. Update #3665.
*	record: Improve overflow handling	Sebastian Huber	2019-08-26	1	-0/+5
\| \| \| \| \|	Signal the accumulated item overflow count with the time of the first new item.
*	record: Add rtems_record_client_set_handler()	Sebastian Huber	2019-08-17	1	-0/+8
\|
*	record: Pass bintime to client handlers	Sebastian Huber	2019-08-17	1	-2/+28
\| \| \| \|	This is a minor optimization.
*	record: Increase client robustness	Sebastian Huber	2019-08-17	1	-0/+1
\| \| \| \|	Do nothing after errors.
*	record: Improve overflow handling	Sebastian Huber	2019-08-17	1	-1/+68
\| \| \| \| \| \| \| \|	In case of a ring buffer overflow, the rtems_record_drain() will push the complete ring buffer content to the client. While the items are processed by the client, new items may overwrite some items being processed. The overwritten items can be detected in the following iteration once the next tail/head information is pushed to the client.
*	record: Detect also large overflows	Sebastian Huber	2019-08-16	1	-1/+1
\|
*	record: Simplify rtems_record_client_context	Sebastian Huber	2019-08-16	1	-2/+0
\|
*	Add low level event recording support	Sebastian Huber	2019-01-29	1	-0/+139
	Add low level event recording infrastructure for system and user defined events. The infrastructure is able to record high frequency events such as * SMP lock acquire/release, * interrupt entry/exit, * thread switches, * UMA zone allocate/free, and * Ethernet packet input/output, etc. It allows post-mortem analysis in fatal error handlers, e.g. the last events are in the record buffer, the newest event overwrites the oldest event. It is possible to detect record buffer overflows for consumers that expect a continuous stream of events, e.g. to display the system state in real-time. The implementation supports high-end SMP machines (more than 1GHz processor frequency, more than four processors). Add a new API instead. The implementation uses per-processor data structures and no atomic read-modify-write operations. It is uses per-processor ring buffers to record the events. The CPU counter is used to get the time of events. It is combined with periodic uptime events to synchronize it with CLOCK_REALTIME. The existing capture engine tries to solve this problem also, but its performance is not good enough for high-end production systems. The main issues are the variable-size buffers and the use of SMP locks for synchronization. To fix this, the API would change significantly. Update #3665.