From: Reinette Chatre <reinette.chatre@intel.com>
To: <babu.moger@amd.com>, <fenghua.yu@intel.com>, <shuah@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
<ilpo.jarvinen@linux.intel.com>,
<maciej.wieczor-retman@intel.com>, <peternewman@google.com>,
<eranian@google.com>
Subject: Re: [PATCH] selftests/resctrl: Fix noncont_cat_run_test for AMD
Date: Fri, 7 Jun 2024 14:47:48 -0700 [thread overview]
Message-ID: <2491e8da-8664-428f-87bd-40595af7af47@intel.com> (raw)
In-Reply-To: <edc31538-3aa1-a35a-ea67-b13f626a84ec@amd.com>
Hi Babu,
On 6/7/24 11:16 AM, Moger, Babu wrote:
> On 6/6/2024 6:58 PM, Reinette Chatre wrote:
>> On 6/6/24 4:09 PM, Moger, Babu wrote:
>>> @@ -301,15 +320,8 @@ static int noncont_cat_run_test(const struct resctrl_test *test,
>>> if (ret)
>>> return ret;
>>>
>>> - if (!strcmp(test->resource, "L3"))
>>> - __cpuid_count(0x10, 1, eax, ebx, ecx, edx);
>>> - else if (!strcmp(test->resource, "L2"))
>>> - __cpuid_count(0x10, 2, eax, ebx, ecx, edx);
>>> - else
>>> - return -EINVAL;
>>> -
>>> - if (sparse_masks != ((ecx >> 3) & 1)) {
>>> - ksft_print_msg("CPUID output doesn't match 'sparse_masks' file content!\n");
>>> + if (!(arch_supports_noncont_cat(test) && sparse_masks)) {
>>> + ksft_print_msg("Hardware does not support non-contiguous CBM!\n");
>>
>> Please fix the test as well as the message. It is not an error if hardware does
>> not support non-contiguous CBM. It is an error if the hardware and kernel disagrees whether
>> non-contiguous CBM is supported.
>
> Not sure about this comment.
>
> Did you mean?
>
> if (!arch_supports_noncont_cat(test)) {
> ksft_print_msg("Hardware does not support non-contiguous CBM!\n");
> return 0;
The above changes whether support for non-contiguous CBM is treated as an error but the
test should still proceed since the test goes on to write different CBM to the system
and verifies results are as expected based on what hardware supports.
> } else if (arch_supports_noncont_cat(test) && !sparse_masks)) {
> ksft_print_msg("Hardware and kernel support for non-contiguous CBM does not match!\n");
> return 1;
I can see how this will work for AMD for the scenario being checked but not for
the different Intel variants.
I think this can all be simplified with something like:
if (arch_supports_noncont_cat(test) != sparse_masks)) {
ksft_print_msg("Hardware and kernel differ on non-contiguous CBM support!\n");
return 1;
}
I modified the message slightly since non-contiguous CBM does not actually require kernel
support.
What do you think?
Reinette
next prev parent reply other threads:[~2024-06-07 21:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 21:36 [PATCH] selftests/resctrl: Fix noncont_cat_run_test for AMD Babu Moger
2024-06-06 20:33 ` Reinette Chatre
2024-06-06 23:09 ` Moger, Babu
2024-06-06 23:58 ` Reinette Chatre
2024-06-07 18:16 ` Moger, Babu
2024-06-07 21:47 ` Reinette Chatre [this message]
2024-06-07 22:35 ` Moger, Babu
2024-06-07 10:21 ` Ilpo Järvinen
2024-06-10 16:00 ` [PATCH v2] " Babu Moger
2024-06-10 16:20 ` Ilpo Järvinen
2024-06-10 17:51 ` Moger, Babu
2024-06-10 21:28 ` Reinette Chatre
2024-06-11 6:50 ` Ilpo Järvinen
2024-06-10 21:32 ` Reinette Chatre
2024-06-10 23:11 ` Moger, Babu
2024-06-11 23:14 ` Reinette Chatre
2024-06-11 22:18 ` [PATCH v3] selftests/resctrl: Fix non-contiguous CBM " Babu Moger
2024-06-12 7:33 ` Ilpo Järvinen
2024-06-26 16:55 ` Reinette Chatre
2024-06-26 19:25 ` Shuah Khan
2024-06-26 20:44 ` Reinette Chatre
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=2491e8da-8664-428f-87bd-40595af7af47@intel.com \
--to=reinette.chatre@intel.com \
--cc=babu.moger@amd.com \
--cc=eranian@google.com \
--cc=fenghua.yu@intel.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=peternewman@google.com \
--cc=shuah@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