From: Sean Christopherson <seanjc@google.com>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, Kai Huang <kai.huang@intel.com>
Subject: Re: [PATCH 6.1.y 2/3] x86/reboot: KVM: Handle VMXOFF in KVM's reboot callback
Date: Thu, 14 Aug 2025 13:25:32 -0700 [thread overview]
Message-ID: <aJ5GPOjf24EW1RPB@google.com> (raw)
In-Reply-To: <20250724170725.1404455-2-sashal@kernel.org>
On Thu, Jul 24, 2025, Sasha Levin wrote:
> From: Sean Christopherson <seanjc@google.com>
>
> [ Upstream commit 119b5cb4ffd0166f3e98e9ee042f5046f7744f28 ]
>
> Use KVM VMX's reboot/crash callback to do VMXOFF in an emergency instead
> of manually and blindly doing VMXOFF. There's no need to attempt VMXOFF
> if a hypervisor, i.e. KVM, isn't loaded/active, i.e. if the CPU can't
> possibly be post-VMXON.
>
> Reviewed-by: Kai Huang <kai.huang@intel.com>
> Link: https://lore.kernel.org/r/20230721201859.2307736-4-seanjc@google.com
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> Stable-dep-of: a0ee1d5faff1 ("KVM: VMX: Flush shadow VMCS on emergency reboot")
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
Acked-by: Sean Christopherson <seanjc@google.com>
next prev parent reply other threads:[~2025-08-14 20:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 9:06 FAILED: patch "[PATCH] KVM: VMX: Flush shadow VMCS on emergency reboot" failed to apply to 6.1-stable tree gregkh
2025-07-24 17:07 ` [PATCH 6.1.y 1/3] x86/reboot: Harden virtualization hooks for emergency reboot Sasha Levin
2025-07-24 17:07 ` [PATCH 6.1.y 2/3] x86/reboot: KVM: Handle VMXOFF in KVM's reboot callback Sasha Levin
2025-08-14 20:25 ` Sean Christopherson [this message]
2025-07-24 17:07 ` [PATCH 6.1.y 3/3] KVM: VMX: Flush shadow VMCS on emergency reboot Sasha Levin
2025-08-14 20:25 ` Sean Christopherson
2025-08-14 20:25 ` [PATCH 6.1.y 1/3] x86/reboot: Harden virtualization hooks for " Sean Christopherson
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=aJ5GPOjf24EW1RPB@google.com \
--to=seanjc@google.com \
--cc=kai.huang@intel.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.