mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: George Guo <dongtai.guo@linux.dev>
To: pratyush@kernel.org, ardb@kernel.org
Cc: chenhuacai@kernel.org, rppt@kernel.org,
	pasha.tatashin@soleen.com, shuah@kernel.org,
	ilias.apalodimas@linaro.org, akpm@linux-foundation.org,
	baoquan.he@linux.dev, ruirui.yang@linux.dev,
	guodongtai@kylinos.cn, kernel@xen0n.name, graf@amazon.com,
	liukexin@kylinos.cn, loongarch@lists.linux.dev,
	linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	linux-efi@vger.kernel.org
Subject: Re: [PATCH v6 1/8] efi: Pass KHO state to the next kernel in a configuration table
Date: Thu, 19 Nov 2026 21:36:31 +0900	[thread overview]
Message-ID: <20261119123631.11165-1-dongtai.guo@linux.dev> (raw)
In-Reply-To: <2vxzecch3x6k.fsf@kernel.org>

Hi Pratyush,

On Thu, Nov 19 2026, Pratyush Yadav wrote:
> Do we even care about non-EFI boot? I'd say ignore that for now until
> someone comes with a real use case for KHO on such systems.

OK. The fallback is only the existing setup_data path, kept when the
table is missing. I won't spend more effort on non-EFI boot, and
whether to remove setup_data can be decided in the x86 series.

> This should be a follow up series. Don't get your series get caught up
> in x86 changes.

Will do. v7 will keep the table common with LoongArch as the only
user, and the x86 patches will follow as a separate series.

> Sounds good to me. You will still need to chase Ard for an ACK on the
> generic EFI table though.

Ard, you asked whether this could be an arch table handled in the
LoongArch code. Pratyush would like a common table that x86 can move to
later, and the x86 prototype above used the same table without changing
its layout. Would you be OK with keeping it in drivers/firmware/efi/
for v7? If you would still rather have it in arch/loongarch/ until the
x86 series lands, I will move it there for v7.

Thanks,
George

  reply	other threads:[~2026-11-19 12:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 17:29 [PATCH v6 0/8] LoongArch: Add KHO support and selftests George Guo
2026-10-29 17:29 ` [PATCH v6 1/8] efi: Pass KHO state to the next kernel in a configuration table George Guo
2026-10-29 19:28   ` Ard Biesheuvel
2026-10-29 19:42     ` Pratyush Yadav
2026-11-03 10:29     ` George Guo
2026-11-04  3:59       ` Huacai Chen
2026-11-19  8:22         ` George Guo
2026-11-19 10:58           ` Pratyush Yadav
2026-11-19 12:36             ` George Guo [this message]
2026-11-04 14:54   ` Mukesh Pilaniya
2026-10-29 17:29 ` [PATCH v6 2/8] kho: Write KHO state to the EFI table at kexec time George Guo
2026-10-29 17:29 ` [PATCH v6 3/8] kho: Include linux/mm.h in kho_block.c George Guo
2026-10-29 17:29 ` [PATCH v6 4/8] kho: Add kho_disable() George Guo
2026-11-05 12:53   ` Mike Rapoport
2026-10-29 17:29 ` [PATCH v6 5/8] LoongArch: Allow memblock arrays to resize George Guo
2026-11-05 12:57   ` Mike Rapoport
2026-11-05 15:07     ` Huacai Chen
2026-11-05 16:07       ` Mike Rapoport
2026-11-06 14:35         ` Huacai Chen
2026-11-08  8:14           ` Mike Rapoport
2026-11-08  8:26             ` Huacai Chen
2026-10-29 17:29 ` [PATCH v6 6/8] LoongArch: Enable kexec handover (KHO) George Guo
2026-10-29 17:29 ` [PATCH v6 7/8] selftests/kho: Add LoongArch vmtest support George Guo
2026-10-29 17:29 ` [PATCH v6 8/8] selftests/liveupdate: " George Guo

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=20261119123631.11165-1-dongtai.guo@linux.dev \
    --to=dongtai.guo@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=ardb@kernel.org \
    --cc=baoquan.he@linux.dev \
    --cc=chenhuacai@kernel.org \
    --cc=graf@amazon.com \
    --cc=guodongtai@kylinos.cn \
    --cc=ilias.apalodimas@linaro.org \
    --cc=kernel@xen0n.name \
    --cc=kexec@lists.infradead.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liukexin@kylinos.cn \
    --cc=loongarch@lists.linux.dev \
    --cc=pasha.tatashin@soleen.com \
    --cc=pratyush@kernel.org \
    --cc=rppt@kernel.org \
    --cc=ruirui.yang@linux.dev \
    --cc=shuah@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

all inboxes | Powered by JetHome®