All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Chris Down" <chris@chrisdown.name>,
	"Pasha Tatashin" <pasha.tatashin@soleen.com>,
	"Mike Rapoport" <rppt@kernel.org>,
	"Pratyush Yadav" <pratyush@kernel.org>
Cc: "Alexander Graf" <graf@amazon.com>,
	"Baoquan He" <baoquan.he@linux.dev>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	kexec@lists.infradead.org, kernel-team@meta.com
Subject: Re: [PATCH 7/9] kho: Report how much handover memory is preserved and restored
Date: Thu, 12 Nov 2026 07:54:12 +0000	[thread overview]
Message-ID: <sashiko-outbox-210643@kernel.org> (raw)
In-Reply-To: <920192d01c6534b5754648e12840f73cdcfa73de.1794383544.git.chris@chrisdown.name>

> Most memory the previous kernel preserved stays reserved until its user
> restores it through KHO, either to use it again or to free it. If
> nothing does, it stays reserved for as long as the kernel runs. On a
> hypervisor host that can be gigabytes, but amusingly nothing really
> shows it reliably. The host simply has less memory than it should, which
> is not exactly obvious.
> 
> All preserved memory is reserved in kho_preserved_memory_reserve(), and
> everything restored through KHO goes through kho_restore_page(), so KHO
> can count both easily. Let's add preserved_size and restored_size, in
> bytes, to /sys/kernel/kexec/kho_incoming/.
> 
> For example, after a live update preserving a 64 MiB memfd:
> 
>                      preserved_size  restored_size
>     before retrieval       67403776           8192
>     after retrieval        67403776       67395584
> 
> The 8 KiB left are the incoming KHO FDT and LUO's FLB header.
> 
> Signed-off-by: Chris Down <chris@chrisdown.name>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1794383544.git.chris@chrisdown.name?part=7



  reply	other threads:[~2026-11-12  7:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11  7:52 [PATCH 0/9] kho, liveupdate: KHO/LUO observability Chris Down
2026-11-11  7:52 ` [PATCH 1/9] kho: Reclaim the metadata page left reserved after kexec Chris Down
2026-11-11 11:08   ` Breno Leitao
2026-11-11 22:29   ` Pasha Tatashin
2026-11-12  7:54   ` sashiko-bot
2026-11-11  7:53 ` [PATCH 2/9] kho: Make bootmem reservations visible to fleet monitoring Chris Down
2026-11-11 23:14   ` Pasha Tatashin
2026-11-12  7:54   ` sashiko-bot
2026-11-11  7:53 ` [PATCH 3/9] liveupdate: Make failed retrieves distinguishable from dropped files Chris Down
2026-11-12  7:54   ` sashiko-bot
2026-11-11  7:53 ` [PATCH 4/9] selftests/liveupdate: Catch incorrect file accounting across kexec Chris Down
2026-11-12  7:54   ` sashiko-bot
2026-11-11  7:53 ` [PATCH 5/9] selftests/kho: Catch missing or zero bootmem reports before kexec Chris Down
2026-11-12  7:54   ` sashiko-bot
2026-11-11  7:53 ` [PATCH 6/9] kho: Expose rejected handovers that look like cold boots Chris Down
2026-11-12  7:54   ` sashiko-bot
2026-11-11  7:53 ` [PATCH 7/9] kho: Report how much handover memory is preserved and restored Chris Down
2026-11-12  7:54   ` sashiko-bot [this message]
2026-11-11  7:53 ` [PATCH 8/9] liveupdate: Expose the sequence number for consecutive live updates Chris Down
2026-11-12  7:54   ` sashiko-bot
2026-11-11  7:53 ` [PATCH 9/9] selftests/liveupdate: Check handover revival, sequence and memory stats Chris Down
2026-11-12  7:54   ` sashiko-bot

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=sashiko-outbox-210643@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=baoquan.he@linux.dev \
    --cc=chris@chrisdown.name \
    --cc=corbet@lwn.net \
    --cc=graf@amazon.com \
    --cc=kernel-team@meta.com \
    --cc=kexec@lists.infradead.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=pratyush@kernel.org \
    --cc=rppt@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=skhan@linuxfoundation.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.