System And Method For Scan-Testing Of Idle Functional Units In Operating Systems
US-2015212151-A1 · Jul 30, 2015 · US
US9513985B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-9513985-B1 |
| Application number | US-201615013731-A |
| Country | US |
| Kind code | B1 |
| Filing date | Feb 2, 2016 |
| Priority date | Jun 29, 2015 |
| Publication date | Dec 6, 2016 |
| Grant date | Dec 6, 2016 |
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.
An approach for improving efficiency of cycle-reproducible debug in a multi-core environment is provided. The approach executes an exerciser image on one or more cores, wherein the exerciser image includes one or more different seeds. The approach determines a seed from the one or more different seeds that locates a fail-condition. Responsive to determining a seed from the one or more different seeds that locates the fail condition, the approach determines an upper bound and a lower bound of the fail-condition. The approach determines an exact cycle where the fail-condition occurs. The approach constructs a multi-cycle trace for the fail-condition.
Opening claim text (preview).
What is claimed is: 1. A method for improving efficiency of cycle-reproducible debug in a multi-core environment, the method comprising: executing, by one or more computer processors, an exerciser image on one or more cores, wherein the exerciser image includes one or more different seeds, wherein executing includes presetting each of the one or more cores with the one or more different seeds, wherein the one or more different seeds are at least one of: a pseudo random value or a binary value, and evaluating the one or more different seeds for each of the one or more cores concurrently; determining, by one or more computer processors, a seed from the one or more different seeds that locates a fail-condition; responsive to determining a seed from the one or more different seeds that locates the fail condition, determining, by one or more computer processors, an upper bound and a lower bound of the fail-condition, wherein determining includes executing the exerciser image with the seed on each of the one or more cores for a range of cycles, wherein each of the one or more cores is set to stop at a different cycle within the range of cycles, searching from an initial cycle at the beginning of a test execution run where the fail-condition does not exist to a subsequent cycle of a test execution run where the fail-condition exists, and determining whether the fail-condition has occurred within the range of cycles executed on each of the one or more cores; responsive to a determination that the fail-condition has occurred within the range of cycles executed by at least one of the one or more cores, determining, by one or more computer processors, a lowest cycle count in the at least one of the one or more cores where the fail-condition as an upper bound; responsive to a determination that the fail-condition has not occurred within the range of cycles executed by at least one of the one or more cores, resetting, by one or more computer processors, each of the one or more cores with a higher stopping cycle; determining, by one or more computer processors, an exact cycle where the fail-condition occurs, wherein determining includes performing a plurality of distributed searches for the fail-condition across each of the one or more cores, wherein performing the plurality of distributed searches includes distributing a number of cycles between the upper bound and the lower bound across each of the one or more cores; constructing, by one or more computer processors, a multi-cycle trace for the fail-condition, wherein constructing includes performing one test execution per-cycle, including the exact cycle where the fail condition occurred, and extracting data from one or more cycles preceding the exact cycle where the fail-condition occurred, data from the exact cycle where the fail-condition occurred, and data from one or more cycles subsequent to the exact cycle where the fail-condition occurred; and aggregating, by one or more computer processors, test data collected from a plurality of test executions.
to test CPU or processors · CPC title
in a multiprocessor or a multi-core unit (multiprocessors per se G06F15/80) · CPC title
Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36) · CPC title
in multi-processor systems, e.g. one processor becoming the primary tester (G06F11/2736 takes precedence) · CPC title
Debugging of software · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.