From: Shuah Khan <skhan@linuxfoundation.org>
To: Muhammad Usama Anjum <Usama.Anjum@collabora.com>,
shuah@kernel.org, fenghua.yu@intel.com,
reinette.chatre@intel.com, ilpo.jarvinen@linux.intel.com
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests:resctrl: Fix build failure on archs without __cpuid_count()
Date: Fri, 6 Sep 2024 08:15:29 -0600 [thread overview]
Message-ID: <ae32280e-e3a2-418c-a148-c59956b6521c@linuxfoundation.org> (raw)
In-Reply-To: <ad3d035e-be82-44c4-a850-a33889fcf717@collabora.com>
On 9/6/24 01:35, Muhammad Usama Anjum wrote:
> Hi Shuah,
>
> Thank you for fixing it.
>
> On 9/5/24 11:02 PM, Shuah Khan wrote:
>> When resctrl is built on architectures without __cpuid_count()
>> support, build fails. resctrl uses __cpuid_count() defined in
>> kselftest.h.
>>
>> Even though the problem is seen while building resctrl on aarch64,
>> this error can be seen on any platform that doesn't support CPUID.
>>
>> CPUID is a x86/x86-64 feature and code paths with CPUID asm commands
>> will fail to build on all other architectures.
>>
>> All others tests call __cpuid_count() do so from x86/x86_64 code paths
>> when _i386__ or __x86_64__ are defined. resctrl is an exception.
>>
>> Fix the problem by defining __cpuid_count() only when __i386__ or
>> __x86_64__ are defined in kselftest.h and changing resctrl to call
>> __cpuid_count() only when __i386__ or __x86_64__ are defined.
>>
>> In file included from resctrl.h:24,
>> from cat_test.c:11:
>> In function ‘arch_supports_noncont_cat’,
>> inlined from ‘noncont_cat_run_test’ at cat_test.c:326:6:
>> ../kselftest.h:74:9: error: impossible constraint in ‘asm’
>> 74 | __asm__ __volatile__ ("cpuid\n\t" \
>> | ^~~~~~~
>> cat_test.c:304:17: note: in expansion of macro ‘__cpuid_count’
>> 304 | __cpuid_count(0x10, 1, eax, ebx, ecx, edx);
>> | ^~~~~~~~~~~~~
>> ../kselftest.h:74:9: error: impossible constraint in ‘asm’
>> 74 | __asm__ __volatile__ ("cpuid\n\t" \
>> | ^~~~~~~
>> cat_test.c:306:17: note: in expansion of macro ‘__cpuid_count’
>> 306 | __cpuid_count(0x10, 2, eax, ebx, ecx, edx);
>>
>> Reported-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
>> Reported-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
>> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
> LGTM
> Reviewed-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
Thank you for the review and finding the problem to begin with.
Much appreciated.
>
> ...
>> diff --git a/tools/testing/selftests/resctrl/cat_test.c b/tools/testing/selftests/resctrl/cat_test.c
>> index 742782438ca3..ae3f0fa5390b 100644
>> --- a/tools/testing/selftests/resctrl/cat_test.c
>> +++ b/tools/testing/selftests/resctrl/cat_test.c
>> @@ -290,12 +290,12 @@ static int cat_run_test(const struct resctrl_test *test, const struct user_param
>>
>> static bool arch_supports_noncont_cat(const struct resctrl_test *test)
>> {
>> - unsigned int eax, ebx, ecx, edx;
>> -
>> /* AMD always supports non-contiguous CBM. */
>> if (get_vendor() == ARCH_AMD)
>> return true;
>>
>> +#if defined(__i386__) || defined(__x86_64__) /* arch */
>> + unsigned int eax, ebx, ecx, edx;
>> /* Intel support for non-contiguous CBM needs to be discovered. */
>> if (!strcmp(test->resource, "L3"))
>> __cpuid_count(0x10, 1, eax, ebx, ecx, edx);
>> @@ -305,6 +305,8 @@ static bool arch_supports_noncont_cat(const struct resctrl_test *test)
>> return false;
>>
>> return ((ecx >> 3) & 1);
>> +#endif /* end arch */
>> + return false;
> nit: empty line before return
Will do.
>
>> }
>>
>> static int noncont_cat_run_test(const struct resctrl_test *test,
>
thanks,
-- Shuah
next prev parent reply other threads:[~2024-09-06 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 18:02 [PATCH] selftests:resctrl: Fix build failure on archs without __cpuid_count() Shuah Khan
2024-09-05 20:45 ` Reinette Chatre
2024-09-05 20:50 ` Shuah Khan
2024-09-06 7:35 ` Muhammad Usama Anjum
2024-09-06 14:15 ` Shuah Khan [this message]
2024-09-06 10:12 ` Ilpo Järvinen
2024-09-06 14:14 ` Shuah Khan
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=ae32280e-e3a2-418c-a148-c59956b6521c@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=Usama.Anjum@collabora.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=reinette.chatre@intel.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