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] [day] [month] [year] [list]
Message-ID: <175873638301.2146431.11936191215737388089.b4-ty@google.com>
Date: Wed, 24 Sep 2025 11:07:34 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Sean Christopherson <seanjc@...gle.com>, Paolo Bonzini <pbonzini@...hat.com>, 
	Shuah Khan <shuah@...nel.org>, kvm@...r.kernel.org, linux-kselftest@...r.kernel.org, 
	linux-kernel@...r.kernel.org, Sukrut Heroorkar <hsukrut3@...il.com>
Cc: skhan@...uxfoundation.org, david.hunter.linux@...il.com
Subject: Re: [PATCH] selftests/kvm: remove stale TODO in xapic_state_test

On Mon, 08 Sep 2025 23:05:46 +0200, Sukrut Heroorkar wrote:
> The TODO about using the number of vCPUs instead of vcpu.id + 1
> was already addressed by commit 376bc1b458c9 ("KVM: selftests: Don't
> assume vcpu->id is '0' in xAPIC state test"). The comment is now
> stale and can be removed.

Applied to kvm-x86 selftests, thanks!

[1/1] selftests/kvm: remove stale TODO in xapic_state_test
      https://github.com/kvm-x86/linux/commit/ff86b48d4ce3

--
https://github.com/kvm-x86/linux/tree/next

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ