From: Rik van Riel <riel@surriel.com>
To: "David Hildenbrand (Red Hat)" <david@kernel.org>,
Borislav Petkov <bp@alien8.de>, Kiryl Shutsemau <kas@kernel.org>
Cc: "Pratik R. Sampat" <prsampat@amd.com>,
linux-mm@kvack.org, linux-coco@lists.linux.dev,
linux-efi@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, dave.hansen@linux.intel.com, ardb@kernel.org,
akpm@linux-foundation.org, osalvador@suse.de,
thomas.lendacky@amd.com, michael.roth@amd.com
Subject: Re: [RFC PATCH 2/4] mm: Add support for unaccepted memory hotplug
Date: Wed, 03 Dec 2025 10:00:03 -0500 [thread overview]
Message-ID: <ed2fd8ed5d3c64e0e57e0d38fe6e3d712f22d13f.camel@surriel.com> (raw)
In-Reply-To: <beec5651-5c23-4f5e-a0a3-d1cc01a8490a@kernel.org>
On Fri, 2025-11-28 at 10:30 +0100, David Hildenbrand (Red Hat) wrote:
> On 11/27/25 19:12, Borislav Petkov wrote:
> >
> > None of that matters if you kexec the same kernels.
> >
> > IOW, for some reason you want to be able to kexec different
> > kernels. The
> > question is why do we care?
>
> kexecing the same kernel is typically used for kdump purposes.
>
> kexecing different kernels is used for all sorts of things
> (live-upgrade, grub-emu come to mind). It's quite common to kexec
> different kernels, or maybe I misunderstood the question here?
>
Even for kdump it is not unusual to use a different
kernel.
When working on kernel code, getting a proper crash
dump can really help figure out where my code went
wrong.
It helps if the kdump kernel doesn't have the same
broken code that my test kernel does :)
--
All Rights Reversed.
next prev parent reply other threads:[~2025-12-03 15:00 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 17:57 [RFC PATCH 0/4] SEV-SNP Unaccepted Memory Hotplug Pratik R. Sampat
2025-11-25 17:57 ` [RFC PATCH 1/4] efi/libstub: Decouple memory bitmap from the unaccepted table Pratik R. Sampat
2025-11-26 11:08 ` Kiryl Shutsemau
2025-11-26 22:27 ` Pratik R. Sampat
2025-11-27 17:29 ` Kiryl Shutsemau
2025-11-25 17:57 ` [RFC PATCH 2/4] mm: Add support for unaccepted memory hotplug Pratik R. Sampat
2025-11-26 11:12 ` Kiryl Shutsemau
2025-11-26 22:27 ` Pratik R. Sampat
2025-11-27 17:40 ` Kiryl Shutsemau
2025-11-28 9:34 ` David Hildenbrand (Red Hat)
2025-12-01 17:15 ` Pratik R. Sampat
2025-12-01 18:25 ` David Hildenbrand (Red Hat)
2025-12-01 19:35 ` Pratik R. Sampat
2025-12-01 17:15 ` Pratik R. Sampat
2025-12-01 17:48 ` Kiryl Shutsemau
2025-12-01 17:58 ` Pratik R. Sampat
2025-11-26 22:31 ` Borislav Petkov
2025-11-27 17:35 ` Kiryl Shutsemau
2025-11-27 18:12 ` Borislav Petkov
2025-11-28 9:30 ` David Hildenbrand (Red Hat)
2025-11-28 11:34 ` Borislav Petkov
2025-12-01 9:18 ` David Hildenbrand (Red Hat)
2025-12-01 11:12 ` Borislav Petkov
2025-12-01 18:32 ` David Hildenbrand (Red Hat)
2025-12-01 19:10 ` Borislav Petkov
2025-12-01 20:10 ` David Hildenbrand (Red Hat)
2025-12-01 20:25 ` Borislav Petkov
2025-12-01 20:36 ` David Hildenbrand (Red Hat)
2025-12-03 14:46 ` Kiryl Shutsemau
2025-12-03 15:58 ` Borislav Petkov
2025-12-03 15:00 ` Rik van Riel [this message]
2025-11-28 9:32 ` David Hildenbrand (Red Hat)
2025-12-01 17:21 ` Pratik R. Sampat
2025-12-01 18:36 ` David Hildenbrand (Red Hat)
2025-12-01 19:35 ` Pratik R. Sampat
2025-12-09 21:36 ` Pratik R. Sampat
2025-12-11 15:00 ` Kiryl Shutsemau
2025-12-11 22:07 ` Pratik R. Sampat
2025-11-25 17:57 ` [RFC PATCH 3/4] x86/sev: Introduce hotplug-aware SNP page state validation Pratik R. Sampat
2025-11-25 17:57 ` [RFC PATCH 4/4] mm: Add support for unaccepted memory hot-remove 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=ed2fd8ed5d3c64e0e57e0d38fe6e3d712f22d13f.camel@surriel.com \
--to=riel@surriel.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-efi@vger.kernel.org \
--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 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.