From: Sebastian Alba Vives <sebasjosue84@gmail.com>
To: opensbi@lists.infradead.org
Cc: anup.patel@oss.qualcomm.com, pengpeng@iscas.ac.cn,
hppiscas@163.com, Sebastian Alba Vives <sebasjosue84@gmail.com>
Subject: [PATCH v2 0/2] lib: sbi_pmu: propagate hardware counter errors
Date: Sun, 25 Oct 2026 08:53:36 -0600 [thread overview]
Message-ID: <20261025145338.2569358-1-sebasjosue84@gmail.com> (raw)
The two patches Anup asked for in the thread for Pengpeng Hou's
SKIP_MATCH class check. v1 is at
https://lore.kernel.org/r/20261025062836.2445655-1-sebasjosue84@gmail.com
Changes in v2:
- patch 1: propagate SBI_EALREADY_STARTED as well, per Anup's review.
An already running counter may have been configured for a different
event previously, so the configure must not report success. The
commit message was reworked around that and the special case is gone.
- patch 2: unchanged except for the context line that patch 1 touches.
Picked up Anup's Reviewed-by.
They stay a series because both touch the same if block in
sbi_pmu_ctr_cfg_match() and the second does not apply without the first.
Built clean for rv64 and rv32, PLATFORM=generic, no new warnings.
Sebastian Alba Vives (2):
lib: sbi_pmu: do not ignore pmu_ctr_start_hw() error in cfg_match
lib: sbi_pmu: reject out-of-bounds counter index in pmu_ctr_write_hw()
lib/sbi/sbi_pmu.c | 22 +++++++++++++++++-----
1 file changed, 17 insertions(+), 5 deletions(-)
--
2.43.0
--
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
next reply other threads:[~2026-10-25 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 14:53 Sebastian Alba Vives [this message]
2026-10-25 14:53 ` [PATCH v2 1/2] lib: sbi_pmu: do not ignore pmu_ctr_start_hw() error in cfg_match Sebastian Alba Vives
2026-10-25 14:53 ` [PATCH v2 2/2] lib: sbi_pmu: reject out-of-bounds counter index in pmu_ctr_write_hw() Sebastian Alba Vives
2026-10-29 8:23 ` [PATCH v2 0/2] lib: sbi_pmu: propagate hardware counter errors Anup Patel
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=20261025145338.2569358-1-sebasjosue84@gmail.com \
--to=sebasjosue84@gmail.com \
--cc=anup.patel@oss.qualcomm.com \
--cc=hppiscas@163.com \
--cc=opensbi@lists.infradead.org \
--cc=pengpeng@iscas.ac.cn \
/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