From: Pratyush Yadav <pratyush@kernel.org>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: linux-kselftest@vger.kernel.org, rppt@kernel.org,
shuah@kernel.org, akpm@linux-foundation.org,
linux-mm@kvack.org, skhan@linuxfoundation.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
corbet@lwn.net, dmatlack@google.com, kexec@lists.infradead.org,
pratyush@kernel.org, skhawaja@google.com, graf@amazon.com
Subject: Re: [PATCH v5 08/13] liveupdate: defer session block allocation and PA setting
Date: Tue, 02 Jun 2026 19:06:25 +0200 [thread overview]
Message-ID: <2vxzv7c0dg8e.fsf@kernel.org> (raw)
In-Reply-To: <20260602031717.197696-9-pasha.tatashin@soleen.com> (Pasha Tatashin's message of "Tue, 2 Jun 2026 03:17:12 +0000")
On Tue, Jun 02 2026, Pasha Tatashin wrote:
> Currently, luo_session_setup_outgoing() allocates the session block and
> sets its physical address in the header immediately. With upcoming
> dynamic block-based session management, this makes the first block
> different from the rest. Move the allocation to where it is first needed.
>
> Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> Reviewed-by: Pratyush Yadav (Google) <pratyush@kernel.org>
> Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
> ---
> include/linux/kho_block.h | 22 +++++++++++
> kernel/liveupdate/luo_core.c | 4 +-
> kernel/liveupdate/luo_internal.h | 2 +-
> kernel/liveupdate/luo_session.c | 68 ++++++++++++++++++++------------
> 4 files changed, 67 insertions(+), 29 deletions(-)
>
> diff --git a/include/linux/kho_block.h b/include/linux/kho_block.h
> index 505bf78409f2..0a8cda2cbfb5 100644
> --- a/include/linux/kho_block.h
> +++ b/include/linux/kho_block.h
> @@ -70,6 +70,28 @@ int kho_block_set_restore(struct kho_block_set *bs, u64 head_pa);
> void kho_block_set_destroy(struct kho_block_set *bs);
> void kho_block_set_clear(struct kho_block_set *bs);
>
> +/**
> + * kho_block_set_head_pa - Get the physical address of the first block header.
> + * @bs: The block set.
> + *
> + * Return: The physical address of the first block header, or 0 if empty.
> + */
> +static inline u64 kho_block_set_head_pa(struct kho_block_set *bs)
> +{
> + return bs->head_pa;
> +}
> +
> +/**
> + * kho_block_set_is_empty - Check if the block set has no allocated blocks.
> + * @bs: The block set.
> + *
> + * Return: True if there are no blocks in the set, false otherwise.
> + */
> +static inline bool kho_block_set_is_empty(struct kho_block_set *bs)
> +{
> + return list_empty(&bs->blocks);
> +}
> +
Are these intended to be here or should they go in patch 7?
> void kho_block_it_init(struct kho_block_it *it, struct kho_block_set *bs);
> void *kho_block_it_reserve_entry(struct kho_block_it *it);
> void *kho_block_it_read_entry(struct kho_block_it *it);
[...]
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2026-06-02 17:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 3:17 [PATCH v5 00/13] liveupdate: Remove limits on sessions and files Pasha Tatashin
2026-06-02 3:17 ` [PATCH v5 01/13] liveupdate: change file_set->count type to u64 for type safety Pasha Tatashin
2026-06-02 3:17 ` [PATCH v5 02/13] liveupdate: avoid mixing cleanup guards with goto in luo_session_retrieve_fd Pasha Tatashin
2026-06-02 3:17 ` [PATCH v5 03/13] liveupdate: centralize state management into struct luo_ser Pasha Tatashin
2026-06-02 3:17 ` [PATCH v5 04/13] liveupdate: register luo_ser as KHO subtree Pasha Tatashin
2026-06-02 17:02 ` Pratyush Yadav
2026-06-02 3:17 ` [PATCH v5 05/13] liveupdate: Extract luo_file_deserialize_one helper Pasha Tatashin
2026-06-02 3:17 ` [PATCH v5 06/13] liveupdate: Extract luo_session_deserialize_one helper Pasha Tatashin
2026-06-02 3:17 ` [PATCH v5 07/13] kho: add support for linked-block serialization Pasha Tatashin
2026-06-02 3:17 ` [PATCH v5 08/13] liveupdate: defer session block allocation and PA setting Pasha Tatashin
2026-06-02 17:06 ` Pratyush Yadav [this message]
2026-06-02 3:17 ` [PATCH v5 09/13] liveupdate: Remove limit on the number of sessions Pasha Tatashin
2026-06-02 3:17 ` [PATCH v5 10/13] liveupdate: Remove limit on the number of files per session Pasha Tatashin
2026-06-02 17:07 ` Pratyush Yadav
2026-06-02 3:17 ` [PATCH v5 11/13] selftests/liveupdate: Test session and file limit removal Pasha Tatashin
2026-06-02 3:17 ` [PATCH v5 12/13] selftests/liveupdate: Add stress-sessions kexec test Pasha Tatashin
2026-06-02 3:17 ` [PATCH v5 13/13] selftests/liveupdate: Add stress-files " Pasha Tatashin
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=2vxzv7c0dg8e.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=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=skhawaja@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.