entryexit.html
895 Bytes
<html>
<head>
<title>SK Entry/Exit Testing</title>
</head>
<body>
<center>
<h1>SK Entry/Exit Testing</h1>
</center>
<h2>Overview</h2>
The entry/exit testing is intended to verify that memory and cache
are managed properly, and also that context (registers, stack) are
properly setup and restored.
<p>
The cache and memory handling should cover scrubbing of iram on exit,
and defensive measures to prevent against attack as described
<a href=../cache_security.html>here</a>).
<h2>Testing</h2>
Currently, most aspects of entry/exit are being scrubbed during a
search for timer entry/exit problems. As a result, only the iram
scrub test is described here. This test (bbapps/sktest/gatekeep)
insures that iram is scrubbed up to the region at top used for
restoring context. The srub is verified for both the sysapp first
coming up and apps making calls into the sk.
</body>
</html>