linux-kernel - Re: [PATCH v3] kvm/x86: allocate the write-tracking metadata on-demand

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] [day] [month] [year] [list]

Date: Thu, 7 Mar 2024 14:07:59 +0800
From: Yan Zhao <yan.y.zhao@...el.com>
To: Sean Christopherson <seanjc@...gle.com>
CC: Paolo Bonzini <pbonzini@...hat.com>, Andrei Vagin <avagin@...gle.com>,
	<linux-kernel@...r.kernel.org>, <x86@...nel.org>, <kvm@...r.kernel.org>,
	Zhenyu Wang <zhenyuw@...ux.intel.com>, Zhi Wang <zhi.a.wang@...el.com>,
	Yongwei Ma <yongwei.ma@...el.com>
Subject: Re: [PATCH v3] kvm/x86: allocate the write-tracking metadata
 on-demand

On Tue, Feb 27, 2024 at 01:28:18PM -0800, Sean Christopherson wrote:
> Added a few more KVM-GT folks.  FYI, this changes KVM to allocate metadata for
> write-tracking on-demand, i.e. when KVM-GT first registers with KVM.  I tested
> by hacking in usage of the external APIs, to register/unregister a node on every
> vCPU before/after vcpu_run(), so I am fairly confident that it's functionally
> correct.  But just in case you see issues in linux-next... :-)
I tested in my environment with KVMGT and found no issues :)