From: "Luck, Tony" <tony.luck@intel.com>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: Xiaochen Shen <shenxiaochen@open-hieco.net>,
Fenghua Yu <fenghuay@nvidia.com>, <bp@alien8.de>,
<shuah@kernel.org>, <skhan@linuxfoundation.org>,
<babu.moger@amd.com>, <james.morse@arm.com>,
<Dave.Martin@arm.com>, <x86@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] selftests/resctrl: Add CPU vendor detection for Hygon
Date: Tue, 9 Dec 2025 15:42:01 -0800 [thread overview]
Message-ID: <aTizyW7R8Mqj-lSJ@agluck-desk3> (raw)
In-Reply-To: <d713c903-b8fd-4909-a520-6426fabc003a@intel.com>
On Tue, Dec 09, 2025 at 03:02:14PM -0800, Reinette Chatre wrote:
> I suggest this be simplified to not have the vendor ID be used both as a value and as a state.
> Here is some pseudo-code that should be able to accomplish this:
>
>
> unsigned int detect_vendor(void)
> {
> static bool initialized = false;
> static unsigned int vendor_id;
> ...
> FILE *inf;
>
>
> if (initialized)
> return vendor_id;
>
> inf = fopen("/proc/cpuinfo", "r");
> if (!inf) {
> vendor_id = 0;
> initialized = true;
> return vendor_id;
> }
>
> /* initialize vendor_id from /proc/cpuinfo */
>
> initialized = true;
> return vendor_id;
> }
>
> unsigned int get_vendor(void)
> {
> unsigned int vendor;
>
> vendor = detect_vendor();
>
> if (vendor == 0)
> ksft_print_msg(...);
>
> return vendor;
> }
If detect_vendor() failed, this you'd get the ksft_print_msg() for every
call to get_vendor().
Why not split completly.
static unsigned int vendor_id;
void detect_vendor(void)
{
FILE *inf = fopen("/proc/cpuinfo", "r");
if (!inf) {
... warning unable to get vendor id ...
}
... initialize from /proc/cpuinfo ...
... warn if doesn't find a known vendor ...
}
Call detect_vendor() at the beginning of main() in each test.
Then just use "vendor_id" whenever you need to test for some vendor
specific feature.
-Tony
next prev parent reply other threads:[~2025-12-09 23:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 9:25 [PATCH v2 0/3] selftests/resctrl: Add Hygon CPUs support and bug fixes Xiaochen Shen
2025-12-05 9:25 ` [PATCH v2 1/3] selftests/resctrl: Add CPU vendor detection for Hygon Xiaochen Shen
2025-12-05 19:28 ` Fenghua Yu
2025-12-08 8:01 ` Xiaochen Shen
2025-12-08 17:57 ` Reinette Chatre
2025-12-09 6:10 ` Xiaochen Shen
2025-12-09 23:02 ` Reinette Chatre
2025-12-09 23:42 ` Luck, Tony [this message]
2025-12-10 0:30 ` Reinette Chatre
2025-12-10 4:46 ` Xiaochen Shen
2025-12-05 9:25 ` [PATCH v2 2/3] selftests/resctrl: Fix a division by zero error on Hygon Xiaochen Shen
2025-12-05 18:53 ` Fenghua Yu
2025-12-08 2:27 ` Xiaochen Shen
2025-12-05 9:25 ` [PATCH v2 3/3] selftests/resctrl: Fix non-contiguous CBM check for Hygon Xiaochen Shen
2025-12-05 19:39 ` Fenghua Yu
2025-12-05 21:30 ` Reinette Chatre
2025-12-05 21:51 ` Fenghua Yu
2025-12-08 8:06 ` Xiaochen Shen
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=aTizyW7R8Mqj-lSJ@agluck-desk3 \
--to=tony.luck@intel.com \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=fenghuay@nvidia.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=shenxiaochen@open-hieco.net \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=x86@kernel.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