Re: [PATCH] KVM: Aggressively drop and reacquire mmu_lock during CLEAR_DIRTY_LOG

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2024-04-02 17:42, David Matlack wrote:
On Thu, Jan 11, 2024 at 8:55 AM David Matlack <dmatlack@xxxxxxxxxx> wrote:

On Tue, Dec 5, 2023 at 10:16 AM David Matlack <dmatlack@xxxxxxxxxx> wrote:
>
> Aggressively drop and reacquire mmu_lock during CLEAR_DIRTY_LOG to avoid
> blocking other threads (e.g. vCPUs taking page faults) for too long.

Ping.

KVM architecture maintainers: Do you have any concerns about the
correctness of this patch? I'm confident dropping the lock is correct
on x86 and it should be on other architectures as well, but
confirmation would be helpful.

Thanks.

Ping again. This patch has been sitting since December 5th. Is there
anything I can do to help get it merged?

Please send a rebased version as a V2. With the number of MMU patches
flying around without much coordination, it is hard to keep track.

Thanks,

        M.
--
Jazz is not dead. It just smells funny...




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux