Re: [PATCH qemu 0/7] Many improvements to HVF memory-related codes

2022-03-01 Thread Yan-Jie Wang
Sorry, I made a mistake. The last line in the function, hvf_find_free_slot, introduced in this commit "hvf: simplify data structures and codes of memory related functions" should be "return NULL;" static hvf_slot *hvf_find_free_slot(void) { hvf_slot *slot; int x; for (x = 0; x < HVF_NU

Re: [PATCH qemu 0/7] Many improvements to HVF memory-related codes

2022-03-01 Thread Yan-Jie Wang
For the dirty-tracking part in my patch series, the major difference between this patch and Alex's patch is that the dirty-tracking logic in my patch will only mark the page being written dirty instead of marking the whole memory slot dirty, and will only restore the write permission to the pag

[PATCH qemu 0/7] Many improvements to HVF memory-related codes

2022-02-28 Thread ~ubzeme
I recently bought a Mac with M1 Pro chip, and use QEMU to setup a Linux virtual machine. QEMU crashed when I started a VM with HVF accelerator enabled and with the device, bochs-display, added. After digging into the source code, I found that dirty-tracking in HVF did not work properly, which mad

Re: [PATCH qemu 0/7] Many improvements to HVF memory-related codes

2022-02-28 Thread Peter Maydell
On Mon, 28 Feb 2022 at 14:07, ~ubzeme wrote: > > I recently bought a Mac with M1 Pro chip, and use QEMU to setup a Linux > virtual machine. QEMU crashed when I started a VM with HVF accelerator > enabled and with the device, bochs-display, added. > > After digging into the source code, I found th