[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC PATCH 2/2] kvm/kvm-all.c: listener should delay kvm_vm_ioctl to
|
From: |
David Hildenbrand |
|
Subject: |
Re: [RFC PATCH 2/2] kvm/kvm-all.c: listener should delay kvm_vm_ioctl to the commit phase |
|
Date: |
Fri, 26 Aug 2022 16:15:29 +0200 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0 |
On 16.08.22 12:12, Emanuele Giuseppe Esposito wrote:
> Instead of sending a single ioctl every time ->region_* or ->log_*
> callbacks are called, "queue" all memory regions in a list that will
> be emptied only when committing.
>
Out of interest, how many such regions does the ioctl support? As many
as KVM theoretically supports? (32k IIRC)
--
Thanks,
David / dhildenb
- Re: [RFC PATCH 1/2] softmmu/memory: add missing begin/commit callback calls, (continued)
[RFC PATCH 2/2] kvm/kvm-all.c: listener should delay kvm_vm_ioctl to the commit phase, Emanuele Giuseppe Esposito, 2022/08/16
Re: [RFC PATCH 2/2] kvm/kvm-all.c: listener should delay kvm_vm_ioctl to the commit phase, Cornelia Huck, 2022/08/22
Re: [RFC PATCH 2/2] kvm/kvm-all.c: listener should delay kvm_vm_ioctl to the commit phase,
David Hildenbrand <=