# US 2003/0217189 A1 · Event data acquisition

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2003/0217189 A1
- Document ID: US20030217189A1
- Status: Published application
- Kind: A1
- Application number: 10/147,113
- Filed: 2002-05-15
- Published: 2003-11-20
- Earliest claimed: 2002-05-15
- Assignees: Microsoft Corporation
- Inventors: David Kelley; Larry Morris
- Web page: https://patentgrep.com/patent/US20030217189A1

## CPC

- G06F 11/3476: {Data logging (G06F11/14, G06F11/2205 take precedence)}
- G06F 11/2236: {to test CPU or processors}
- G06F 2201/86: Event-based monitoring
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

An event data acquisition device has a data segment multiplexer to receive data segments corresponding to processor events generated with a test device, and a memory component to maintain the data segments in an order that they are received from the test device. A control component of the event data acquisition device pauses the test device processor when the memory component exceeds a threshold number of stored data segments. An event data packet component generates event data packets where an individual data packet includes data segments having information for a particular processor event.

## Claims

### Claim 1

A method to log processor events with an event data acquisition device, comprising:
receiving data segments from a test device, the data segments corresponding to the processor events;
writing the data segments to a first-in, first-out memory component in an order that they are received from the test device; and
pausing processing in the test device when the first-in, first-out memory component exceeds a threshold number of stored data segments.

### Claim 2 (depends on 1)

A method as recited in claim 1, further comprising resuming processing of the test device when the first-in, first-out memory component maintains less than the threshold number of stored data segments.

### Claim 3 (depends on 1)

A method as recited in claim 1, further comprising resuming processing of the test device when the first-in, first-out memory component maintains less than a minimum number of stored data segments.

### Claim 4 (depends on 1)

A method as recited in claim 1, further comprising time-stamping the data segments when they are received from the test device.

### Claim 5 (depends on 1)

A method as recited in claim 1, further comprising:
labeling a first data segment having header information with a memory address identifier corresponding to a first memory address of the test device; and
labeling a second data segment having event information with a memory address identifier corresponding to a second memory address of the test device.

### Claim 6 (depends on 1)

A method as recited in claim 1, further comprising:
labeling a first data segment having header information with an event data source identifier corresponding to a source of the first data segment, and with a memory address identifier corresponding to a first memory address of the test device; and
labeling a second data segment having event information with the event data source identifier corresponding to the source of the second data segment, and with a memory address identifier corresponding to a second memory address of the test device.

### Claim 7 (depends on 1)

A method as recited in claim 1, further comprising:
time-stamping the data segments when they are received from the test device;
labeling a first data segment having header information with a memory address identifier corresponding to a first memory address of the test device; and
labeling a second data segment having event information with a memory address identifier corresponding to a second memory address of the test device.

### Claim 8 (depends on 1)

A method as recited in claim 1, further comprising:
time-stamping the data segments when they are received from the test device;
labeling a first data segment having header information with an event data source identifier corresponding to a source of the first data segment, and with a memory address identifier corresponding to a first memory address of the test device; and
labeling a second data segment having event information with the event data source identifier corresponding to the source of the second data segment, and with a memory address identifier corresponding to a second memory address of the test device.

### Claim 9 (depends on 1)

A method as recited in claim 1, further comprising generating processor event data packets, an individual processor event data packet including at least one data segment having information for a particular processor event.

### Claim 10 (depends on 1)

A method as recited in claim 1, further comprising:
time-stamping the data segments when they are received from the test device;
identifying the data segments having header information;
identifying the data segments having event information; and
generating a processor event data packet including at least one data segment having header information for a particular processor event and at least one data segment having event information for the particular processor event.

### Claim 11 (depends on 1)

A method as recited in claim 1, further comprising:
generating processor event data packets, an individual processor event data packet including at least one data segment having information for a particular processor event; and
determining processor event data packet errors.

### Claim 12 (depends on 1)

A method as recited in claim 1, further comprising:
generating processor event data packets, an individual processor event data packet including at least one data segment having information for a particular processor event;
determining processor event data packet errors; and
communicating the processor event data packets to a host computing device.

### Claim 13 (depends on 1)

A method as recited in claim 1, wherein receiving the data segments includes receiving the data segments via an interconnect bus.

### Claim 14 (depends on 1)

One or more computer-readable media comprising computer-executable instructions that, when executed, perform the method of claim 1.

### Claim 15

A method, comprising:
receiving data segments from a test device, the data segments corresponding to events generated in a test device;
writing the data segments to a first-in, first-out memory component in an order that they are received from the test device; and
generating event data packets, an individual event data packet including at least one data segment having information for a particular event.

### Claim 16 (depends on 15)

A method as recited in claim 15, further comprising generating an event data packet including at least one data segment having header information for a particular event and at least one data segment having event information for the particular event.

### Claim 17 (depends on 15)

A method as recited in claim 15, further comprising time-stamping the data segments when they are received from the test device.

### Claim 18 (depends on 15)

A method as recited in claim 15, further comprising:
labeling a first data segment having header information with a memory address identifier corresponding to a first memory address of the test device; and
labeling a second data segment having event information with a memory address identifier corresponding to a second memory address of the test device.

### Claim 19 (depends on 15)

A method as recited in claim 15, further comprising:
labeling a first data segment having header information with an event data source identifier corresponding to a source of the first data segment, and with a memory address identifier corresponding to a first memory address of the test device; and
labeling a second data segment having event information with the event data source identifier corresponding to the source of the second data segment, and with a memory address identifier corresponding to a second memory address of the test device.

### Claim 20 (depends on 15)

A method as recited in claim 15, further comprising:
time-stamping the data segments when they are received from the test device;
labeling a first data segment having header information with a memory address identifier corresponding to a first memory address of the test device; and
labeling a second data segment having event information with a memory address identifier corresponding to a second memory address of the test device.

### Claim 21 (depends on 15)

A method as recited in claim 15, further comprising:
time-stamping the data segments when they are received from the test device;
labeling a first data segment having header information with an event data source identifier corresponding to a source of the first data segment, and with a memory address identifier corresponding to a first memory address of the test device; and
labeling a second data segment having event information with the event data source identifier corresponding to the source of the second data segment, and with a memory address identifier corresponding to a second memory address of the test device.

### Claim 22 (depends on 15)

A method as recited in claim 15, further comprising pausing processing in the test device when the first-in, first-out memory component exceeds a threshold number of stored data segments.

### Claim 23 (depends on 15)

A method as recited in claim 15, further comprising
pausing processing in the test device when the first-in, first-out memory component exceeds a threshold number of stored data segments; and
resuming processing of the test device when the first-in, first-out memory component maintains less than the threshold number of stored data segments.

### Claim 24 (depends on 15)

A method as recited in claim 15, further comprising communicating the event data packets to a host computing device.

### Claim 25 (depends on 15)

A method as recited in claim 15, wherein receiving the data segments includes receiving the data segments via an interconnect bus.

### Claim 26 (depends on 15)

One or more computer-readable media comprising computer-executable instructions that, when executed, direct an event data acquisition device to perform the method of claim 15.

### Claim 27

An event data acquisition device, comprising:
a data segment multiplexer configured to receive data segments from a test device, the data segments corresponding to test device events;
a memory component configured to receive the data segments from the data segment multiplexer and maintain the data segments in an order that they are received from the test device; and
a control component configured to pause processing in the test device when the memory component exceeds a threshold number of stored data segments.

### Claim 28 (depends on 27)

An event data acquisition device as recited in claim 27, wherein the control component is further configured to resume processing of the test device when the memory component maintains less than the threshold number of stored data segments.

### Claim 29 (depends on 27)

An event data acquisition device as recited in claim 27, wherein the control component is further configured to resume processing of the test device when the memory component maintains less than a minimum number of stored data segments.

### Claim 30 (depends on 27)

An event data acquisition device as recited in claim 27, further comprising an event data packet component configured to generate event data packets, an individual event data packet including at least one data segment having header information for a particular test device event and at least one data segment having event information for the particular test device event.

### Claim 31 (depends on 27)

An event data acquisition device as recited in claim 27, further comprising an event data packet component configured to generate event data packets, an individual event data packet including at least one data segment having information for a particular test device event.

### Claim 32 (depends on 27)

An event data acquisition device as recited in claim 27, further comprising an event data packet component configured to generate event data packets, an individual event data packet including at least one data segment having information for a particular test device event, and the event data packet component further configured to communicate the event data packets to a host computing device.

### Claim 33 (depends on 27)

An event data acquisition device as recited in claim 27, further comprising an event data packet component configured to:
generate event data packets, an individual event data packet including at least one data segment having header information for a particular test device event and at least one data segment having event information for the particular test device event;
determine event data errors in the event data packets; and
communicate the event data packets to a host computing device.

### Claim 34 (depends on 27)

An event data acquisition device as recited in claim 27, wherein the data segment multiplexer receives the data segments from a processor in the test device via an interconnect bus.

### Claim 35 (depends on 27)

An event data acquisition device as recited in claim 27, wherein the data segment multiplexer is further configured to timestamp the data segments when they are received from the test device.

### Claim 36 (depends on 27)

An event data acquisition device as recited in claim 27, wherein the data segment multiplexer is further configured to:
receive a first data segment having header information from the test device, the first data segment written to a first memory address in the test device;
receive a second data segment having event information from the test device, the second data segment written to a second memory address in the test device;
label the first data segment with a memory address identifier corresponding to the first memory address; and
label the second data segment with a memory address identifier corresponding to the second memory address.

### Claim 37 (depends on 27)

An event data acquisition device as recited in claim 27, wherein the data segment multiplexer is further configured to:
receive a first data segment having header information from the test device, the first data segment written to a first memory address in the test device;
receive a second data segment having event information from the test device, the second data segment written to a second memory address in the test device;
label the first data segment with a memory address identifier corresponding to the first memory address, and with a data segment source identifier that corresponds to a source of the first data segment; and
label the second data segment with a memory address identifier corresponding to the second memory address, and with the data segment source identifier that corresponds to the source of the second data segment.

### Claim 38 (depends on 27)

An event data acquisition device as recited in claim 27, wherein the data segment multiplexer is further configured to:
receive a first data segment having header information from the test device, the first data segment written to a first memory address in the test device;
receive a second data segment having event information from the test device, the second data segment written to a second memory address in the test device;
timestamp the first and second data segments when they are received from the test device;
label the first data segment with a memory address identifier corresponding to the first memory address; and
label the second data segment with a memory address identifier corresponding to the second memory address.

### Claim 39

An event data acquisition device, comprising:
a data segment multiplexer configured to receive data segments from a test device, the data segments corresponding to test device events;
a first-in, first-out memory component configured to receive the data segments from the data segment multiplexer and maintain the data segments in an order that they are received from the test device; and
an event data packet component configured to generate event data packets, an individual event data packet including data segments having information corresponding to a particular test device event.

### Claim 40 (depends on 39)

An event data acquisition device as recited in claim 39, further comprising a control component configured to pause processing in the test device when the first-in, first-out memory component exceeds a threshold number of stored data segments.

### Claim 41 (depends on 39)

An event data acquisition device as recited in claim 39, further comprising a control component configured to pause processing in the test device when the first-in, first-out memory component exceeds a threshold number of stored data segments, and resume processing of the test device when the first-in, first-out memory component maintains less than the threshold number of stored data segments.

### Claim 42 (depends on 39)

An event data acquisition device as recited in claim 39, wherein the event data packet component is further configured to communicate the event data packets to a host computing device.

### Claim 43 (depends on 39)

An event data acquisition device as recited in claim 39, wherein the event data packet component is further configured to determine event data errors in the event data packets.

### Claim 44 (depends on 39)

An event data acquisition device as recited in claim 39, wherein the data segment multiplexer receives the data segments from a processor of the test device via an interconnect bus.

### Claim 45 (depends on 39)

An event data acquisition device as recited in claim 39, wherein the data segment multiplexer is further configured to timestamp the data segments when they are received from the test device.

### Claim 46 (depends on 39)

An event data acquisition device as recited in claim 39, wherein the data segment multiplexer is further configured to:
receive a first data segment having header information from the test device, the first data segment written to a first memory address in the test device;
receive a second data segment having event information from the test device, the second data segment written to a second memory address in the test device;
timestamp the first and second data segments when they are received from the test device;
label the first data segment with a memory address identifier corresponding to the first memory address; and
label the second data segment with a memory address identifier corresponding to the second memory address.

### Claim 47

A system, comprising:
a test device configured to generate processor events;
an event data acquisition device configured to:
receive data segments from the test device, the data segments corresponding to the processor events;
maintain the data segments in a first-in, first-out memory component, the data segments maintained in an order that they are received from the test device;
generate processor event data packets, an individual processor event data packet including at least one data segment having header information for a particular processor event and at least one data segment having event information for the particular processor event; and
communicate the processor event data packets to a host computing device.

### Claim 48 (depends on 47)

A system as recited in claim 47, wherein the event data acquisition device is further configured to pause processing in the test device when the first-in, first-out memory component exceeds a threshold number of stored data segments.

### Claim 49 (depends on 47)

A system as recited in claim 47, wherein the event data acquisition device is further configured to pause processing in the test device when the first-in, first-out memory component exceeds a threshold number of stored data segments, and resume processing of the test device when the first-in, first-out memory component maintains less than the threshold number of stored data segments.

### Claim 50 (depends on 47)

A system as recited in claim 47, wherein the event data acquisition device is further configured to timestamp the data segments when they are received from the test device.

### Claim 51 (depends on 47)

A system as recited in claim 47, wherein the event data acquisition device is further configured to:
receive a first data segment having header information from the test device, the first data segment written to a first memory address in the test device;
receive a second data segment having event information from the test device, the second data segment written to a second memory address in the test device;
timestamp the first and second data segments when they are received from the test device;
label the first data segment with a memory address identifier corresponding to the first memory address; and
label the second data segment with a memory address identifier corresponding to the second memory address.

### Claim 52 (depends on 47)

A system as recited in claim 47, wherein the test device and the event data acquisition device are coupled via an interconnect bus.

### Claim 53 (depends on 47)

A system as recited in claim 47, wherein the event data acquisition device is a peripheral card that is coupled to the test device via an interconnect bus.

### Claim 54

One or more computer-readable media comprising computer executable instructions that, when executed, direct an event data acquisition device to perform a method comprising:
time-stamping data segments received from a test device, the data segments corresponding to processor events;
labeling first data segments having header information with a memory address identifier of a first memory address that the first data segments are written to in the test device;
labeling second data segments having event information with a memory address identifier of a second memory address that the second data segments are written to in the test device;
writing the data segments to a first-in, first-out memory component in an order that they are received from the test device;
generating processor event data packets, an individual processor event data packet including at least one data segment having header information for a particular processor event and at least one data segment having event information for the particular processor event.

### Claim 55 (depends on 54)

One or more computer-readable media as recited in claim 54, wherein the method further comprises pausing processing in the test device when the first-in, first-out memory component exceeds a threshold number of stored data segments.

### Claim 56 (depends on 54)

One or more computer-readable media as recited in claim 54, wherein the method further comprises:
pausing processing in the test device when the first-in, first-out memory component exceeds a threshold number of stored data segments; and
resuming processing of the test device when the first-in, first-out memory component maintains less than the threshold number of stored data segments.
