All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Pu Lehui <pulehui@huaweicloud.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	palmer@dabbelt.com, alex@ghiti.fr, pulehui@huawei.com
Subject: Re: [PATCH -next] riscv: Enable ARCH_HAVE_NMI_SAFE_CMPXCHG
Date: Wed, 06 Aug 2025 17:15:59 +0000	[thread overview]
Message-ID: <175450055949.2863135.12380729156820044095.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250711090443.1688404-1-pulehui@huaweicloud.com>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Alexandre Ghiti <alexghiti@rivosinc.com>:

On Fri, 11 Jul 2025 09:04:43 +0000 you wrote:
> From: Pu Lehui <pulehui@huawei.com>
> 
> The implement of cmpxchg() in riscv is based on atomic primitives and
> has NMI-safe features, so it can be used safely in the in_nmi context.
> ftrace's ringbuffer relies on NMI-safe cmpxchg() in the NMI context.
> Currently, in_nmi() is true when riscv kprobe is in trap-based mode, so
> this config needs to be selected, otherwise kprobetrace will not be
> available.
> 
> [...]

Here is the summary with links:
  - [-next] riscv: Enable ARCH_HAVE_NMI_SAFE_CMPXCHG
    https://git.kernel.org/riscv/c/9ad032ba418c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
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: patchwork-bot+linux-riscv@kernel.org
To: Pu Lehui <pulehui@huaweicloud.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	palmer@dabbelt.com, alex@ghiti.fr, pulehui@huawei.com
Subject: Re: [PATCH -next] riscv: Enable ARCH_HAVE_NMI_SAFE_CMPXCHG
Date: Wed, 06 Aug 2025 17:15:59 +0000	[thread overview]
Message-ID: <175450055949.2863135.12380729156820044095.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250711090443.1688404-1-pulehui@huaweicloud.com>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Alexandre Ghiti <alexghiti@rivosinc.com>:

On Fri, 11 Jul 2025 09:04:43 +0000 you wrote:
> From: Pu Lehui <pulehui@huawei.com>
> 
> The implement of cmpxchg() in riscv is based on atomic primitives and
> has NMI-safe features, so it can be used safely in the in_nmi context.
> ftrace's ringbuffer relies on NMI-safe cmpxchg() in the NMI context.
> Currently, in_nmi() is true when riscv kprobe is in trap-based mode, so
> this config needs to be selected, otherwise kprobetrace will not be
> available.
> 
> [...]

Here is the summary with links:
  - [-next] riscv: Enable ARCH_HAVE_NMI_SAFE_CMPXCHG
    https://git.kernel.org/riscv/c/9ad032ba418c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2025-08-06 17:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11  9:04 [PATCH -next] riscv: Enable ARCH_HAVE_NMI_SAFE_CMPXCHG Pu Lehui
2025-07-11  9:04 ` Pu Lehui
2025-07-17  2:00 ` Pu Lehui
2025-07-17  2:00   ` Pu Lehui
2025-07-17  7:38 ` Alexandre Ghiti
2025-07-17  7:38   ` Alexandre Ghiti
2025-08-06 17:15 ` patchwork-bot+linux-riscv [this message]
2025-08-06 17:15   ` patchwork-bot+linux-riscv

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=175450055949.2863135.12380729156820044095.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pulehui@huawei.com \
    --cc=pulehui@huaweicloud.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.