From: linuxtestproject.agent@gmail.com
To: Piotr Kubaj <piotr.kubaj@intel.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] pmc_core: add test for pkgc_blocker_residency_show
Date: Tue, 11 Aug 2026 17:10:05 +0000 [thread overview]
Message-ID: <20260811171005.9063-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260811162856.67654-2-piotr.kubaj@intel.com>
Hi Piotr,
On August 11, 2026, Piotr Kubaj wrote:
> pmc_core: add test for pkgc_blocker_residency_show
> /*
> * Interval between the two samples. The PMT telemetry region behind these
> * counters refreshes at roughly 1s granularity: measured on Nova Lake, no
> * counter moved over 200ms or 500ms, while 5 of 28 moved over 1s. Sample well
> * past that so a static counter means "idle source", not "not refreshed yet".
> */
> #define SAMPLE_DELAY_US 2000000
> ...
> usleep(SAMPLE_DELAY_US);
Could this use bounded exponential-backoff polling instead? The fixed sleep is
being used to synchronize the second sample with the asynchronous telemetry
refresh, which violates the no sleep-based synchronization rule.
> if (sscanf(line, "%63s %u", name, &value) != 2) {
> tst_res(TFAIL, "malformed counter line: '%s'", line);
> continue;
> }
>
> if (strncmp(name, PREFIX, sizeof(PREFIX) - 1)) {
Could this validate the complete line and require a nonempty source suffix?
The current conversion accepts signed values, trailing tokens, and the bare
name "PKGC_BLOCK_RESIDENCY_". If both snapshots contain such a line, it is
recorded as a valid counter and the test can pass despite malformed output.
> .needs_root = 1,
Could the high-level description explain why root is required? Tests setting
needs_root must document the reason in the exported test description.
> high_freq_hwp_cap_cppc
> cpufreq_intel
> rfim01
> +pkgc_blocker_residency_show
Could the new entry be inserted alphabetically? Leaf .gitignore entries are
required to remain sorted.
Verdict - Needs revision
---
Note:
The agent can sometimes produce false positives although often its
findings are genuine. If you find issues with the review, please
comment this email or ignore the suggestions.
Regards,
LTP AI Reviewer
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-08-11 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 16:28 [LTP] [PATCH] pmc_core: add test for pkgc_blocker_residency_show Piotr Kubaj
2026-08-11 17:10 ` linuxtestproject.agent [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=20260811171005.9063-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=piotr.kubaj@intel.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.