From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Muhammad Usama Anjum <Usama.Anjum@collabora.com>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Shuah Khan <shuah@kernel.org>,
Reinette Chatre <reinette.chatre@intel.com>,
linux-kselftest@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Shaopeng Tan <tan.shaopeng@jp.fujitsu.com>,
Fenghua Yu <fenghua.yu@intel.com>
Subject: Re: [PATCH 0/3] selftests: Fix cpuid / vendor checking build issues
Date: Thu, 22 Aug 2024 10:41:08 +0300 (EEST) [thread overview]
Message-ID: <975d32d5-9a86-1a31-984e-a31dc0353123@linux.intel.com> (raw)
In-Reply-To: <7f4d4d41-e59d-4574-99e7-4dba69929954@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 1764 bytes --]
On Thu, 22 Aug 2024, Muhammad Usama Anjum wrote:
> On 8/21/24 11:30 AM, Shuah Khan wrote:
> > 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?
>
> Yeah, build errors are resolved.
Great, thanks for testing!
I'll send v2 with RFC removed soon.
> > Hi Reinette - do these look okay to you? Can you give me an ack if they do?
> >
> > thanks,
> > -- Shuah
> >
>
--
i.
prev parent reply other threads:[~2024-08-22 7:41 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 ` [PATCH 0/3] selftests: Fix cpuid / vendor checking build issues Shuah Khan
2024-08-22 4:51 ` Muhammad Usama Anjum
2024-08-22 7:41 ` Ilpo Järvinen [this message]
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=975d32d5-9a86-1a31-984e-a31dc0353123@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Usama.Anjum@collabora.com \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tan.shaopeng@jp.fujitsu.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