2016
DOI: 10.1109/tc.2015.2481411
|View full text |Cite
|
Sign up to set email alerts
|

A Power-Aware Approach for Online Test Scheduling in Many-Core Architectures

Abstract: Aggressive technology scaling triggers novel challenges to the design of multi-/many-core systems, such as limited power budget and increased reliability issues. Today's many-core systems employ dynamic power management and runtime mapping strategies trying to offer optimal performance while fulfilling power constraints. On the other hand, due to the reliability challenges, online testing techniques are becoming a necessity in current and near future technologies. However, state-of-the-art techniques are not a… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
12
0

Year Published

2016
2016
2019
2019

Publication Types

Select...
3
3
2

Relationship

2
6

Authors

Journals

citations
Cited by 13 publications
(12 citation statements)
references
References 40 publications
0
12
0
Order By: Relevance
“…Skitsas et al (2018)) or selectively based on a priority rule (e.g. Skitsas et al (2016); Haghbayan et al (2016b)).…”
Section: Fault Diagnosismentioning
confidence: 99%
See 1 more Smart Citation
“…Skitsas et al (2018)) or selectively based on a priority rule (e.g. Skitsas et al (2016); Haghbayan et al (2016b)).…”
Section: Fault Diagnosismentioning
confidence: 99%
“…To overcome this limitation, in the second class of approaches cores are selectively tested thus exploiting an ad-hoc scheduling policy to limit the impact on the system performance. Haghbayan et al (2016b) proposed an SBST routine scheduling algorithm for many-core architectures aimed at testing cores on the basis of the suffered stress, in terms of an aging metric, during the execution of the nominal workload. The scheduling policy is aimed at avoiding any degradation in system performance while not violating the power budget of the many-core system.…”
Section: Fault Diagnosismentioning
confidence: 99%
“…both transient and permanent faults, while other strategies (e.g. [88], [89]) schedule at runtime software-based self testing routines to identify permanent damages.…”
Section: Reliabilitymentioning
confidence: 99%
“…This method implies that the entire system will be offline during the duration of the test process, thereby interrupting the execution of other applications. Another approach is to initiate testing on individual cores that have been observed to be idle for some time [25] [26] [27]. Thus, the testing process in minimally intrusive, but the time required to complete the testing of all cores is substantially longer (since each core is individually tested at different points in time).…”
Section: Introductionmentioning
confidence: 99%