From: Shuah Khan <skhan@linuxfoundation.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Muhammad Usama Anjum" <usama.anjum@collabora.com>,
"Shuah Khan" <shuah@kernel.org>,
"Reinette Chatre" <reinette.chatre@intel.com>,
linux-kselftest@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Shaopeng Tan <tan.shaopeng@jp.fujitsu.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 0/3] selftests: Fix cpuid / vendor checking build issues
Date: Wed, 21 Aug 2024 00:30:53 -0600 [thread overview]
Message-ID: <88575c79-b6be-42d2-b863-d57f83f8c99c@linuxfoundation.org> (raw)
In-Reply-To: <20240813104515.19152-1-ilpo.jarvinen@linux.intel.com>
On 8/13/24 04:45, Ilpo Järvinen wrote:
> First, generalize resctrl selftest non-contiguous CAT check to not
> assume non-AMD vendor implies Intel. Second, improve kselftest common
> parts and resctrl selftest such that the use of __cpuid_count() does
> not lead into a build failure (happens at least on ARM).
>
> The last patch might still require some work on which symbol the
> conditional in kselftest.h is implemented. I could not find any
> pre-existing one that could be used. Perhaps somebody who's more
> familiar with the kselftest build system has a better suggestion on
> which symbol the logic should be based at?
>
> Ilpo Järvinen (3):
> selftests/resctrl: Generalize non-contiguous CAT check
> selftests/resctrl: Always initialize ecx to avoid build warnings
> [RFC] kselftest: Provide __cpuid_count() stub on non-x86 archs
>
> tools/testing/selftests/kselftest.h | 6 +++++
> tools/testing/selftests/lib.mk | 4 ++++
> tools/testing/selftests/resctrl/cat_test.c | 28 +++++++++++++---------
> 3 files changed, 27 insertions(+), 11 deletions(-)
>
These changes look good to me. Can you send the RFC patch without the RFC tag
for me to pull in? I don't apply RFC patches.
Usama, does this fix the problem you are seeing?
Hi Reinette - do these look okay to you? Can you give me an ack if they do?
thanks,
-- Shuah
next prev parent reply other threads:[~2024-08-21 6:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 10:45 [PATCH 0/3] selftests: Fix cpuid / vendor checking build issues Ilpo Järvinen
2024-08-13 10:45 ` [PATCH 1/3] selftests/resctrl: Generalize non-contiguous CAT check Ilpo Järvinen
2024-08-22 4:48 ` Muhammad Usama Anjum
2024-08-13 10:45 ` [PATCH 2/3] selftests/resctrl: Always initialize ecx to avoid build warnings Ilpo Järvinen
2024-08-22 4:49 ` Muhammad Usama Anjum
2024-08-13 10:45 ` [RFC PATCH 3/3] kselftest: Provide __cpuid_count() stub on non-x86 archs Ilpo Järvinen
2024-08-22 4:49 ` Muhammad Usama Anjum
2024-08-21 6:30 ` Shuah Khan [this message]
2024-08-22 4:51 ` [PATCH 0/3] selftests: Fix cpuid / vendor checking build issues Muhammad Usama Anjum
2024-08-22 7:41 ` Ilpo Järvinen
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=88575c79-b6be-42d2-b863-d57f83f8c99c@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--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 \
--cc=tan.shaopeng@jp.fujitsu.com \
--cc=usama.anjum@collabora.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