Erik Rose

Perhaps negating the above realization: stack frames don't point to each other. ["One consequence of of [sic] the lack of return addresses and frame pointer chains is that there is...

And killing off that idea again: Big Go's compilation results don't contain a `$__stack_pointer` (though it could go by a different name or be otherwise extractable).

Ulyssa clarified that she means the shift-mem changes should be ported over to Viceroy as well (from ExecuteD).

When we do that, we must be sure to commit a built adapter (viceroy-component-adapter.wasm) as well.

Thanks so much! That clears it right up. Redundancy that serves a purpose is no redundancy at all. :-) > One thing you'll need to handle I think though is...

Would someone assign this to me, please? Thanks!

Here is my [work in progress](https://github.com/bytecodealliance/wasmtime/compare/main...erikrose:wasmtime:epoch-mmu). I am approaching it incrementally, first using the simpler "interrupt page" (per `Store`, i.e. per thread) method and then, once that works end to...

Thanks, Alex. I'll take some time to meditate over this. > Where possible I'd recommend doing anything nontrivial in signal handlers altogether. Can I assume you meant "recommend against" there?

@alexcrichton @cfallin Thank you for your detailed writeups! The way this is slowly agglomerating in my head is something like… * Keep the sigaltstack. * My dead loads at the...

@posborne and I talked off to the side, but, to confirm in-thread: all you need is `epoch_interruption_via_mmu`. Atm, it and the existing `epoch_interruption` are orthogonal, but that's not the final...