All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nam Cao <namcao@linutronix.de>
To: Xiaofeng Yuan <xiaofengmian@163.com>
Cc: charlie@rivosinc.com, linux-riscv@lists.infradead.org
Subject: Re: [PATCH] riscv: kprobes: Add test case for c.jal instruction simulation
Date: Sat, 27 Jun 2026 15:25:21 +0200	[thread overview]
Message-ID: <87cxxcazem.fsf@yellow.woof> (raw)
In-Reply-To: <6A3FC8FF.1BF932.00001@m16.mail.163.com>

Xiaofeng Yuan <xiaofengmian@163.com> writes:
> Thanks for the test case. Since c.jal is RV32-only, I haven't been able
> to run it on real hardware. I tried running the full kprobes KUNIT test
> suite under QEMU riscv32, but the test appears to hang before
> completing -- even without the c.jal test case included.

That is not supposed to happen.

> I suspect this may be a QEMU emulation speed issue or a pre-existing
> limitation of the test framework in an emulated environment.
>
> Did you run this test on real hardware or in QEMU? If QEMU, any tips
> on how to get it to complete?

I mostly run on QEMU, but I did run on real hardware a few times. I
never observed a problem.

If you want me to look into it, please share your qemu command and
kernel config file.

Nam

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

      reply	other threads:[~2026-06-27 13:25 UTC|newest]

Thread overview: 4+ 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 [this message]

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=87cxxcazem.fsf@yellow.woof \
    --to=namcao@linutronix.de \
    --cc=charlie@rivosinc.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=xiaofengmian@163.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.