From: Dave Hansen <dave.hansen@intel.com>
To: "Pratik R. Sampat" <prsampat@amd.com>, Kiryl Shutsemau <kas@kernel.org>
Cc: linux-mm@kvack.org, linux-coco@lists.linux.dev, x86@kernel.org,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
ardb@kernel.org, akpm@linux-foundation.org, david@kernel.org,
osalvador@suse.de, thomas.lendacky@amd.com, michael.roth@amd.com
Subject: Re: [PATCH v3 2/2] x86/sev: Add support to unaccept memory after hot-remove
Date: Thu, 29 Jan 2026 09:39:55 -0800 [thread overview]
Message-ID: <b7cbc2f4-6fef-44c2-a0f4-2d6895c0fd74@intel.com> (raw)
In-Reply-To: <097a4980-9d10-40d2-9667-d07bf19e7b86@amd.com>
On 1/29/26 09:32, Pratik R. Sampat wrote:
> In that case a fall through for TDX (with a comment explaining why) and
> panic for rest may be the way to go?
No. panic() is an absolute last resort. It's almost never the way to go.
What else can we do to ensure we never reach this code if the platform
doesn't support memory un-acceptance?
next prev parent reply other threads:[~2026-01-29 17:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 20:41 [PATCH v3 0/2] SEV-SNP Unaccepted Memory Hotplug Pratik R. Sampat
2026-01-28 20:41 ` [PATCH v3 1/2] mm/memory_hotplug: Add support to accept memory during hot-add Pratik R. Sampat
2026-01-29 10:35 ` Kiryl Shutsemau
2026-01-29 17:32 ` Pratik R. Sampat
2026-01-28 20:41 ` [PATCH v3 2/2] x86/sev: Add support to unaccept memory after hot-remove Pratik R. Sampat
2026-01-28 21:08 ` Andrew Morton
2026-01-28 22:25 ` Pratik R. Sampat
2026-01-28 21:15 ` Dave Hansen
2026-01-29 10:40 ` Kiryl Shutsemau
2026-01-29 17:32 ` Pratik R. Sampat
2026-01-29 17:39 ` Dave Hansen [this message]
2026-01-29 19:32 ` Pratik R. Sampat
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=b7cbc2f4-6fef-44c2-a0f4-2d6895c0fd74@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=kas@kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=osalvador@suse.de \
--cc=prsampat@amd.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