Apparatuses and methods for generating event codes including event source

• US 9,400,734 B2
• Filed: 05/13/2014
• Issued: 07/26/2016
• Est. Priority Date: 09/15/2013
• Status: Active Grant

• Current Assignee: SanDisk Technologies LLC (Western Digital Corporation)
• Original Assignee: SanDisk Technologies LLC (Western Digital Corporation)
• Inventors: Aharonov, Arseniy, Brief, David, Gueta, Asaf
• Primary Examiner(s): Lee, Adam
• Application Number:
  US14/276,744
• Publication Number:
  US 20150082313A1
• Time in Patent Office: 805 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 11/36 Preventing errors by testing or debugging software
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system

Abstract

Apparatuses and methods implemented therein are disclosed for generating event codes that include the source of the events that caused the generation of the event codes. In one embodiment the apparatus comprises a memory, a processor, logic element and an event generator. The memory is configured to store instructions corresponding to a scheduler and instructions corresponding to a first thread and a second thread. The processor is configured to execute instructions corresponding to the scheduler wherein the scheduler selects a one of the first or second thread wherein the processor executes instructions corresponding to the selected one of the first or second thread. The logic element is configured to receive an identifier corresponding to the selected thread and a received asynchronous event. The logic element produces a concatenated event identifier comprising the thread identifier and the received asynchronous event.

Claims

1. An apparatus comprising:

a memory configured to store a program for a scheduler and a program for each of a first thread and a second thread pending execution in the apparatus;

a processor configured to execute the program for the scheduler wherein the scheduler selects a one of the first or second thread and wherein the processor executes the program for the selected one of the first or second thread;

a logic element configured to receive an asynchronous event and a thread identifier uniquely identifying the selected thread, and to produce a concatenated event identifier comprising the received thread identifier and the received asynchronous event, wherein the received asynchronous event is received in response to an execution of an instruction caused by the selected thread, wherein the received asynchronous event indicates the execution of the instruction, and wherein either the first thread or second thread is capable of causing execution of the instruction; and

a timestamp configuration register comprising a first group of one or more bits for configuring a periodicity of a series of periodic events and a second group of one or more bits for configuring a precision of a timestamp fraction of the asynchronous event relative to one of the periodic events.

2. The apparatus of claim 1 further comprising:

a register configured to receive the concatenated event identifier;

a counter configured to receive a clock signal and generate the series of periodic events of the configured periodicity;

a timestamp fraction generator coupled to the register and configured to generate the timestamp fraction in response to the concatenated event identifier being received by the register, wherein generating the timestamp fraction comprises obtaining a count from the counter following the time the event is received; and

an event code generator configured to receive the timestamp fraction and the concatenated event identifier and generate an event code comprising at least the timestamp fraction and an identifier derived from the concatenated event identifier.

3. The apparatus of claim 2, wherein the count is a function of a change in the value of the counter since the last generated periodic event.

4. The apparatus of claim 3, wherein the count represents a time elapsed since the last generated periodic event.

5. The apparatus of claim 4, wherein the asynchronous event is of a unique type within one of a set of types of asynchronous events.

6. The apparatus of claim 5, wherein the set of types of asynchronous events occur at a common maximum rate.

7. The apparatus of claim 6, wherein the periodicity of the periodic events is configured by the timestamp configuration register to be a function of the maximum rate.

8. A method implemented in a device to generate an event code, the method comprising:

receiving a thread identifier uniquely identifying either a selected one of a first or a second thread, wherein a scheduler selects the one of the first or second thread and wherein a processor executes the selected one of the first or second thread;

generating a concatenated event identifier comprising the thread identifier and a received asynchronous event, wherein the asynchronous event is received in response to an execution of an instruction caused by the selected thread, wherein the asynchronous event indicates the execution of the instruction and wherein either the first thread or second thread is capable of causing execution of the instruction; and

setting a first group of one or more bits of a time stamp configuration register for configuring a first periodicity at which a first set of periodic events are generated, wherein the timestamp configuration register further comprising a second group of one or more bits for configuring the precision of a timestamp fraction of the asynchronous event relative to one of the first set of periodic events.

9. A method of claim 8 further comprising:

configuring a first source to generate the first set of periodic events at a first rate according the first periodicity;

receiving periodic events from the first source;

in response to receiving the concatenated event identifier, determining the timestamp fraction, wherein the timestamp fraction represents a time lapse between a previously received periodic event from the first source and when the asynchronous event was concatenated with the event identifier; and

generating the event code, the event code comprising the timestamp fraction relative to another event and an identifier derived from the concatenated event identifier.

10. The method of claim 9, wherein the asynchronous event is one of a first set of asynchronous events and the first set of asynchronous events occur at a first maximum rate.

11. The method of claim 10, wherein the first rate for generating the periodic events by the first source is determined by the first maximum rate.

12. The method of claim 9, further comprising generating a periodic event code in response to receiving a periodic event from the first source.

13. The method of claim 12, wherein generating the periodic event code further comprises including in the generated periodic event code information indicating the status of the device.

14. The method of claim 11, further comprising configuring a second source to generate periodic events at a second rate wherein the second rate is determined by a second maximum rate at which a second set of asynchronous events occur.

15. The method of claim 14, further comprising in response to receiving a second asynchronous event from the second set of asynchronous events, determining a timestamp fraction, wherein the timestamp fraction represents a time lapse between a previously received periodic event from the second source and when the second asynchronous event was generated.

16. The method of 14 wherein the second maximum rate is different from the first maximum rate.