All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiaofeng Yuan <xiaofengmian@163.com>
To: Nam Cao <namcao@linutronix.de>
Cc: Charlie Jenkins <thecharlesjenkins@gmail.com>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	Xiaofeng Yuan <xiaofengmian@163.com>
Subject: Re: [PATCH] riscv: kprobes: Add test case for c.jal instruction simulation
Date: Wed, 01 Jul 2026 10:46:31 +0000	[thread overview]
Message-ID: <6A44F009.1BDCEE.00001@m16.mail.163.com> (raw)
In-Reply-To: <20260627115051.3235783-1-namcao@linutronix.de>

Hi Nam,

Thanks again for the test case — it has been included in the v6 c.jal
series, credited to you.

Regarding the QEMU hang I asked you about earlier: I found the root
cause.  The hang was not a QEMU issue — it was caused by
EXECMEM_KPROBES allocating read-only pages without writable
permissions when CONFIG_STRICT_MODULE_RWX is not enabled (as happens
with an allnoconfig-derived config).  This affects both RV32 and RV64.

I have submitted a separate fix series titled "riscv: fix kprobes on
minimal kernel configs" to address this.

Best regards,
Xiaofeng
_______________________________________________
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: Xiaofeng Yuan <xiaofengmian@163.com>
To: Nam Cao <namcao@linutronix.de>
Cc: Charlie Jenkins <thecharlesjenkins@gmail.com>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	Xiaofeng Yuan <xiaofengmian@163.com>
Subject: Re: [PATCH] riscv: kprobes: Add test case for c.jal instruction simulation
Date: Wed, 01 Jul 2026 10:46:31 +0000	[thread overview]
Message-ID: <6A44F009.1BDCEE.00001@m16.mail.163.com> (raw)
In-Reply-To: <20260627115051.3235783-1-namcao@linutronix.de>

Hi Nam,

Thanks again for the test case — it has been included in the v6 c.jal
series, credited to you.

Regarding the QEMU hang I asked you about earlier: I found the root
cause.  The hang was not a QEMU issue — it was caused by
EXECMEM_KPROBES allocating read-only pages without writable
permissions when CONFIG_STRICT_MODULE_RWX is not enabled (as happens
with an allnoconfig-derived config).  This affects both RV32 and RV64.

I have submitted a separate fix series titled "riscv: fix kprobes on
minimal kernel configs" to address this.

Best regards,
Xiaofeng

  parent reply	other threads:[~2026-07-01 10:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-27 11:50 [PATCH] riscv: kprobes: Add test case for c.jal instruction simulation Nam Cao
2026-06-27 11:50 ` Nam Cao
2026-06-27 12:58 ` Xiaofeng Yuan
2026-06-27 13:25   ` Nam Cao
2026-07-01 10:46 ` Xiaofeng Yuan [this message]
2026-07-01 10:46   ` Xiaofeng Yuan
2026-07-10 18:40 ` patchwork-bot+linux-riscv
2026-07-10 18:40   ` 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=6A44F009.1BDCEE.00001@m16.mail.163.com \
    --to=xiaofengmian@163.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=namcao@linutronix.de \
    --cc=thecharlesjenkins@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 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.