Jarkko Sakkinen
Jarkko Sakkinen
So is this about implementing EACCEPT, EACCEPTCOPY and EMODPE, which acknowledge EAUG, EMODPR and EMODT? I don't understand this issue.
And internal bookkeeping for what exact purpose?
I think this covered by https://github.com/enarx/enarx/issues/1381.
https://github.com/rust-osdev/x86_64/pull/348
`brk()` requires tracking so I guess this could be called `feat(sgx): brk()`? It requires to track address ranges of RW VMA's. @haraldh What do you think?
Where are the validation functions?
I'm doing now a partition table for shim-sgx. With it I'll create the following policy: * `mmap()` can be only done to empty address space. * `mprotect()` can be only...
I'm working on a ledger for mm: https://github.com/jarkkojs/mmledger/blob/main/src/mmledger/mod.rs. I think this quite elegant and does not lead to a circular dependency where ledger structures themselves need a working mm.
> @jarkkojs You can try tackling this once you finish updating PolkaVM in `polkadot-sdk`. +1
`DW_AT_name [DW_FORM_strp] : (indirect string, .debug_str+0x0): cap` @koute, verified with `rz-bin -d`: https://book.rizin.re/src/tools/rz-bin/intro.html This is by far the most reliable tool to dump DWARF (highly recommended).