From: linuxtestproject.agent@gmail.com
To: Piotr Kubaj <piotr.kubaj@intel.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] high_freq_hwp_cap_cppc.c: new test
Date: Tue, 9 Jun 2026 12:42:52 +0000 [thread overview]
Message-ID: <20260609124252.4112-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260609121840.61087-2-piotr.kubaj@intel.com>
Hi Piotr,
On Tue, Jun 9 2026, Piotr Kubaj wrote:
> high_freq_hwp_cap_cppc.c: new test
> +#include "tst_test.h"
> +#include "tst_safe_prw.h"
> +#include "lapi/cpuid.h"
lapi/cpuid.h contains #error on non-x86 architectures and
__cpuid_count uses x86 inline assembly, so this file will not
compile on ARM, s390x, etc.
Ground rule 6 requires architecture-specific tests to still compile
everywhere. The existing ptrace07.c shows the correct pattern:
wrap the entire file body in
#if defined(__i386__) || defined(__x86_64__) with a
TST_TEST_TCONF("test requires x86") in the #else branch.
> + for (int i = 0; i < nproc; i++)
> + tst_res(TINFO, "cpu%d: %s", i, mismatch[i] ? "MISMATCH" : "OK");
Offline CPUs are skipped during the comparison loop but the
summary still prints "OK" for them (mismatch[i] is zero from
memset). This is misleading -- "OK" implies the values matched
when no check was performed. Consider skipping offline CPUs here
too, or printing "OFFLINE" instead.
> +/*\
> + * Verify for all online logical CPUs that their highest performance value are
> + * the same for HWP Capability MSR 0x771 and CPPC sysfs file.
The test sets .needs_root = 1 but the doc comment does not explain
why root is required. Per the LTP guidelines, the reason should be
stated (reading /dev/cpu/N/msr needs CAP_SYS_RAWIO / root).
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
next prev parent reply other threads:[~2026-06-09 12:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 12:18 [LTP] [PATCH v14] high_freq_hwp_cap_cppc.c: new test Piotr Kubaj
2026-06-09 12:42 ` linuxtestproject.agent [this message]
2026-06-09 13:55 ` [LTP] " Cyril Hrubis
2026-06-09 14:35 ` [LTP] [PATCH v14] " Cyril Hrubis
2026-06-09 14:40 ` Andrea Cervesato via ltp
-- strict thread matches above, loose matches on Subject: below --
2026-05-14 9:35 [LTP] [PATCH v13] " Piotr Kubaj
2026-05-14 11:58 ` [LTP] " linuxtestproject.agent
2026-05-07 7:22 [LTP] [PATCH v12] " Piotr Kubaj
2026-05-07 9:38 ` [LTP] " linuxtestproject.agent
2026-05-06 12:56 [LTP] [PATCH v11] " Piotr Kubaj
2026-05-06 14:15 ` [LTP] " linuxtestproject.agent
2026-05-05 9:54 [LTP] [PATCH v10] " Piotr Kubaj
2026-05-05 17:54 ` [LTP] " linuxtestproject.agent
2026-05-04 10:17 [LTP] [PATCH v9] " Piotr Kubaj
2026-05-04 11:55 ` [LTP] " linuxtestproject.agent
2026-04-20 9:44 [LTP] [PATCH v7] " Piotr Kubaj
2026-04-20 10:53 ` [LTP] " linuxtestproject.agent
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=20260609124252.4112-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.