linux-kernel - Re: [PATCH v2 3/3] KVM: selftests: Add a test to invoke MMU shrinker on KVM VMs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHVum0f-3OMnLj5DNnmBZM-f-fP6ApeO8UzaVk0MDyVMnnifYg@mail.gmail.com>
Date: Fri, 4 Oct 2024 13:03:00 -0700
From: Vipin Sharma <vipinsh@...gle.com>
To: seanjc@...gle.com, pbonzini@...hat.com, dmatlack@...gle.com
Cc: zhi.wang.linux@...il.com, weijiang.yang@...el.com, mizhang@...gle.com, 
	liangchen.linux@...il.com, kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 3/3] KVM: selftests: Add a test to invoke MMU shrinker
 on KVM VMs

On Fri, Oct 4, 2024 at 12:55 PM Vipin Sharma <vipinsh@...gle.com> wrote:

> diff --git a/tools/testing/selftests/kvm/x86_64/mmu_shrinker_test.c b/tools/testing/selftests/kvm/x86_64/mmu_shrinker_test.c
> new file mode 100644
> index 0000000000000..81dd745bcebdb
> --- /dev/null
> +++ b/tools/testing/selftests/kvm/x86_64/mmu_shrinker_test.c
> @@ -0,0 +1,269 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * MMU shrinker test
> + *
> + * Test MMU shrinker invocation on VMs. This test needs kernel built with
> + * shrinker debugfs and mounted. Generally that location is
> + * /sys/debug/kernel/shrinker.
> + *
> + * Test will keep adding and removing memslots while guest is accessing memory
> + * so that vCPUs will keep taking fault and filling up caches to process the
> + * page faults. It will also invoke shrinker after memslot changes which will
> + * race with vCPUs to empty caches.
> + *
> + * Copyright 2010 Google LLC

Oops! This should have been 2024. I clearly live in the past.
Should I send v3 or can it be updated when this is merged?