All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Justus Bergermann" <mail@justus-bergermann.de>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf vendor events riscv: Add PMU events JSON file for T-Head C908
Date: Mon, 05 Oct 2026 16:19:40 +0000	[thread overview]
Message-ID: <20261005161940.8124F1F0089A@smtp.kernel.org> (raw)
In-Reply-To: <20261005-c908-pmu-events-v1-1-cfab33201c59@justus-bergermann.de>

> The XuanTie C908 cannot use the existing thead/c900-legacy event file:
> The c900-legacy mapfile entry is 0x5b7-0x0-0x0, which works because the
> c906 and c910 leave marchid and mimpid unimplemented, so both read
> as zero. The C908 implements them: a Kendryte K230 with the c908 reports
> mvendorid 0x5b7, marchid 0x8000000009140d00 and mimpid 0x50000. No entry
> matches, so perf currently resolves no vendor event names at all on this
> core.
> 
> Add a thead/c908 directory describing the 165 raw events defined in
> Table 14.6 of the XuanTie C908 user manual, codes 0x01 to 0xb4, and a
> mapfile entry for the core.
> 
> Signed-off-by: Justus Bergermann <mail@justus-bergermann.de>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261005-c908-pmu-events-v1-1-cfab33201c59@justus-bergermann.de?part=1


      reply	other threads:[~2026-10-05 16:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 16:15 [PATCH] perf vendor events riscv: Add PMU events JSON file for T-Head C908 Justus Bergermann
2026-10-05 16:15 ` Justus Bergermann
2026-10-05 16:19 ` sashiko-bot [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=20261005161940.8124F1F0089A@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mail@justus-bergermann.de \
    --cc=sashiko-reviews@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 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.