All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Kaiser <martin@kaiser.cx>
To: Shuai Xue <xueshuai@linux.alibaba.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <pjw@kernel.org>,
	aou@eecs.berkeley.edu, alex@ghiti.fr,
	linux-riscv@lists.infradead.org, oleg@redhat.com,
	rostedt@goodmis.org, mhiramat@kernel.org, mark.rutland@arm.com,
	peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
	namhyung@kernel.org, alexander.shishkin@linux.intel.com,
	jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
	james.clark@linaro.org, jpoimboe@kernel.org, jikos@kernel.org,
	mbenes@suse.cz, pmladek@suse.com, joe.lawrence@redhat.com,
	shuah@kernel.org, mpdesouza@suse.com,
	oliver.yang@linux.alibaba.com, zhuo.song@linux.alibaba.com,
	jkchen@linux.alibaba.com, linux-kernel@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, live-patching@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v6 0/7] riscv: Add reliable stack unwinding for livepatch
Date: Mon, 12 Oct 2026 10:44:56 +0200	[thread overview]
Message-ID: <asyeCD1xaIuKv3nl@akranes.kaiser.cx> (raw)
In-Reply-To: <fbdb7b4c-0f80-41b0-b6d8-a4501ff3e820@linux.alibaba.com>

Hi Shuai,

Thus wrote Shuai Xue (xueshuai@linux.alibaba.com):

> It is great to hear that livepatch works both on a standard rv64 QEMU
> and on the rv64 CHERI system. Could you share what the minor tweaks
> for CHERI were? If any of them are generic -- for example frame-record
> size/alignment or pointer-width assumptions in the unwinder -- it may
> be worth folding them into this series, so the cheri-linux tree has
> less to carry downstream. If they are purely CHERI-specific, a pointer
> to your tree would still be a useful reference.

the cheri changes are simple fixups of data types and assembly instructions.
This isn't something that can be upstreamed at this point.

Eventually, it'll end up in the cheri linux tree at
https://github.com/CHERI-Alliance/linux
but there's more cleanup to do first.

I just wanted to show my interest in getting your patches merged.

Thanks,
Martin

> +Palmer, Paul, gentle ping on this series.

> It has been under review since late May (v1 on May 27, now in its sixth
> revision) and the tags collected so far are:

>   * Acked-by: Miroslav Benes <mbenes@suse.cz>             (7/7, livepatch)
>   * Reviewed-by: Marcos Paulo de Souza <mpdesouza@suse.com> (7/7)
>   * Reviewed-by: Martin Kaiser <martin@kaiser.cx>         (whole series)
>   * Tested-by: Martin Kaiser <martin@kaiser.cx>           (whole series,
>     rv64 QEMU and rv64 CHERI, livepatch working on both)
>   * Reviewed-by: Shuai Xue <xueshuai@linux.alibaba.com>   (2/7, 3/7, 4/7, 6/7)

> v6 still applies cleanly onto the current riscv/for-next
> (52318cf0fa6e). If it helps, I can send a v7 that folds in Martin's
> Reviewed-by/Tested-by tags.

> Could the series be considered for the upcoming 7.4 merge window?

> Thanks,
> Shuai Xue



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Martin Kaiser <martin@kaiser.cx>
To: Shuai Xue <xueshuai@linux.alibaba.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <pjw@kernel.org>,
	aou@eecs.berkeley.edu, alex@ghiti.fr,
	linux-riscv@lists.infradead.org, oleg@redhat.com,
	rostedt@goodmis.org, mhiramat@kernel.org, mark.rutland@arm.com,
	peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
	namhyung@kernel.org, alexander.shishkin@linux.intel.com,
	jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
	james.clark@linaro.org, jpoimboe@kernel.org, jikos@kernel.org,
	mbenes@suse.cz, pmladek@suse.com, joe.lawrence@redhat.com,
	shuah@kernel.org, mpdesouza@suse.com,
	oliver.yang@linux.alibaba.com, zhuo.song@linux.alibaba.com,
	jkchen@linux.alibaba.com, linux-kernel@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, live-patching@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v6 0/7] riscv: Add reliable stack unwinding for livepatch
Date: Mon, 12 Oct 2026 10:44:56 +0200	[thread overview]
Message-ID: <asyeCD1xaIuKv3nl@akranes.kaiser.cx> (raw)
In-Reply-To: <fbdb7b4c-0f80-41b0-b6d8-a4501ff3e820@linux.alibaba.com>

Hi Shuai,

Thus wrote Shuai Xue (xueshuai@linux.alibaba.com):

> It is great to hear that livepatch works both on a standard rv64 QEMU
> and on the rv64 CHERI system. Could you share what the minor tweaks
> for CHERI were? If any of them are generic -- for example frame-record
> size/alignment or pointer-width assumptions in the unwinder -- it may
> be worth folding them into this series, so the cheri-linux tree has
> less to carry downstream. If they are purely CHERI-specific, a pointer
> to your tree would still be a useful reference.

the cheri changes are simple fixups of data types and assembly instructions.
This isn't something that can be upstreamed at this point.

Eventually, it'll end up in the cheri linux tree at
https://github.com/CHERI-Alliance/linux
but there's more cleanup to do first.

I just wanted to show my interest in getting your patches merged.

Thanks,
Martin

> +Palmer, Paul, gentle ping on this series.

> It has been under review since late May (v1 on May 27, now in its sixth
> revision) and the tags collected so far are:

>   * Acked-by: Miroslav Benes <mbenes@suse.cz>             (7/7, livepatch)
>   * Reviewed-by: Marcos Paulo de Souza <mpdesouza@suse.com> (7/7)
>   * Reviewed-by: Martin Kaiser <martin@kaiser.cx>         (whole series)
>   * Tested-by: Martin Kaiser <martin@kaiser.cx>           (whole series,
>     rv64 QEMU and rv64 CHERI, livepatch working on both)
>   * Reviewed-by: Shuai Xue <xueshuai@linux.alibaba.com>   (2/7, 3/7, 4/7, 6/7)

> v6 still applies cleanly onto the current riscv/for-next
> (52318cf0fa6e). If it helps, I can send a v7 that folds in Martin's
> Reviewed-by/Tested-by tags.

> Could the series be considered for the upcoming 7.4 merge window?

> Thanks,
> Shuai Xue



  reply	other threads:[~2026-10-12  8:45 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14  9:26 [PATCH v6 0/7] riscv: Add reliable stack unwinding for livepatch Shuai Xue
2026-09-14  9:26 ` Shuai Xue
2026-09-14  9:26 ` [PATCH v6 1/7] riscv: stacktrace: Add frame record metadata Shuai Xue
2026-09-14  9:26   ` Shuai Xue
2026-09-14  9:40   ` sashiko-bot
2026-09-14  9:26 ` [PATCH v6 2/7] riscv: stacktrace: disable KASAN and KCOV instrumentation for stacktrace.o Shuai Xue
2026-09-14  9:26   ` Shuai Xue
2026-09-14  9:32   ` sashiko-bot
2026-09-14  9:26 ` [PATCH v6 3/7] riscv: ftrace: always preserve s0 in dynamic ftrace register frame Shuai Xue
2026-09-14  9:26   ` Shuai Xue
2026-09-14  9:32   ` sashiko-bot
2026-09-14  9:26 ` [PATCH v6 4/7] riscv: stacktrace: introduce stack-bound tracking helpers Shuai Xue
2026-09-14  9:26   ` Shuai Xue
2026-09-14  9:33   ` sashiko-bot
2026-09-14  9:26 ` [PATCH v6 5/7] riscv: stacktrace: switch to frame-pointer based unwinder Shuai Xue
2026-09-14  9:26   ` Shuai Xue
2026-09-14  9:39   ` sashiko-bot
2026-10-09 18:59   ` Karl Mehltretter
2026-10-09 18:59     ` Karl Mehltretter
2026-10-10  3:38     ` Shuai Xue
2026-10-10  3:38       ` Shuai Xue
2026-10-13 20:18   ` Martin Kaiser
2026-10-13 20:18     ` Martin Kaiser
2026-09-14  9:26 ` [PATCH v6 6/7] riscv: Kconfig: enable HAVE_RELIABLE_STACKTRACE and HAVE_LIVEPATCH Shuai Xue
2026-09-14  9:26   ` Shuai Xue
2026-09-14  9:38   ` sashiko-bot
2026-09-14  9:26 ` [PATCH v6 7/7] selftests/livepatch: Add RISC-V syscall wrapper prefix Shuai Xue
2026-09-14  9:26   ` Shuai Xue
2026-09-14  9:38   ` sashiko-bot
2026-09-29  7:28 ` [PATCH v6 0/7] riscv: Add reliable stack unwinding for livepatch Martin Kaiser
2026-09-29  7:28   ` Martin Kaiser
2026-10-08 11:42   ` Shuai Xue
2026-10-08 11:42     ` Shuai Xue
2026-10-12  8:44     ` Martin Kaiser [this message]
2026-10-12  8:44       ` Martin Kaiser

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=asyeCD1xaIuKv3nl@akranes.kaiser.cx \
    --to=martin@kaiser.cx \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alex@ghiti.fr \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jikos@kernel.org \
    --cc=jkchen@linux.alibaba.com \
    --cc=joe.lawrence@redhat.com \
    --cc=jolsa@kernel.org \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mbenes@suse.cz \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=mpdesouza@suse.com \
    --cc=namhyung@kernel.org \
    --cc=oleg@redhat.com \
    --cc=oliver.yang@linux.alibaba.com \
    --cc=palmer@dabbelt.com \
    --cc=peterz@infradead.org \
    --cc=pjw@kernel.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=shuah@kernel.org \
    --cc=xueshuai@linux.alibaba.com \
    --cc=zhuo.song@linux.alibaba.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 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.