From: Jan Kiszka <jan.kiszka@siemens.com>
To: Shivanand Kunijadar <Shivanand.Kunijadar@toshiba-tsip.com>,
cip-dev@lists.cip-project.org
Cc: dinesh.kumar@toshiba-tsip.com, kazuhiro3.hayashi@toshiba.co.jp
Subject: Re: [isar-cip-core][PATCH v1 0/5] Add support for delta kernel binary update
Date: Wed, 13 Aug 2025 16:52:22 +0200 [thread overview]
Message-ID: <420f5c3e-e5fc-41fc-8b95-e5e86af0e4dd@siemens.com> (raw)
In-Reply-To: <20250813134630.3943194-1-Shivanand.Kunijadar@toshiba-tsip.com>
On 13.08.25 15:46, Shivanand Kunijadar wrote:
> This patch series enables the delta kernel binary updates along with
> rootfs. When rdiff is selected it generates deltas for both kernel and rootfs.
>
> In the CI, we just change PV value to 2.0 for the second image and there
> is no change (code) in the kernel binary at the moment. Do you think building
> the second image with RT kernel is appropriate here to verify delta
> kernel updates?
Right, we may need a better delta example for the kernel. I originally
chose that (prior to delta updates) for having changes both in the
kernel and the rootfs that have to correlate. But we actually already
have a link because the ID or hash of the rootfs needs to be stored in
the UKI and, thus, updated in lock-step with the image.
For delta demonstration, we likely need a small change in the rootfs
only. Maybe enable/disable CONFIG_IMAGE_TESTING / kas/opt/test.yml? Or
something artificial and truly small, but that would clutter our menu...
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
next prev parent reply other threads:[~2025-08-13 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 13:46 [isar-cip-core][PATCH v1 0/5] Add support for delta kernel binary update Shivanand Kunijadar
2025-08-13 13:46 ` [isar-cip-core][PATCH v1 1/5] delta-update.yml: Add previous image kernel file for rdiff delta update Shivanand Kunijadar
2025-08-13 13:46 ` [isar-cip-core][PATCH v1 2/5] Add delta update support for kernel binary update using rdiff_file handler Shivanand Kunijadar
2025-08-14 10:08 ` Jan Kiszka
2025-08-14 10:13 ` Shivanand.Kunijadar
2025-08-13 13:46 ` [isar-cip-core][PATCH v1 3/5] README.swupdate.md: Modify readme for kernel binary delta update support Shivanand Kunijadar
2025-08-13 13:46 ` [isar-cip-core][PATCH v1 4/5] swupdate-handler-roundrobin: Update revision for rdiff_file handler support Shivanand Kunijadar
2025-08-13 13:46 ` [isar-cip-core][PATCH v1 5/5] .gitlab-ci.yml: Add linux.efi to previous image folder Shivanand Kunijadar
2025-08-13 14:52 ` Jan Kiszka [this message]
2025-08-14 5:28 ` [cip-dev] [isar-cip-core][PATCH v1 0/5] Add support for delta kernel binary update Shivanand.Kunijadar
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=420f5c3e-e5fc-41fc-8b95-e5e86af0e4dd@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Shivanand.Kunijadar@toshiba-tsip.com \
--cc=cip-dev@lists.cip-project.org \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
/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