Re: [PATCH v13 00/12] RV: Linear temporal logic monitors for RT application

2025-08-10 Thread patchwork-bot+linux-riscv
Hello: This patch was applied to riscv/linux.git (fixes) by Steven Rostedt (Google) : On Wed, 9 Jul 2025 21:21:11 +0200 you wrote: > Real-time applications may have design flaws causing them to have > unexpected latency. For example, the applications may raise page faults, or > may be blocked tr

Re: [PATCH v8 00/22] RV: Linear temporal logic monitors for RT application

2025-08-10 Thread patchwork-bot+linux-riscv
Hello: This patch was applied to riscv/linux.git (fixes) by Steven Rostedt (Google) : On Mon, 12 May 2025 12:50:43 +0200 you wrote: > Real-time applications may have design flaws causing them to have > unexpected latency. For example, the applications may raise page faults, or > may be blocked tr

Re: [PATCH v12 00/12] RV: Linear temporal logic monitors for RT application

2025-08-10 Thread patchwork-bot+linux-riscv
Hello: This patch was applied to riscv/linux.git (fixes) by Steven Rostedt (Google) : On Wed, 9 Jul 2025 19:56:17 +0200 you wrote: > Real-time applications may have design flaws causing them to have > unexpected latency. For example, the applications may raise page faults, or > may be blocked tr

Re: [PATCH v11 00/21] RV: Linear temporal logic monitors for RT application

2025-08-10 Thread patchwork-bot+linux-riscv
Hello: This patch was applied to riscv/linux.git (fixes) by Steven Rostedt (Google) : On Fri, 4 Jul 2025 15:19:52 +0200 you wrote: > Real-time applications may have design flaws causing them to have > unexpected latency. For example, the applications may raise page faults, or > may be blocked tr

Re: [PATCH v7 00/22] RV: Linear temporal logic monitors for RT application

2025-08-10 Thread patchwork-bot+linux-riscv
Hello: This patch was applied to riscv/linux.git (fixes) by Steven Rostedt (Google) : On Fri, 9 May 2025 10:11:59 +0200 you wrote: > Real-time applications may have design flaws causing them to have > unexpected latency. For example, the applications may raise page faults, or > may be blocked tr

Re: [PATCH v6 00/22] RV: Linear temporal logic monitors for RT application

2025-08-10 Thread patchwork-bot+linux-riscv
Hello: This patch was applied to riscv/linux.git (fixes) by Steven Rostedt (Google) : On Wed, 30 Apr 2025 13:02:15 +0200 you wrote: > Real-time applications may have design flaws causing them to have > unexpected latency. For example, the applications may raise page faults, or > may be blocked tr

Re: [PATCH v5 00/23] RV: Linear temporal logic monitors for RT application

2025-08-10 Thread patchwork-bot+linux-riscv
Hello: This patch was applied to riscv/linux.git (fixes) by Steven Rostedt (Google) : On Tue, 29 Apr 2025 14:00:45 +0200 you wrote: > Real-time applications may have design flaws causing them to have > unexpected latency. For example, the applications may raise page faults, or > may be blocked tr

Re: [PATCH v4 00/22] RV: Linear temporal logic monitors for RT application

2025-08-10 Thread patchwork-bot+linux-riscv
Hello: This patch was applied to riscv/linux.git (fixes) by Steven Rostedt (Google) : On Wed, 23 Apr 2025 08:49:55 +0200 you wrote: > Real-time applications may have design flaws causing them to have > unexpected latency. For example, the applications may raise page faults, or > may be blocked tr

Re: [PATCH v3 00/22] RV: Linear temporal logic monitors for RT application

2025-08-10 Thread patchwork-bot+linux-riscv
Hello: This patch was applied to riscv/linux.git (fixes) by Steven Rostedt (Google) : On Wed, 16 Apr 2025 08:51:06 +0200 you wrote: > Real-time applications may have design flaws causing them to have > unexpected latency. For example, the applications may raise page faults, or > may be blocked tr

Re: [PATCH v2] riscv: ftrace: Properly acquire text_mutex to fix a race condition

2025-07-16 Thread patchwork-bot+linux-riscv
Hello: This patch was applied to riscv/linux.git (fixes) by Palmer Dabbelt : On Fri, 11 Jul 2025 07:38:38 + you wrote: > As reported by lockdep, some patching was done without acquiring > text_mutex, so there could be a race when mapping the page to patch > since we use the same fixmap entry.

Re: [PATCH v4 01/12] riscv: ftrace: support fastcc in Clang for WITH_ARGS

2025-06-02 Thread patchwork-bot+linux-riscv
Hello: This series was applied to riscv/linux.git (for-next) by Alexandre Ghiti : On Tue, 8 Apr 2025 02:08:25 +0800 you wrote: > From: Andy Chiu > > Some caller-saved registers which are not defined as function arguments > in the ABI can still be passed as arguments when the kernel is compiled

Re: [PATCH fixes v2 1/2] riscv: Replace function-like macro by static inline function

2025-04-24 Thread patchwork-bot+linux-riscv
Hello: This series was applied to riscv/linux.git (fixes) by Palmer Dabbelt : On Sat, 19 Apr 2025 13:13:59 +0200 you wrote: > From: Björn Töpel > > The flush_icache_range() function is implemented as a "function-like > macro with unused parameters", which can result in "unused variables" > warn

Re: [PATCH] riscv: ftrace: Add parentheses in macro definitions of make_call_t0 and make_call_ra

2025-03-26 Thread patchwork-bot+linux-riscv
Hello: This patch was applied to riscv/linux.git (for-next) by Alexandre Ghiti : On Thu, 6 Feb 2025 13:28:36 -0600 you wrote: > This patch adds parentheses to parameters caller and callee of macros > make_call_t0 and make_call_ra. Every existing invocation of these two > macros uses a single var

Re: [PATCH] riscv: tracing: Fix __write_overflow_field in ftrace_partial_regs()

2025-03-26 Thread patchwork-bot+linux-riscv
Hello: This patch was applied to riscv/linux.git (for-next) by Alexandre Ghiti : On Mon, 24 Feb 2025 18:42:21 -0800 you wrote: > The size of ®s->a0 is unknown, causing the error: > > ../include/linux/fortify-string.h:571:25: warning: call to > '__write_overflow_field' declared with attribute war

Re: [PATCH v10 0/2] riscv: Add runtime constant support

2025-03-26 Thread patchwork-bot+linux-riscv
Hello: This series was applied to riscv/linux.git (for-next) by Alexandre Ghiti : On Wed, 19 Mar 2025 11:35:18 -0700 you wrote: > Ard brought this to my attention in this patch [1]. > > I benchmarked this patch on the Nezha D1 (which does not contain Zba or > Zbkb so it uses the default algorith

Re: [PATCH v2 0/2] ftrace: Make ftrace_regs abstract and consolidate code

2024-12-11 Thread patchwork-bot+linux-riscv
Hello: This series was applied to riscv/linux.git (fixes) by Steven Rostedt (Google) : On Tue, 08 Oct 2024 19:05:27 -0400 you wrote: > This is based on: > > https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git/ > ftrace/for-next > > ftrace_regs was created to hold regist

Re: [PATCH v3] ftrace: Consolidate ftrace_regs accessor functions for archs using pt_regs

2024-12-11 Thread patchwork-bot+linux-riscv
Hello: This patch was applied to riscv/linux.git (fixes) by Steven Rostedt (Google) : On Thu, 10 Oct 2024 20:21:14 -0400 you wrote: > From: Steven Rostedt > > Most architectures use pt_regs within ftrace_regs making a lot of the > accessor functions just calls to the pt_regs internally. Instead

Re: [PATCH v2 3/3] riscv: add PREEMPT_LAZY support

2024-12-11 Thread patchwork-bot+linux-riscv
Hello: This patch was applied to riscv/linux.git (fixes) by Peter Zijlstra : On Mon, 21 Oct 2024 17:08:42 +0200 you wrote: > From: Jisheng Zhang > > riscv has switched to GENERIC_ENTRY, so adding PREEMPT_LAZY is as simple > as adding TIF_NEED_RESCHED_LAZY related definitions and enabling > ARCH

Re: [PATCH v2 3/3] riscv: add PREEMPT_LAZY support

2024-12-11 Thread patchwork-bot+linux-riscv
Hello: This patch was applied to riscv/linux.git (fixes) by Peter Zijlstra : On Thu, 10 Oct 2024 14:25:45 +0200 you wrote: > From: Jisheng Zhang > > riscv has switched to GENERIC_ENTRY, so adding PREEMPT_LAZY is as simple > as adding TIF_NEED_RESCHED_LAZY related definitions and enabling > ARCH

Re: [PATCH v12 0/5] Tracepoints and static branch in Rust

2024-12-11 Thread patchwork-bot+linux-riscv
Hello: This series was applied to riscv/linux.git (fixes) by Steven Rostedt (Google) : On Wed, 30 Oct 2024 16:04:23 + you wrote: > An important part of a production ready Linux kernel driver is > tracepoints. So to write production ready Linux kernel drivers in Rust, > we must be able to call