From: Pratyush Yadav <pratyush@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Alexander Graf <graf@amazon.com>, Mike Rapoport <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>
Cc: kexec@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Suren Baghdasaryan <surenb@google.com>
Subject: [PATCH v2 0/2] kho: clean up page initialization logic
Date: Fri, 16 Jan 2026 11:22:13 +0000 [thread overview]
Message-ID: <20260116112217.915803-1-pratyush@kernel.org> (raw)
From: "Pratyush Yadav (Google)" <pratyush@kernel.org>
Hi,
This series simplifies the page initialization logic in kho_restore_page(). It
was originally only a single patch [0], but on Pasha's suggestion, I added
another patch to use unsigned long for nr_pages.
Technically speaking, the patches aren't related and can be applied
independently, but bundling them together since patch 2 relies on 1 and it is
easier to manage them this way.
Changes in v2:
- Use unsigned long for nr_pages.
[0] https://lore.kernel.org/all/20251223104448.195589-1-pratyush@kernel.org/
Pratyush Yadav (2):
kho: use unsigned long for nr_pages
kho: simplify page initialization in kho_restore_page()
include/linux/kexec_handover.h | 6 ++--
kernel/liveupdate/kexec_handover.c | 47 +++++++++++++++++++-----------
2 files changed, 33 insertions(+), 20 deletions(-)
base-commit: 0f61b1860cc3f52aef9036d7235ed1f017632193
--
2.52.0.457.g6b5491de43-goog
next reply other threads:[~2026-01-16 11:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 11:22 Pratyush Yadav [this message]
2026-01-16 11:22 ` [PATCH v2 1/2] kho: use unsigned long for nr_pages Pratyush Yadav
2026-01-16 22:26 ` Andrew Morton
2026-01-20 13:06 ` Mike Rapoport
2026-01-20 13:03 ` Mike Rapoport
2026-01-22 19:08 ` Pasha Tatashin
2026-01-16 11:22 ` [PATCH v2 2/2] kho: simplify page initialization in kho_restore_page() Pratyush Yadav
2026-01-20 13:05 ` Mike Rapoport
2026-01-22 19:11 ` 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=20260116112217.915803-1-pratyush@kernel.org \
--to=pratyush@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=graf@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=rppt@kernel.org \
--cc=surenb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox