linux-kernel - Re: [PATCH v7 5/5] KVM: selftests: Allowing running dirty_log_perf

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 for Android: free password hash cracker in your pocket

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

Message-ID: <Y2AmrZO0UtpU8EDu@google.com>
Date:   Mon, 31 Oct 2022 19:49:01 +0000
From:   Sean Christopherson <seanjc@...gle.com>
To:     Vipin Sharma <vipinsh@...gle.com>
Cc:     pbonzini@...hat.com, dmatlack@...gle.com, andrew.jones@...ux.dev,
        wei.w.wang@...el.com, kvm@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v7 5/5] KVM: selftests: Allowing running
 dirty_log_perf_test on specific CPUs

On Mon, Oct 31, 2022, Vipin Sharma wrote:
> Add a command line option, -c, to pin vCPUs to physical CPUs (pCPUs),
> i.e.  to force vCPUs to run on specific pCPUs.
> 
> Requirement to implement this feature came in discussion on the patch
> "Make page tables for eager page splitting NUMA aware"
> https://lore.kernel.org/lkml/YuhPT2drgqL+osLl@google.com/
> 
> This feature is useful as it provides a way to analyze performance based
> on the vCPUs and dirty log worker locations, like on the different NUMA
> nodes or on the same NUMA nodes.
> 
> To keep things simple, implementation is intentionally very limited,
> either all of the vCPUs will be pinned followed by an optional main
> thread or nothing will be pinned.
> 
> Signed-off-by: Vipin Sharma <vipinsh@...gle.com>
> Suggested-by: David Matlack <dmatlack@...gle.com>
> ---

Reviewed-by: Sean Christopherson <seanjc@...gle.com>