Re: [PATCH] hw/virtio: Add ioeventfd option for balloon

On 04.01.24 08:15, 沈哲赟 wrote: Traditional mmio in balloon makes Qemu do balloon inflation in the same thread as vcpu thread. In a CPU overcommitment scenario, host may run more than one vcpu threads on one host CPU, which makes madvise_dontneed_free() wait for a long time due to the function cond

[PATCH] hw/virtio: Add ioeventfd option for balloon

Traditional mmio in balloon makes Qemu do balloon inflation in the same thread as vcpu thread. In a CPU overcommitment scenario, host may run more than one vcpu threads on one host CPU, which makes madvise_dontneed_free() wait for a long time due to the function cond_resched() at host side. If usi

Re: [PATCH] hw/virtio: Add ioeventfd option for balloon

Please CC the relevant maintainers, I only stumbled over that by luck. See scripts/get_maintainer.pl On 12.12.23 08:50, Zheyun Shen wrote: Traditional mmio in balloon makes qemu do balloon inflation in the same thread as vcpu thread.In a CPU overcommitment scenario, host may run more than one

[PATCH] hw/virtio: Add ioeventfd option for balloon

Traditional mmio in balloon makes qemu do balloon inflation in the same thread as vcpu thread.In a CPU overcommitment scenario, host may run more than one vcpu threads on one host thread, which makes madvise_dontneed_free() wait for a long time due to the function cond_resched() at host side. If u