Supporting hang detection and data recovery in microprocessor systems
US-2019243701-A1 · Aug 8, 2019 · US
US12013746B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12013746-B2 |
| Application number | US-202017032737-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 25, 2020 |
| Priority date | Sep 25, 2020 |
| Publication date | Jun 18, 2024 |
| Grant date | Jun 18, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Techniques and mechanisms for logging crash event information based on a high-level representation of a structure that a crash log is to have. In an embodiment, a crash log agent logs information which describes system state to a record of a crash log. A structure of the record is defined by instructions which include a high-level reference to a type of information that is to be retrieved for logging to the record. Based on the high-level reference, the crash log agent accesses reference information which indicates a correspondence of the information type to a circuit resource with which state information is to be retrieved. A transaction unit of the crash log agent generates a command to target the circuit resource in response to an indication of a crash log event. In another embodiment, the transaction unit identifies the circuit resource prior to the crash log event.
Opening claim text (preview).
What is claimed is: 1. An integrated circuit (IC) comprising: a crash log agent comprising: a collection engine comprising circuitry to: receive instructions which define a record structure, the instructions comprising a generic identifier of an information type to indicate a first correspondence of the information type to a field of the record structure; and access reference information, based on the generic identifier, to determine a second correspondence of the information type to a functional block; and a transaction unit coupled to the collection engine, wherein, based on the second correspondence, the collection engine is to communicate that the transaction unit is to retrieve state information of the information type, wherein the transaction unit comprises circuitry to send a command, in response to an indication of a crash event, to access a register of the functional block; wherein one of the collection engine or the transaction unit is to determine, based on the first correspondence and the generic identifier, that the register is a repository of the state information. 2. The IC of claim 1 , wherein: the functional block is a first functional block, wherein the IC further comprises multiple functional blocks including the first functional block; the transaction unit is a first transaction unit; and the crash log agent comprises multiple transaction units, including the first transaction unit, each coupled to communicate with a different respective one or more of the multiple functional blocks. 3. The IC of claim 2 , wherein the reference information identifies the first transaction unit as being coupled to support communication with the first functional block; and wherein, based on the generic identifier and the reference information, the collection engine is to select the first transaction unit from among the multiple transaction units to retrieve state information of the information type. 4. The IC of claim 2 , wherein the reference information identifies a correspondence of multiple transaction units each with a different respective one or more functional block types. 5. The IC of claim 2 , wherein, for each transaction unit of the multiple transaction units: the collection engine is to indicate to the transaction unit a respective one or more registers of the multiple functional blocks that the transaction unit is to access; and the transaction unit is to detect the indication of the crash event after the collection engine indicates the respective one or more registers to the transaction unit. 6. The IC of claim 1 , wherein: the functional block is a first functional block; the IC further comprises one or more functional blocks including the first functional block; the collection engine is to indicate to the transaction unit multiple registers of the one or more functional blocks that the transaction unit is to access; and the transaction unit is to detect the indication of the crash event after the collection engine indicates the multiple registers to the transaction unit. 7. The IC of claim 1 , wherein the reference information is first reference information, wherein a first transaction unit comprises second reference information which identifies a correspondence of functional block types each with a respective one or more register types. 8. The IC of claim 7 , wherein, for multiple register types, the second reference information further identifies a respective indicator to target a register which is of the register type. 9. A method comprising: at a collection engine of a crash log agent: receiving instructions which defines a record structure, wherein the instructions comprise a generic identifier of an information type to indicate a first correspondence of the information type to a field of the record structure, wherein the collection engine is coupled to a functional block comprising a register; based on the generic identifier, accessing reference information to determine a second correspondence of the information type to the functional block; and based on the second correspondence, communicating that a transaction unit of the crash log agent is to retrieve state information of the information type; and with the transaction unit, sending a command, in response to an indication of a crash event, to access the register, wherein one of the collection engine or the transaction unit determines, based on the first correspondence and the generic identifier, that the register is a repository of the state information. 10. The method of claim 9 , wherein: the functional block is a first functional block, wherein an integrated circuit (IC) comprises multiple functional blocks including the first functional block; the transaction unit is a first transaction unit; and the crash log agent comprises multiple transaction units, including the first transaction unit, each coupled to communicate with a different respective one or more of the multiple functional blocks. 11. The method of claim 10 , wherein the reference information identifies the first transaction unit as being coupled to support communication with the first functional block, the method further comprising: with the collection engine, selecting the first transaction unit from among the multiple transaction units, based on the generic identifier and the reference information, to retrieve state information of the information type. 12. The method of claim 10 , wherein the reference information identifies a correspondence of multiple transaction units each with a different respective one or more functional block types. 13. The method of claim 9 , wherein: the functional block is a first functional block; an integrated circuit (IC) comprises one or more functional blocks including the first functional block; the collection engine indicates to the transaction unit multiple registers of the one or more functional blocks that the transaction unit is to access; and the transaction unit detects the indication of the crash event after the collection engine indicates the multiple registers to the transaction unit. 14. The method of claim 9 , wherein the reference information is first reference information, wherein a first transaction unit comprises second reference information which identifies a correspondence of functional block types each with a respective one or more register types. 15. A system comprising: an integrated circuit (IC) comprising: a crash log agent comprising: a collection engine comprising circuitry to: receive instructions which define a record structure, the instructions comprising a generic identifier of an information type to indicate a first correspondence of the information type to a field of the record structure; and access reference information, based on the generic identifier, to determine a second correspondence of the information type to a functional block; and a transaction unit coupled to the collection engine, wherein, based on the second correspondence, the collection engine is to communicate that the transaction unit is to retrieve state information of the information type, wherein the transaction unit comprises circuitry to send a command, in response to an indication of a crash event, to access a register of the functional block; wherein one of the collection engine or the transaction unit is to determine, based on the first correspondence and the generic identifier, that the register is a repository of the state information; and a display device coupled to the IC, the display device to display an image based on a signal communicated with the functional block.
Alarm or error message display · CPC title
Monitoring arrangements determined by the means or processing involved in reporting the monitored data (error or fault reporting or logging G06F11/0766) · CPC title
Storage of error reports, e.g. persistent data storage, storage using memory protection · CPC title
in an input/output transactions management context (input/output processing in general G06F13/00) · CPC title
in a multiprocessor or a multi-core unit (multiprocessors per se G06F15/80) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.