PROJECT TITLE :

Subtleties of Run-Time Virtual Address Stacks

ABSTRACT:

The run-time virtual address (VA) stack has some distinctive properties, which have garnered the attention of researchers. The stack one-dimensionally grows and shrinks at its top, and contains data that's seemingly local/personal to 1 thread, or method. Most previous connected research has targeted on these properties. But, this article aims to demonstrate how typical wisdom per the run-time VA stack fails to capture some critical subtleties and complexities. We first explore two widely established assumptions surrounding the VA stack space: (1) Knowledge accesses will be classified as falling either underneath VA-stack-space accesses, or non-stack-space accesses, with no aliasing; (a pair of) The VA stack data is completely private and invisible to other threads/processes. Subsequently, we have a tendency to summarize a representative choice of connected work that pursued the micro-architectural concept of using run-time VA stacks to extend the final-purpose register file. We then demonstrate why these assumptions are invalid, by using examples from prior work to spotlight the potential hazards concerning information consistency, shared memory consistency, and cache coherence. Finally, we recommend safeguards against these hazards. Overall, we tend to explore the operate-essential issues that future operating systems and compilers ought to address to effectively reap all the advantages of using run-time VA stacks.