Forgive me if this is infeasible since I don’t know the architecture well enough, but what about using the MMU’s privileged position to watch for a specific peek or poke or both pattern and only then expose addresses? Assuming that is doable, you could even have alternate patterns that would expose the MMU at different addresses so that it was run time selectable. Justin > On Sep 22, 2019, at 13:37, Mia Magnusson <mia_at_plea.se> wrote: > --=_z6Zxlh2RPxkD5oT+39kDSOjqW2d4ndSZ2jKCeO78zWkQmZqw Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8"> <META NAME="Generator" CONTENT="Zarafa HTML builder 1.0"> <TITLE></TITLE> </HEAD> <BODY> <!-- Converted from text/plain format --> <P><FONT STYLE="font-family: courier" SIZE=2> Forgive me if this is infeasible since I don’t know the architecture well enough, but what about using the MMU’s privileged position to watch for a specific peek or poke or both pattern and only then expose addresses? Assuming that is doable, you could even have alternate patterns that would expose the MMU at different addresses so that it was run time selectable.<br> <br> Justin<br> <br> > On Sep 22, 2019, at 13:37, Mia Magnusson <mia_at_plea.se> wrote:<br> > <br> </FONT> </P> </BODY></HTML> --=_z6Zxlh2RPxkD5oT+39kDSOjqW2d4ndSZ2jKCeO78zWkQmZqw--Received on 2020-05-29 22:40:50
Archive generated by hypermail 2.3.0.