All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: "Pasha Tatashin" <pasha.tatashin@soleen.com>
Cc: "Pratyush Yadav" <pratyush@kernel.org>,
	 "Mike Rapoport" <rppt@kernel.org>,
	 "Alexander Graf" <graf@amazon.com>,
	 "Jonathan Corbet" <corbet@lwn.net>,
	 "Shuah Khan" <skhan@linuxfoundation.org>,
	 "Randy Dunlap" <rdunlap@infradead.org>,
	 "Andrew Morton" <akpm@linux-foundation.org>,
	 "Tarun Sahu" <tarunsahu@google.com>,
	 "David Matlack" <dmatlack@google.com>,
	 "Samiullah Khawaja" <skhawaja@google.com>,
	 <kexec@lists.infradead.org>, <linux-mm@kvack.org>,
	 <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	 <linux-kselftest@vger.kernel.org>
Subject: Re: [RFC PATCH 2/5] kho: build KHO objects into a single kho.o
Date: Tue, 17 Nov 2026 11:41:11 +0100	[thread overview]
Message-ID: <2vxz5wxvhha0.fsf@kernel.org> (raw)
In-Reply-To: <DMWWRQTLNYH6.1LJ2K5HT60LK8@soleen.com> (Pasha Tatashin's message of "Mon, 16 Nov 2026 15:13:23 -0500")

On Mon, Nov 16 2026, Pasha Tatashin wrote:

> On Mon Nov 16, 2026 at 8:40 AM EST, Pratyush Yadav wrote:
>> From: "Pratyush Yadav (Google)" <pratyush@kernel.org>
>>
>> kho_block.o is part of the KHO infrastructure, but is currently built as
>> part of luo.o, which ties it to CONFIG_LIVEUPDATE.
>>
>> Group all KHO objects into a composite kho.o, built for
>> CONFIG_KEXEC_HANDOVER, the same way the LUO objects are grouped into
>> luo.o. This also gives a single place to add new KHO objects.
>>
>> Signed-off-by: Pratyush Yadav (Google) <pratyush@kernel.org>
>> ---
>>  kernel/liveupdate/Makefile | 12 ++++++++----
>>  1 file changed, 8 insertions(+), 4 deletions(-)
>>
>> diff --git a/kernel/liveupdate/Makefile b/kernel/liveupdate/Makefile
>> index d9f4694625567..bc679905ce3f2 100644
>> --- a/kernel/liveupdate/Makefile
>> +++ b/kernel/liveupdate/Makefile
>> @@ -1,13 +1,17 @@
>>  # SPDX-License-Identifier: GPL-2.0
>>  
>> +kho-y :=								\
>> +		kexec_handover.o				\
>> +		kho_block.o
>> +
>> +kho-$(CONFIG_KEXEC_HANDOVER_DEBUGFS) += kexec_handover_debugfs.o
>> +
>> +obj-$(CONFIG_KEXEC_HANDOVER)		+= kho.o
>> +
>>  luo-y :=								\
>> -		kho_block.o						\
>>  		luo_core.o						\
>>  		luo_file.o						\
>>  		luo_flb.o						\
>>  		luo_session.o
>>  
>> -obj-$(CONFIG_KEXEC_HANDOVER)		+= kexec_handover.o
>> -obj-$(CONFIG_KEXEC_HANDOVER_DEBUGFS)	+= kexec_handover_debugfs.o
>> -
>>  obj-$(CONFIG_LIVEUPDATE)		+= luo.o
>
> Please send it as a separate patch. I have the same change included as 
> part of the kho-ro series, but let's fix it outside of both series 
> instead as a standalone fix. Also, maybe rename kexec_handover_debugfs.c 
> to kho_debugfs.c and kexec_handover.c to kho_core.c for consistency, now 
> that they are not shared with the rest of the kexec_* files in kernel/*?

Sure, makes sense. I have a few other misc cleanups in mind like
re-organizing some of the KHO headers. I can do that all in a single
"misc cleanups" series.

-- 
Regards,
Pratyush Yadav

  reply	other threads:[~2026-11-17 10:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 13:40 [RFC PATCH 0/5] KHO map Pratyush Yadav
2026-11-16 13:40 ` [RFC PATCH 1/5] kho: add KHOSER_CLEAR_PTR() Pratyush Yadav
2026-11-16 13:40 ` [RFC PATCH 2/5] kho: build KHO objects into a single kho.o Pratyush Yadav
2026-11-16 20:13   ` Pasha Tatashin
2026-11-17 10:41     ` Pratyush Yadav [this message]
2026-11-16 13:40 ` [RFC PATCH 3/5] kho: add KHO map Pratyush Yadav
2026-11-16 13:40 ` [RFC PATCH 4/5] kho: test: add KHO map test Pratyush Yadav
2026-11-16 13:40 ` [RFC PATCH 5/5] mm/memfd_luo: use KHO map for tracking folios Pratyush Yadav
2026-11-16 22:45 ` [RFC PATCH 0/5] KHO map Pasha Tatashin
2026-11-17 12:26   ` Pratyush Yadav
2026-11-17 15:35     ` Pratyush Yadav
2026-11-17 16:05       ` Pasha Tatashin
2026-11-17 10:10 ` Chris Down
2026-11-17 12:19   ` Pratyush Yadav

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=2vxz5wxvhha0.fsf@kernel.org \
    --to=pratyush@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=dmatlack@google.com \
    --cc=graf@amazon.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=rdunlap@infradead.org \
    --cc=rppt@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=skhawaja@google.com \
    --cc=tarunsahu@google.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 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.