ZLangJIT

> hmm alright > > so according to https://lwn.net/Articles/808807/ > > it would be safe to assume that this would transform -m xyzM such that it specifies the amount of...

im thinking something like this ill work on it some more next week linux sysv shm API note - https://dev.to/0xog_pg/using-shared-memory-in-linux-1p62 note termux provides a shm wrapper for ashmem ```c #if...

> Is it intended for SysV SHM IPC or for plain memory mapped files? i would like both if possible

ok i have managed to map the files but i cannot seem to find them in rvvm guest ``` INFO: Attached MMIO device at 0x40004000, type "nvme" INFO: mapping path...

```c rvvm_info("mapped path '%s' at address %p with size %zu", path, shm_ctx->buffer, shm_ctx->size); rvvm_mmio_dev_t shm_region = { .mapping = shm_ctx->buffer, .size = shm_ctx->size, .data = shm_ctx, .type = &shm_data_dev_type, };...

hmm it appears to stall if we attempt to expose any file that is larger than 1040944 bytes or expose a 1040944 byte file twice (`-shm_data f.i -shm_id foo -shm_data...

additionally we consume extra memory based on how many files we expose and the total size of all exposed files

hmm INFO: Generated DTB at 0xb1e02890, size 2086764 a bootable one (where it doesnt stall) is INFO: Generated DTB at 0xb1f00b50, size 1045676

hmm https://patchwork.kernel.org/project/qemu-devel/patch/[email protected]/ seems to mention the device tree has a fixed max size of ~1MB to 2MB

> I think it would be better to invest into a `virtio-gpu` device implementation and reuse existing `virglrenderer` on host and Mesa `virgl` driver in guest. would that work on...