From: Inochi Amaoto <inochiama@outlook.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Nikita Shubin <n.shubin@yadro.com>,
Inochi Amaoto <inochiama@outlook.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH V3] perf vendor events riscv: add T-HEAD C9xx JSON file
Date: Thu, 18 May 2023 17:48:27 +0800 [thread overview]
Message-ID: <IA1PR20MB4953FCC20C89F2659EB34896BB7F9@IA1PR20MB4953.namprd20.prod.outlook.com> (raw)
In-Reply-To: <36fcef74ba3d21250f4c9605e691d1e2dac20ebb.camel@maquefel.me>
> licheerv # perf record
> [ 432.015618] watchdog: BUG: soft lockup - CPU#0 stuck for 26s!
> [perf:117]
> [ 460.015617] watchdog: BUG: soft lockup - CPU#0 stuck for 52s!
> [perf:117]
> [ 488.015616] watchdog: BUG: soft lockup - CPU#0 stuck for 78s!
> [perf:117]
> [ 516.015617] watchdog: BUG: soft lockup - CPU#0 stuck for 104s!
> [perf:117]
>
> But that's not related to your patch anyway.
Same issue on c920, but it did not always occur.
Like a sbi issue for T-HEAD cpus.
> I am strongly against using "c9xx" wildcard, i would prefer declaring
> them separate (especially taking in mind that c920 is c910 with vector
> - AFAIK), but that's up to Arnaldo to decide.
AFAIK, there is no reliable way to distinguish c906 and c910 cores. And
the events of c910 and c920 are the same (according to the draft document
of the c920).
Anyway, I agree to let Arnaldo decide.
> Tested-by: Nikita Shubin <n.shubin@yadro.com>
Thanks.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-05-18 9:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 7:12 [PATCH V3] perf vendor events riscv: add T-HEAD C9xx JSON file Inochi Amaoto
2023-05-18 12:09 ` Nikita Shubin
2023-05-18 9:48 ` Inochi Amaoto [this message]
2023-06-24 0:17 ` Namhyung Kim
2023-06-24 1:32 ` Inochi Amaoto
2023-06-24 4:35 ` Namhyung Kim
2023-06-24 6:42 ` Inochi Amaoto
2023-06-24 8:54 ` Conor Dooley
2023-06-26 23:14 ` Namhyung Kim
2023-06-27 8:40 ` Atish Patra
2023-06-27 11:51 ` Nikita Shubin
2023-06-22 0:11 ` Palmer Dabbelt
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=IA1PR20MB4953FCC20C89F2659EB34896BB7F9@IA1PR20MB4953.namprd20.prod.outlook.com \
--to=inochiama@outlook.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=n.shubin@yadro.com \
--cc=namhyung@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).