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]
Message-Id: <173184539747.890800.11538594220662178668.b4-ty@ellerman.id.au>
Date: Sun, 17 Nov 2024 23:09:57 +1100
From: Michael Ellerman <patch-notifications@...erman.id.au>
To: mpe@...erman.id.au, npiggin@...il.com, christophe.leroy@...roup.eu, naveen@...nel.org, maddy@...ux.ibm.com, vaibhav@...ux.ibm.com, Gautam Menghani <gautam@...ux.ibm.com>
Cc: linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] arch/powerpc/pseries: Fix KVM guest detection for disabling hardlockup detector

On Fri, 08 Nov 2024 15:18:37 +0530, Gautam Menghani wrote:
> As per the kernel documentation[1], hardlockup detector should be
> disabled in KVM guests as it may give false positives. On PPC, hardlockup
> detector is enabled inside KVM guests because disable_hardlockup_detector()
> is marked as early_initcall and it relies on kvm_guest static key
> (is_kvm_guest()) which is initialized later during boot by
> check_kvm_guest(), which is a core_initcall. check_kvm_guest() is also
> called in pSeries_smp_probe(), which is called before initcalls, but it is
> skipped if KVM guest does not have doorbell support or if the guest is
> launched with SMT=1.
> 
> [...]

Applied to powerpc/next.

[1/1] arch/powerpc/pseries: Fix KVM guest detection for disabling hardlockup detector
      https://git.kernel.org/powerpc/c/44e5d21e6d3fd2a1fed7f0327cf72e99397e2eaf

cheers

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ