mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Ravi Bangoria <ravi.bangoria@amd.com>,
	Xiaoyao Li <xiaoyao.li@intel.com>,
	rangemachine@gmail.com,  whanos@sergal.fun
Subject: Re: [PATCH v3 0/6] KVM: SVM: Fix DEBUGCTL bugs
Date: Fri,  2 May 2025 14:51:01 -0700	[thread overview]
Message-ID: <174622246244.883023.7921101160630129073.b4-ty@google.com> (raw)
In-Reply-To: <20250227222411.3490595-1-seanjc@google.com>

On Thu, 27 Feb 2025 14:24:05 -0800, Sean Christopherson wrote:
> Fix a long-lurking bug in SVM where KVM runs the guest with the host's
> DEBUGCTL if LBR virtualization is disabled.  AMD CPUs rather stupidly
> context switch DEBUGCTL if and only if LBR virtualization is enabled (not
> just supported, but fully enabled).
> 
> The bug has gone unnoticed because until recently, the only bits that
> KVM would leave set were things like BTF, which are guest visible but
> won't cause functional problems unless guest software is being especially
> particular about #DBs.
> 
> [...]

Applied patch 6 to kvm-x86 svm (1-5 already went into 6.15).

[6/6] KVM: SVM: Treat DEBUGCTL[5:2] as reserved
      https://github.com/kvm-x86/linux/commit/5ecdb48dd918

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

      parent reply	other threads:[~2025-05-02 21:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 22:24 Sean Christopherson
2025-02-27 22:24 ` [PATCH v3 1/6] KVM: SVM: Drop DEBUGCTL[5:2] from guest's effective value Sean Christopherson
2025-02-27 22:24 ` [PATCH v3 2/6] KVM: SVM: Suppress DEBUGCTL.BTF on AMD Sean Christopherson
2025-02-27 22:24 ` [PATCH v3 3/6] KVM: x86: Snapshot the host's DEBUGCTL in common x86 Sean Christopherson
2025-02-27 22:24 ` [PATCH v3 4/6] KVM: SVM: Manually context switch DEBUGCTL if LBR virtualization is disabled Sean Christopherson
2025-02-27 22:24 ` [PATCH v3 5/6] KVM: x86: Snapshot the host's DEBUGCTL after disabling IRQs Sean Christopherson
2025-02-27 22:24 ` [PATCH v3 6/6] KVM: SVM: Treat DEBUGCTL[5:2] as reserved Sean Christopherson
2025-02-28  9:31 ` [PATCH v3 0/6] KVM: SVM: Fix DEBUGCTL bugs Ravi Bangoria
2025-02-28 14:04   ` Sean Christopherson
2025-02-28 23:40 ` Sean Christopherson
2025-04-02  3:57 ` Maxim Levitsky
2025-04-08 15:08   ` Maxim Levitsky
2025-04-08 22:43   ` Sean Christopherson
2025-04-09 20:52     ` Maxim Levitsky
2025-04-14  6:32     ` Sandipan Das
2025-04-14 14:43       ` Maxim Levitsky
2025-05-02 21:51 ` Sean Christopherson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=174622246244.883023.7921101160630129073.b4-ty@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rangemachine@gmail.com \
    --cc=ravi.bangoria@amd.com \
    --cc=whanos@sergal.fun \
    --cc=xiaoyao.li@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®