Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Shivansh Dhiman <shivansh.dhiman@amd.com>
To: <seanjc@google.com>, <pbonzini@redhat.com>, <tglx@linutronix.de>,
	<mingo@redhat.com>
Cc: <kvm@vger.kernel.org>, <x86@kernel.org>,
	<thomas.lendacky@amd.com>, <nikunj.dadhania@amd.com>,
	<santosh.shukla@amd.com>,
	Shivansh Dhiman <shivansh.dhiman@amd.com>
Subject: Re: [PATCH] KVM: SVM: Clear VMCB save area instead of entire VMCB on shutdown intercept
Date: Mon, 5 Oct 2026 23:46:57 +0530	[thread overview]
Message-ID: <533a53d3-cd7c-498f-8f5f-c22774fc1e58@amd.com> (raw)
In-Reply-To: <20260824131824.6040-1-shivansh.dhiman@amd.com>



On 24-08-26 18:48, Shivansh Dhiman wrote:
> The AMD APM previously stated that after an intercepted shutdown, the
> entire VMCB state is undefined. In practice, only the save area is
> undefined and most of the control area remains valid. Revision 3.45 of
> the APM now makes this explicit:
> 
>   "After an intercepted shutdown, the VMCB control area is valid (with
>    the exception of offsets 60h, 61h, and 68h) and the VMCB state save
>    area is undefined."
> 
> KVM zeroes the entire VMCB before INITing the vCPU based on the old
> wording, discarding control area state that hardware preserves.
> 
> Clear only the save area and the three undefined control area fields
> (int_ctl[15:0] and int_state) in line with the updated APM.

Hi,

Gentle ping for reviewing/merging this patch for VMCB save area
clearing on a shutdown intercept. Would appreciate any feedback or
guidance on next steps.

Thanks,
Shivansh

      parent reply	other threads:[~2026-10-05 18:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 13:18 [PATCH] KVM: SVM: Clear VMCB save area instead of entire VMCB on shutdown intercept Shivansh Dhiman
2026-08-24 13:51 ` sashiko-bot
2026-08-25  6:43   ` Shivansh Dhiman
2026-10-06  5:02     ` Sean Christopherson
2026-10-06 15:57       ` Shivansh Dhiman
2026-10-05 18:16 ` Shivansh Dhiman [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=533a53d3-cd7c-498f-8f5f-c22774fc1e58@amd.com \
    --to=shivansh.dhiman@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nikunj.dadhania@amd.com \
    --cc=pbonzini@redhat.com \
    --cc=santosh.shukla@amd.com \
    --cc=seanjc@google.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox