The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Jürgen Groß" <jgross@suse.com>
To: Dave Hansen <dave.hansen@intel.com>,
	"Reshetova, Elena" <elena.reshetova@intel.com>,
	"Annapurve, Vishal" <vannapurve@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"bp@alien8.de" <bp@alien8.de>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"thomas.lendacky@amd.com" <thomas.lendacky@amd.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"kas@kernel.org" <kas@kernel.org>,
	"Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
	"dwmw@amazon.co.uk" <dwmw@amazon.co.uk>,
	"Huang, Kai" <kai.huang@intel.com>,
	"seanjc@google.com" <seanjc@google.com>,
	"Chatre, Reinette" <reinette.chatre@intel.com>,
	"Yamahata, Isaku" <isaku.yamahata@intel.com>,
	"Williams, Dan J" <dan.j.williams@intel.com>,
	"ashish.kalra@amd.com" <ashish.kalra@amd.com>,
	"nik.borisov@suse.com" <nik.borisov@suse.com>,
	"Gao, Chao" <chao.gao@intel.com>,
	"sagis@google.com" <sagis@google.com>,
	"Chen, Farrah" <farrah.chen@intel.com>,
	Binbin Wu <binbin.wu@linux.intel.com>
Subject: Re: [PATCH 4/7] x86/kexec: Disable kexec/kdump on platforms with TDX partial write erratum
Date: Wed, 8 Oct 2025 20:13:41 +0200	[thread overview]
Message-ID: <c68c29ba-fe81-4411-b976-7867120e38ca@suse.com> (raw)
In-Reply-To: <9d86698d-525e-4d8c-b3d9-b6a0e7634649@intel.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 626 bytes --]

On 08.10.25 17:40, Dave Hansen wrote:
> On 10/7/25 06:31, Jürgen Groß wrote:>
>> If we can't come to an agreement that kdump should be allowed in
>> spite of a potential #MC, maybe we could disable kdump only if TDX
>> guests have been active on the machine before?
> 
> How would we determine that?
> 
> We can't just call the TDX module to see because it might have been
> running before but got shut down.

Ah, okay, I didn't think of that.

Then we could add a kernel boot parameter to let the user opt-in for kexec
being possible in spite of the potential #MC. I think this should cover it.


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2025-10-08 18:13 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01 16:09 [PATCH v8 0/7] TDX host: kexec/kdump support Paolo Bonzini
2025-09-01 16:09 ` [PATCH 1/7] x86/kexec: Consolidate relocate_kernel() function parameters Paolo Bonzini
2025-09-01 16:09 ` [PATCH 2/7] x86/sme: Use percpu boolean to control WBINVD during kexec Paolo Bonzini
2025-09-01 16:09 ` [PATCH 3/7] x86/virt/tdx: Mark memory cache state incoherent when making SEAMCALL Paolo Bonzini
2025-09-01 16:09 ` [PATCH 4/7] x86/kexec: Disable kexec/kdump on platforms with TDX partial write erratum Paolo Bonzini
2025-09-30  1:38   ` Vishal Annapurve
2025-09-30 21:32     ` Dave Hansen
2025-10-01  2:05       ` Vishal Annapurve
2025-10-01 14:32         ` Dave Hansen
2025-10-01 17:17           ` Vishal Annapurve
2025-10-01 18:00             ` Dave Hansen
2025-10-01 21:19               ` Huang, Kai
2025-10-02  6:59             ` Reshetova, Elena
2025-10-02  7:46               ` Juergen Gross
2025-10-02  8:10                 ` Reshetova, Elena
2025-10-02 15:06                 ` Dave Hansen
2025-10-02 16:09                   ` Vishal Annapurve
2025-10-18 15:54                     ` Vishal Annapurve
2025-10-21 17:08                       ` Dave Hansen
2025-10-22  2:50                         ` Vishal Annapurve
2025-10-22 21:05                           ` Huang, Kai
2025-10-23 16:54                             ` Vishal Annapurve
2025-10-07 13:31                   ` Jürgen Groß
2025-10-08 15:40                     ` Dave Hansen
2025-10-08 18:13                       ` Jürgen Groß [this message]
2025-10-26 23:33   ` Vishal Annapurve
2025-10-27  0:50     ` Huang, Kai
2025-10-27 16:23       ` Edgecombe, Rick P
2025-10-27 21:28         ` Huang, Kai
2025-10-28  0:07           ` Vishal Annapurve
2025-10-28  9:31             ` Huang, Kai
2025-11-03 16:44               ` Vishal Annapurve
2025-09-01 16:09 ` [PATCH 5/7] x86/virt/tdx: Remove the !KEXEC_CORE dependency Paolo Bonzini
2025-09-01 16:09 ` [PATCH 6/7] x86/virt/tdx: Update the kexec section in the TDX documentation Paolo Bonzini
2025-09-01 16:09 ` [PATCH 7/7] KVM: TDX: Explicitly do WBINVD when no more TDX SEAMCALLs Paolo Bonzini
2025-10-03 13:09 ` [PATCH v8 0/7] TDX host: kexec/kdump support Paolo Bonzini
2025-10-03 13:54   ` David Woodhouse
2025-10-03 14:05   ` Dave Hansen

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=c68c29ba-fe81-4411-b976-7867120e38ca@suse.com \
    --to=jgross@suse.com \
    --cc=ashish.kalra@amd.com \
    --cc=binbin.wu@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=chao.gao@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@intel.com \
    --cc=dwmw@amazon.co.uk \
    --cc=elena.reshetova@intel.com \
    --cc=farrah.chen@intel.com \
    --cc=hpa@zytor.com \
    --cc=isaku.yamahata@intel.com \
    --cc=kai.huang@intel.com \
    --cc=kas@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nik.borisov@suse.com \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=reinette.chatre@intel.com \
    --cc=rick.p.edgecombe@intel.com \
    --cc=sagis@google.com \
    --cc=seanjc@google.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --cc=vannapurve@google.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