From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: "Chang S. Bae" <chang.seok.bae@intel.com>,
Shuah Khan <shuah@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Weihong Zhang <weihong.zhang@intel.com>,
Binbin Wu <binbin.wu@linux.intel.com>,
angquan yu <angquan21@gmail.com>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
kernel@collabora.com, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests: x86: skip the tests if prerequisites aren't fulfilled
Date: Tue, 12 Mar 2024 14:26:28 +0500 [thread overview]
Message-ID: <21f8dbe3-9de2-41ad-a8bd-61d66cb38e90@collabora.com> (raw)
In-Reply-To: <1cacbd08-1131-4be4-b318-58c05afda2de@intel.com>
On 3/11/24 10:39 PM, Chang S. Bae wrote:
> On 3/11/2024 10:02 AM, Muhammad Usama Anjum wrote:
>> On 3/9/24 6:06 AM, Chang S. Bae wrote:
>>> On 3/7/2024 10:37 AM, Muhammad Usama Anjum wrote:
>>>
>>>> -static void check_cpuid_xtiledata(void)
>>>> +static int check_cpuid_xtiledata(void)
>>>> {
>>>> uint32_t eax, ebx, ecx, edx;
>>>> @@ -153,12 +160,16 @@ static void check_cpuid_xtiledata(void)
>>>> * eax: XTILEDATA state component size
>>>> * ebx: XTILEDATA state component offset in user buffer
>>>> */
>>>> - if (!eax || !ebx)
>>>> - fatal_error("xstate cpuid: invalid tile data size/offset: %d/%d",
>>>> - eax, ebx);
>>>> + if (!eax || !ebx) {
>>>> + ksft_print_msg("xstate cpuid: invalid tile data size/offset:
>>>> %d/%d\n",
>>>> + eax, ebx);
>>>> + return -1;
>>>> + }
>>>> xtiledata.size = eax;
>>>> xtiledata.xbuf_offset = ebx;
>>>> +
>>>> + return 0;
>>>> }
>>>
>>> I don't think it is okay to silently skip the test here. If the feature is
>>> available, the tile data size and offset should not be zero.
>> We are logging that data size/offset are invalid if either eax or ebx are
>> invalid and then we are skipping. Not sure what you are asking me to change.
>
> You intention seems to skip the test when AMX is not available.
Yes,
> But this
> function should only be invoked when AMX is actually available, not as part
> of the feature availability check.
How can we check if AMX is available or not?
> Therefore, I think this change is not
> relevant. Also, if we encounter invalid TILEDATA CPUID, it should be a
> reason to *fail* the test, rather than calling out a skip, right?
I see. But once we check if AMX is available.
>
> Thanks,
> Chang
>
--
BR,
Muhammad Usama Anjum
next prev parent reply other threads:[~2024-03-12 9:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 18:37 [PATCH] selftests: x86: skip the tests if prerequisites aren't fulfilled Muhammad Usama Anjum
2024-03-09 1:06 ` Chang S. Bae
2024-03-11 17:02 ` Muhammad Usama Anjum
2024-03-11 17:39 ` Chang S. Bae
2024-03-12 9:26 ` Muhammad Usama Anjum [this message]
2024-03-12 16:07 ` Chang S. Bae
2024-03-12 17:28 ` Muhammad Usama Anjum
2024-03-11 12:39 ` Kirill A. Shutemov
2024-03-12 0:10 ` Binbin Wu
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=21f8dbe3-9de2-41ad-a8bd-61d66cb38e90@collabora.com \
--to=usama.anjum@collabora.com \
--cc=angquan21@gmail.com \
--cc=binbin.wu@linux.intel.com \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kernel@collabora.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=shuah@kernel.org \
--cc=weihong.zhang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox