mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: loongarch@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] Enable some configs in loongson3_defconfig
Date: Fri, 9 May 2025 23:09:21 +0800	[thread overview]
Message-ID: <fccef9c4-da67-c232-7d61-07f2c6cabbd0@loongson.cn> (raw)
In-Reply-To: <CAAhV-H5yvrfd0aH=AuFwYQzFcnQAMBekO0frvwhThaPKx6p1RQ@mail.gmail.com>

On 5/7/25 12:24, Huacai Chen wrote:
...

> Have you tried (both OpenSSL)
> 
> sudo ./perf probe -x /usr/lib64/libcrypto.so BN_mod_mul_montgomery
> sudo ./perf stat -e probe_libcrypto:BN_mod_mul_montgomery openssl speed sm2
> 
> or (both Tongsuo)
> 
> sudo ./perf probe -x /opt/tongsuo/lib/libcrypto.so BN_mod_mul_montgomery
> sudo ./perf stat -e probe_libcrypto:BN_mod_mul_montgomery
> /opt/tongsuo/bin/openssl speed sm2
> 
> and still success?
> 
> I tried, and both got a SIGTRAP or system hang.

I can reproduce it now and have a draft patch to fix it.

I am busy with some emergency stuff recently and will send
the formal patch as soon as I have some free time to make
a proper commit message.

Thanks,
Tiezhu


      reply	other threads:[~2025-05-09 15:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-30 13:15 Tiezhu Yang
2025-04-30 13:15 ` [PATCH 1/5] LoongArch: Clean up loongson3_defconfig Tiezhu Yang
2025-04-30 13:15 ` [PATCH 2/5] LoongArch: Enable tracing infrastructure in defconfig Tiezhu Yang
2025-04-30 13:15 ` [PATCH 3/5] LoongArch: Enable tracing syscalls " Tiezhu Yang
2025-04-30 13:15 ` [PATCH 4/5] LoongArch: Enable debug information " Tiezhu Yang
2025-04-30 13:15 ` [PATCH 5/5] LoongArch: Enable kprobe and ftrace " Tiezhu Yang
2025-04-30 13:41 ` [PATCH 0/5] Enable some configs in loongson3_defconfig Huacai Chen
2025-05-01  1:37   ` Vincent Li
2025-05-01  3:19     ` Huacai Chen
2025-05-07  4:24   ` Huacai Chen
2025-05-09 15:09     ` Tiezhu Yang [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=fccef9c4-da67-c232-7d61-07f2c6cabbd0@loongson.cn \
    --to=yangtiezhu@loongson.cn \
    --cc=chenhuacai@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®