From: Reinette Chatre <reinette.chatre@intel.com>
To: Xiaochen Shen <shenxiaochen@open-hieco.net>,
<tony.luck@intel.com>, <bp@alien8.de>, <fenghuay@nvidia.com>,
<shuah@kernel.org>, <skhan@linuxfoundation.org>
Cc: <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 v3 2/4] selftests/resctrl: Add CPU vendor detection for Hygon
Date: Thu, 11 Dec 2025 21:23:09 -0800 [thread overview]
Message-ID: <43b8ec69-3a19-48c0-93cf-48f3142b091c@intel.com> (raw)
In-Reply-To: <20251211064632.2344393-3-shenxiaochen@open-hieco.net>
Hi Xiaochen,
On 12/10/25 10:46 PM, Xiaochen Shen wrote:
> The resctrl selftest currently fails on Hygon CPUs that support Platform
> QoS features, printing the error:
>
> "# Can not get vendor info..."
>
> This occurs because vendor detection is missing for Hygon CPUs.
>
> Fix this by extending the CPU vendor detection logic to include
> Hygon's vendor ID.
>
> Signed-off-by: Xiaochen Shen <shenxiaochen@open-hieco.net>
> ---
Changelog is clear this is a fix, does patch need backport?
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Reinette
next prev parent reply other threads:[~2025-12-12 5:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 6:46 [PATCH v3 0/4] selftests/resctrl: Add Hygon CPUs support and bug fixes Xiaochen Shen
2025-12-11 6:46 ` [PATCH v3 1/4] selftests/resctrl: Define CPU vendor IDs as bits to match usage Xiaochen Shen
2025-12-12 5:22 ` Reinette Chatre
2025-12-12 7:32 ` Xiaochen Shen
2025-12-12 19:04 ` Reinette Chatre
2025-12-11 6:46 ` [PATCH v3 2/4] selftests/resctrl: Add CPU vendor detection for Hygon Xiaochen Shen
2025-12-12 5:23 ` Reinette Chatre [this message]
2025-12-12 7:38 ` Xiaochen Shen
2025-12-11 6:46 ` [PATCH v3 3/4] selftests/resctrl: Fix a division by zero error on Hygon Xiaochen Shen
2025-12-11 6:46 ` [PATCH v3 4/4] selftests/resctrl: Fix non-contiguous CBM check for Hygon 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=43b8ec69-3a19-48c0-93cf-48f3142b091c@intel.com \
--to=reinette.chatre@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=shenxiaochen@open-hieco.net \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tony.luck@intel.com \
--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