LekKit

I hope they won't be mad if we look at their implementation and reuse it somewhat :) @X547 Could you please look at this whenever you have free time? It...

Nah it's fine here

Please have a look at NVMe device example: https://github.com/LekKit/RVVM/blob/419e1796692a3d6cd838f8933224f354f7a4169b/src/devices/nvme.c#L586 It should be fairly straightforward to use, PCI only defines a device identification mechanism (Device/Vendor IDs, device class). The actual device...

I also want to ask you to stop opening more issues because it is very confusing to navigate them, and some questions you asked lately are not easily understandable.

PCI Device class codes explanation: https://admin.pci-ids.ucw.cz/read/PD/ PCI Vendor/Device ID listing: https://admin.pci-ids.ucw.cz/read/PC/ Dump PCI device address / class code / vendor & device ID / revision: ```sh lspci -n ``` ...

Load/store memory instructions specifics should be ignored from device perspective. RVVM MMIO API can be seen in `src/rvvmlib.h`, and is well documented.

Please see the RVVM API and only then try to adapt anything. Devices should not touch CPU specifics directly, like load/store instruction opcodes, registers. Devices should not trap the CPU...

The RISC-V Vector extension i think is not easily translatable to SIMD/NEON because it is a lot more advanced. AVX512 on the other hand is somewhat useful, but not many...

Are you trying to realign next auto zone to page boundary?

Does the commit 43846ef work as desired?