Trace Hub Logic for Automatic Event Triggering

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computing devices require manual analysis of trace data, which is inefficient and can overwhelm memory bandwidth, limiting real-time event tracing and diagnostics.

Innovation Solution

Implementing trace hub logic with automatic event triggering, where event trigger rules match trace packets to invoke callbacks, enabling real-time reaction and automated debugging without user intervention, allowing for finer-grained execution tracing without overwhelming processing capacity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual analysis of trace data is performed, then analysis can be done with simple tools, but it is inefficient and overwhelms memory bandwidth

Engineering Contradiction:
Improvetrace analysis efficiencyVSAvoidmemory bandwidth consumption
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The trace hub performs preliminary filtering and matching of trace packets against event trigger rules before transmitting data to remote hosts. This preliminary action reduces the volume of data that needs to be analyzed manually, improving efficiency while reducing memory bandwidth consumption by only transmitting relevant matched packets.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The trace hub acts as an intermediary between trace data generation and manual analysis. It automatically matches packets against rules and filters results, serving as a mediator that reduces the burden on both memory bandwidth and human analysts by pre-processing and selecting only relevant data.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If fine-grained execution tracing is implemented, then detailed diagnostics are achieved, but processing capacity is overwhelmed

Engineering Contradiction:
Improvetracing granularityVSAvoidprocessing capacity demand
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

Event trigger rules are pre-configured to define specific patterns and conditions for matching trace packets. This preliminary setup allows the system to automatically filter and process only relevant packets at fine-grained levels without overwhelming processing capacity, as the matching logic is prepared in advance rather than requiring real-time complex analysis of all packets.

Inventive Principle:
Principle #10Preliminary action

3Extent of automation

If automatic event triggering is implemented, then real-time reaction is achieved, but system complexity increases

Engineering Contradiction:
Improveevent triggering automationVSAvoidtrace hub logic complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The automatic event triggering functionality is segmented into distinct modular components: packet matching logic that compares packets against rules, event generator logic that creates events from matches, and callback execution mechanisms. This segmentation allows real-time automation while managing complexity through modular, independent components that can be configured and maintained separately.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10534688B2Trace hub logic with automatic event triggering
Publication Date: 2020.01.14 INTEL CORP
  • US10534688B2 patent drawing
  • US10534688B2 patent drawing
  • US10534688B2 patent drawing

AI summary

Technologies for execution trace with automatic event triggering include a computing device that includes an execution trace hub. The trace hub observes execution trace packets and determines whether the execution trace packets match one or more event trigger rules. If an execution packet matches an event trigger rule, the trace hub invokes an event callback. The event callback may be a predefined hardware function of the computing device or a software function. The trace hub may be configured with event trigger rules and associated event callbacks, for example by writing to one or more corresponding configuration space registers. In response to invoking the event callback, the computing device may, for example, output state information of the computing device to a data storage device, halt execution, activate a debug mode of the processor, or execute a software recovery function. Other embodiments are described and claimed.