linux-kernel - Re: [PATCH v2] KVM: SVM: Fix an off-by-one typo in the comment for enabling AVIC by default

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: <176849887444.718912.15225828841384052421.b4-ty@google.com>
Date: Thu, 15 Jan 2026 10:03:36 -0800
From: Sean Christopherson <seanjc@...gle.com>
To: Sean Christopherson <seanjc@...gle.com>, Paolo Bonzini <pbonzini@...hat.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Naveen N Rao <naveen@...nel.org>
Subject: Re: [PATCH v2] KVM: SVM: Fix an off-by-one typo in the comment for
 enabling AVIC by default

On Thu, 08 Jan 2026 19:50:37 -0800, Sean Christopherson wrote:
> Fix a goof in the comment that documents KVM's logic for enabling AVIC by
> default to reference Zen5+ as family 0x1A (Zen5), not family 0x19 (Zen4).
> The code is correct (checks for _greater_ than 0x19), only the comment is
> flawed.
> 
> Opportunistically tweak the check too, even though it's already correct,
> so that both the comment and the code reference 0x1A, and so that the
> checks are "ascending", i.e. check Zen4 and then Zen5+.
> 
> [...]

Applied to kvm-x86 svm, thanks!

[1/1] KVM: SVM: Fix an off-by-one typo in the comment for enabling AVIC by default
      https://github.com/kvm-x86/linux/commit/69555130dccb

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