Exception Trace Data Filtering Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data processing systems face challenges in efficiently tracing exception handling events due to the generation of large amounts of trace data, which can lead to buffer overflow and loss of information, especially when exception tracing is enabled, making it difficult to analyze processing activity effectively.
Innovation Solution
The implementation of a trace module that varies the amount of exception trace information output based on configuration data, allowing for filtering, merging of trace packets, and the use of a tailchain flag, as well as compression modes to reduce the size of exception trace packets, thereby improving the tracing of exception handling events and alleviating buffer overflow issues.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If exception tracing is enabled to monitor processing activity, then diagnostic capability is improved, but trace data volume increases causing buffer overflow
Solution Approach 1:
The patent extracts and outputs only selected exception handling events rather than all trace data. The trace filter selectively passes exception entry, exit, and return events while filtering out other trace data, thereby reducing the volume of trace data sent to the trace analyzer while maintaining diagnostic capability for exception handling.
Solution Approach 2:
The patent applies partial action by selectively tracing only exception handling events rather than all processing activity. The trace filter enables partial monitoring of processing activity focused specifically on exception events, which provides sufficient diagnostic information while minimizing trace data volume.
2Loss of information
If all exception trace information is output for complete analysis, then information completeness is improved, but bandwidth consumption increases
Solution Approach 1:
The trace filter extracts only the essential exception handling events (entry, exit, return) from the complete trace data stream. This selective extraction maintains the completeness of exception handling information while significantly reducing the bandwidth required to transmit trace data to the analyzer.
Solution Approach 2:
The patent segments trace data into different categories and selectively processes only exception handling events. The trace filter divides the trace data stream and separates exception events from other processing activity, transmitting only the segmented exception data to reduce bandwidth consumption while preserving complete exception handling information.
3Reliability
If trace filtering is applied to reduce data volume, then buffer overflow is prevented, but trace analysis capability may be reduced
Solution Approach 1:
The trace filter acts as an intermediary between the trace data source and the trace analyzer. It selectively passes exception handling events while blocking other trace data, thereby preventing buffer overflow while maintaining the trace analyzer's ability to fully analyze exception handling behavior. The intermediary preserves all necessary exception information for complete analysis.
Data Source
Figure 1~2
Figure 3A~3C
Figure 4~5
AI summary
An apparatus 2 comprises trace circuitry 6, 120 to output exception trace data indicating exception handling events detected during monitoring of processing activity of processing circuitry 4. A configuration element 16 maintains exception trace configuration data for controlling the output of the exception trace data via the trace circuitry 6, 120. When output of exception trace data is enabled, the trace circuitry 6, 120 selects, in dependence on the exception trace configuration data, how much of the exception trace data to output.