linux-toolchains.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miroslav Benes <mbenes@suse.cz>
To: Song Liu <song@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,  linux-toolchains@vger.kernel.org,
	live-patching@vger.kernel.org,  indu.bhagat@oracle.com,
	puranjay@kernel.org, wnliu@google.com,  irogers@google.com,
	joe.lawrence@redhat.com, jpoimboe@kernel.org,
	 mark.rutland@arm.com, peterz@infradead.org,
	roman.gushchin@linux.dev,  rostedt@goodmis.org, will@kernel.org,
	kernel-team@meta.com,  Suraj Jitindar Singh <surajjs@amazon.com>,
	Torsten Duwe <duwe@suse.de>
Subject: Re: [PATCH 2/2] arm64: Implement HAVE_LIVEPATCH
Date: Wed, 12 Mar 2025 15:05:07 +0100 (CET)	[thread overview]
Message-ID: <alpine.LSU.2.21.2503121503340.12980@pobox.suse.cz> (raw)
In-Reply-To: <20250308012742.3208215-3-song@kernel.org>

Hi,

On Fri, 7 Mar 2025, Song Liu wrote:

> This is largely based on [1] by Suraj Jitindar Singh.
> 
> Test coverage:
> 
> - Passed manual tests with samples/livepatch.
> - Passed all but test-kprobe.sh in selftests/livepatch.
>   test-kprobe.sh is expected to fail, because arm64 doesn't have
>   KPROBES_ON_FTRACE.

Correct. The test should take into account and bail out.

> - Passed tests with kpatch-build [2]. (This version includes commits that
>   are not merged to upstream kpatch yet).
> 
> [1] https://lore.kernel.org/all/20210604235930.603-1-surajjs@amazon.com/
> [2] https://github.com/liu-song-6/kpatch/tree/fb-6.13
> Cc: Suraj Jitindar Singh <surajjs@amazon.com>
> Cc: Torsten Duwe <duwe@suse.de>
> Signed-off-by: Song Liu <song@kernel.org>

Acked-by: Miroslav Benes <mbenes@suse.cz>

Also as mentioned in the other thread, parts of this patch will go once 
arm64 is converted to generic entry infrastructure.

Thank you,
Miroslav

  reply	other threads:[~2025-03-12 14:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-08  1:27 [PATCH 0/2] arm64: livepatch: Enable livepatch without sframe Song Liu
2025-03-08  1:27 ` [PATCH 1/2] arm64: Implement arch_stack_walk_reliable Song Liu
2025-03-13 18:12   ` Breno Leitao
2025-03-13 19:10     ` Song Liu
2025-03-18 18:45   ` Josh Poimboeuf
2025-03-18 20:14     ` Song Liu
2025-03-18 23:00       ` Josh Poimboeuf
2025-03-18 23:38         ` Song Liu
2025-03-19  1:03           ` Josh Poimboeuf
2025-03-19  3:58             ` Song Liu
2025-03-19  5:39               ` Josh Poimboeuf
2025-03-19 18:37                 ` Weinan Liu
2025-03-19 19:09                   ` Song Liu
2025-03-08  1:27 ` [PATCH 2/2] arm64: Implement HAVE_LIVEPATCH Song Liu
2025-03-12 14:05   ` Miroslav Benes [this message]
2025-03-13 18:09   ` Breno Leitao

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=alpine.LSU.2.21.2503121503340.12980@pobox.suse.cz \
    --to=mbenes@suse.cz \
    --cc=duwe@suse.de \
    --cc=indu.bhagat@oracle.com \
    --cc=irogers@google.com \
    --cc=joe.lawrence@redhat.com \
    --cc=jpoimboe@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-toolchains@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=peterz@infradead.org \
    --cc=puranjay@kernel.org \
    --cc=roman.gushchin@linux.dev \
    --cc=rostedt@goodmis.org \
    --cc=song@kernel.org \
    --cc=surajjs@amazon.com \
    --cc=will@kernel.org \
    --cc=wnliu@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;
as well as URLs for NNTP newsgroup(s).