2019
DOI: 10.48550/arxiv.1912.09770
|View full text |Cite
Preprint
|
Sign up to set email alerts
|

CacheQuery: Learning Replacement Policies from Hardware Caches

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1

Citation Types

0
4
0

Year Published

2020
2020
2020
2020

Publication Types

Select...
2

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(4 citation statements)
references
References 0 publications
0
4
0
Order By: Relevance
“…The replacement policy described in [10] agrees with the ones described in [3,62] in the selection of the eviction candidate most of the times. Indeed, our attack can be explained considering any of them as the correct one.…”
Section: Replacement Policy and Accurate Eviction Of Datamentioning
confidence: 58%
See 2 more Smart Citations
“…The replacement policy described in [10] agrees with the ones described in [3,62] in the selection of the eviction candidate most of the times. Indeed, our attack can be explained considering any of them as the correct one.…”
Section: Replacement Policy and Accurate Eviction Of Datamentioning
confidence: 58%
“…It turns out that Intel implements a tree based Pseudo-LRU replacement policy in the low level caches. Independently and concurrently with the design of this attack, some other researchers arrived to the same conclusion [3,62].…”
Section: Influence Of the Replacement Policy Of The L1 Cachesmentioning
confidence: 70%
See 1 more Smart Citation
“…To identify the replacement policy on our machine, we used a CacheAnalyzer tool by nanoBench [3]. The resulting replacement policy is approximately QLRU_H11_M1_R0_U0 ("Quad-age LRU") on specific cache sets [51]. 4 QLRU is a Static-RRIP Replacement policy variant with a 2 bit field used for the age of a cache line [3,24], summed up here: lines until there is a candidate ready for eviction (age = 3).…”
Section: Receiver (Monitoring Replacement State)mentioning
confidence: 99%