Proceedings of the 50th Annual IEEE/ACM International Symposium on Microarchitecture 2017
DOI: 10.1145/3123939.3123950
|View full text |Cite
|
Sign up to set email alerts
|

Efficient exception handling support for GPUs

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
4
2

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(2 citation statements)
references
References 40 publications
0
2
0
Order By: Relevance
“…Today, machine checks [54] (e.g., ECC errors in the cache/memory hierarchy) are the only example of imprecise exception in modern CPUs because they are non-restartable and cause the OS to terminate the process or even crash. Finally, emerging accelerators such as GPUs [55] adopt imprecise exceptions because precise exceptions pose a dramatic performance overhead or require significantly more silicon area and power. As computing systems evolve, the cost of supporting precise exceptions and their programming implications are being gradually revisited with new constraints.…”
Section: Precise Exceptionsmentioning
confidence: 99%
“…Today, machine checks [54] (e.g., ECC errors in the cache/memory hierarchy) are the only example of imprecise exception in modern CPUs because they are non-restartable and cause the OS to terminate the process or even crash. Finally, emerging accelerators such as GPUs [55] adopt imprecise exceptions because precise exceptions pose a dramatic performance overhead or require significantly more silicon area and power. As computing systems evolve, the cost of supporting precise exceptions and their programming implications are being gradually revisited with new constraints.…”
Section: Precise Exceptionsmentioning
confidence: 99%
“…To handle page fault, Power et al [11] gave one hardware solution, which modified CPU interrupt return microcode and added one extra CPU register to handle GPU page fault. But extra hardware support is not necessary, Tanasic et al [14] gave 3 possible design of GPU page handler (Wrap Disabling, Replay Queue or Operand log), which could remove CPU involvement in GPU page fault.…”
Section: Rit Note That This Communication Is Batched Each Communicamentioning
confidence: 99%