The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Yan Zhao <yan.y.zhao@intel.com>, seanjc@google.com
Cc: rick.p.edgecombe@intel.com, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org
Subject: Re: [PATCH v2 0/2] two KVM MMU fixes for TDX
Date: Mon, 24 Feb 2025 19:39:42 +0100	[thread overview]
Message-ID: <bb9e45ae-11ae-43bb-b53b-cf2e9dede3e5@redhat.com> (raw)
In-Reply-To: <20250220102436.24373-1-yan.y.zhao@intel.com>

On 2/20/25 11:24, Yan Zhao wrote:
> Hi,
> 
> There are two fixes to KVM MMU for TDX in response to two hypothetically
> triggered errors:
> (1) errors in tdh_mem_page_add(),
> (2) fatal errors in tdh_mem_sept_add()/tdh_mem_page_aug().
> 
> Patch 1 handles the error in SEPT zap resulting from error (1).
> Patch 2 fixes a possible stuck in the kernel loop introduced by error (2).
> 
> The two errors are not observed in any real workloads yet.
> The series is tested by faking the error in the SEAMCALL wrapper while
> bypassing the real SEAMCALLs.
> 
> v2:
> - Use kvm_check_request(KVM_REQ_VM_DEAD) to detect VM dead in patch 2.
>    (Sean)
> 
> v1: https://lore.kernel.org/all/20250217085535.19614-1-yan.y.zhao@intel.com
> 
> Thanks
> Yan

Applied to kvm-coco-queue, thanks.

Paolo


      parent reply	other threads:[~2025-02-24 18:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 10:24 [PATCH v2 0/2] two KVM MMU fixes for TDX Yan Zhao
2025-02-20 10:26 ` [PATCH v2 1/2] KVM: TDX: Handle SEPT zap error due to page add error in premap Yan Zhao
2025-02-20 10:27 ` [PATCH v2 2/2] KVM: x86/mmu: Bail out kvm_tdp_map_page() when VM dead Yan Zhao
2025-02-24 18:39 ` Paolo Bonzini [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=bb9e45ae-11ae-43bb-b53b-cf2e9dede3e5@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rick.p.edgecombe@intel.com \
    --cc=seanjc@google.com \
    --cc=yan.y.zhao@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