From: Reinette Chatre <reinette.chatre@intel.com>
To: babu.moger@amd.com, "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: fenghua.yu@intel.com, shuah@kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linux-kselftest@vger.kernel.org,
"Maciej Wieczór-Retman" <maciej.wieczor-retman@intel.com>,
peternewman@google.com, eranian@google.com
Subject: Re: [PATCH v2] selftests/resctrl: Fix noncont_cat_run_test for AMD
Date: Mon, 10 Jun 2024 14:28:09 -0700 [thread overview]
Message-ID: <399b6497-2c76-4f16-8e21-27d209e214d2@intel.com> (raw)
In-Reply-To: <0e153d27-fa1d-4c47-8d4e-a2004c991ffc@amd.com>
Hi Babu,
On 6/10/24 10:51 AM, Moger, Babu wrote:
> Hi
>
> On 6/10/24 11:20, Ilpo Järvinen wrote:
>> On Mon, 10 Jun 2024, Babu Moger wrote:
>>
>>> The selftest noncont_cat_run_test fails on AMD with the warnings. Reason
>>
>> noncont_cat_run_test()
>
> I want to mention the test here. not function. How about this?
>
> "The selftest non-contiguous CBM test fails on AMD with the warnings."
>
This does not take Ilpo's feedback regarding "the warnings" into account.
I agree with Ilpo (keeping his comment below) that "with the warnings"
sounds incomplete. Also, it is not necessary to mention both "selftest"
and "test" in "The selftest non-contiguous CBM test".
You can change it to something like:
The non-contiguous CBM test fails on AMD with:
/* insert error message here */
AMD always supports non-contiguous CBM but does not report
it via CPUID.
Fix the non-contiguous CBM test to use CPUID to discover
non-contiguous CBM support only on Intel.
>>
>> (In general, use () when refering to a function, same thing in the
>> shortlog).
>>
>> "the warnings" sounds like I should know about what warning it fails with
>> but there's no previous context which tells that information. I suggest
>> you either use "a warning" or quote the warning it fails with into the
>> commit message.
>>
>>> is, AMD supports non contiguous CBM masks but does not report it via CPUID.
The "M" in CBM is for "mask" so there is no need to write "mask" after CBM.
Reinette
next prev parent reply other threads:[~2024-06-10 21:28 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
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 [this message]
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=399b6497-2c76-4f16-8e21-27d209e214d2@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