From: Petr Mladek <pmladek@suse.com>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: jpoimboe@kernel.org, jikos@kernel.org, mbenes@suse.cz,
joe.lawrence@redhat.com, live-patching@vger.kernel.org
Subject: Re: [PATCH v2 1/3] livepatch: Add "replace" sysfs attribute
Date: Mon, 24 Jun 2024 15:46:35 +0200 [thread overview]
Message-ID: <Znl4u_dWfqK53G3k@pathway.suse.cz> (raw)
In-Reply-To: <20240610013237.92646-2-laoar.shao@gmail.com>
On Mon 2024-06-10 09:32:35, Yafang Shao wrote:
> When building a livepatch, a user can set it to be either an atomic replace
> livepatch or a non atomic replace livepatch. However, it is not easy to
> identify whether a livepatch is atomic replace or not until it actually
> replaces some old livepatches. It will be beneficial to show it directly.
>
> A new sysfs interface called 'replace' is introduced in this patch. The
> result after this change is as follows:
>
> $ cat /sys/kernel/livepatch/livepatch-non_replace/replace
> 0
>
> $ cat /sys/kernel/livepatch/livepatch-replace/replace
> 1
The description is not sufficient. It does not explain why this
information is useful.
The proposed change allows to see the replace flag only when
the livepatch is already installed. But the value does
not have any effect at this point. It has effect only when
the livepatch is being installed.
I would propose something like:
<proposal>
There are situations when it might make sense to combine livepatches
with and without the atomic replace on the same system. For example,
the livepatch without the atomic replace might provide a hotfix
or extra tuning.
Managing livepatches on such systems might be challenging. And the
information which of the installed livepatches do not use the atomic
replace would be useful.
Add new sysfs interface 'replace'. It works as follows:
$ cat /sys/kernel/livepatch/livepatch-non_replace/replace
0
$ cat /sys/kernel/livepatch/livepatch-replace/replace
1
</proposal>
> Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
Otherwise the change looks good.
With a better description:
Reviewed-by: Petr Mladek <pmladek@suse.com>
Best Regards,
Petr
next prev parent reply other threads:[~2024-06-24 13:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 1:32 [PATCH v2 0/3] livepatch: Add "replace" sysfs attribute Yafang Shao
2024-06-10 1:32 ` [PATCH v2 1/3] " Yafang Shao
2024-06-24 13:46 ` Petr Mladek [this message]
2024-06-25 2:14 ` Yafang Shao
2024-06-10 1:32 ` [PATCH v2 2/3] selftests/livepatch: Add selftests for " Yafang Shao
2024-06-11 17:28 ` Marcos Paulo de Souza
2024-06-24 13:49 ` Petr Mladek
2024-06-10 1:32 ` [PATCH v2 3/3] livepatch: Replace snprintf() with sysfs_emit() Yafang Shao
2024-06-24 13:50 ` Petr Mladek
2024-06-10 17:18 ` [PATCH v2 0/3] livepatch: Add "replace" sysfs attribute Song Liu
2024-06-11 2:46 ` Yafang Shao
2024-06-11 5:01 ` Song Liu
2024-06-21 7:31 ` Petr Mladek
2024-06-21 8:39 ` Yafang Shao
2024-06-21 10:04 ` Petr Mladek
2024-06-23 2:52 ` Yafang Shao
2024-06-24 14:04 ` Petr Mladek
2024-06-25 2:16 ` Yafang Shao
2024-06-27 13:02 ` Miroslav Benes
2024-06-27 15:55 ` Yafang Shao
2024-06-28 8:20 ` Miroslav Benes
2024-06-21 2:26 ` Yafang Shao
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=Znl4u_dWfqK53G3k@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=laoar.shao@gmail.com \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).