From: Petr Mladek <pmladek@suse.com>
To: zhang warden <zhangwarden@gmail.com>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
Marcos Paulo de Souza <mpdesouza@suse.com>,
Miroslav Benes <mbenes@suse.cz>, Jiri Kosina <jikos@kernel.org>,
Joe Lawrence <joe.lawrence@redhat.com>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] selftests: livepatch: add test cases of stack_order sysfs interface
Date: Fri, 11 Oct 2024 10:36:14 +0200 [thread overview]
Message-ID: <Zwjjfpb0hSSE2Ap4@pathway.suse.cz> (raw)
In-Reply-To: <CDB9AA87-5034-40BB-891B-CC846D7EEBDA@gmail.com>
On Fri 2024-10-11 09:51:07, zhang warden wrote:
>
>
> > On Oct 10, 2024, at 23:51, Josh Poimboeuf <jpoimboe@kernel.org> wrote:
> >
> > Maybe add a replace=[true|false] module parameter.
> >
>
> How to do it?
> Isn't the way we build modules using make?
> How to set this replace value?
You could find inspiration in
tools/testing/selftests/livepatch/test-livepatch.sh, see
load_lp $MOD_REPLACE replace=0
vs.
load_lp $MOD_REPLACE replace=1
You could more or less copy the "multiple livepatches" and
"atomic replace livepatch" self-tests. The new tests
would check the "stack_order" sysfs value instread of checking
whether /proc/cmdline and /proc/meminfo are livepatched.
Best Regards,
Petr
prev parent reply other threads:[~2024-10-11 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 7:52 [PATCH 0/1] selftests: livepatch: add test cases of stack_order sysfs Wardenjohn
2024-10-08 7:52 ` [PATCH 1/1] selftests: livepatch: add test cases of stack_order sysfs interface Wardenjohn
2024-10-10 12:31 ` Marcos Paulo de Souza
2024-10-10 15:11 ` zhang warden
2024-10-10 15:51 ` Josh Poimboeuf
2024-10-11 1:51 ` zhang warden
2024-10-11 4:09 ` Josh Poimboeuf
2024-10-11 8:36 ` Petr Mladek [this message]
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=Zwjjfpb0hSSE2Ap4@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mpdesouza@suse.com \
--cc=zhangwarden@gmail.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;
as well as URLs for NNTP newsgroup(s).