public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>,
	 Reinette Chatre <reinette.chatre@intel.com>,
	Shuah Khan <shuah@kernel.org>,
	 Shaopeng Tan <tan.shaopeng@jp.fujitsu.com>,
	kernel@collabora.com,  Shuah Khan <skhan@linuxfoundation.org>,
	 LKML <linux-kernel@vger.kernel.org>,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] selftests: resctrl: ignore builds for unsupported architectures
Date: Fri, 9 Aug 2024 10:23:31 +0300 (EEST)	[thread overview]
Message-ID: <d60cf782-9ab0-ed4a-0b3e-ba7a73ae8d51@linux.intel.com> (raw)
In-Reply-To: <20240809071059.265914-1-usama.anjum@collabora.com>

On Fri, 9 Aug 2024, Muhammad Usama Anjum wrote:

> This test doesn't have support for other architectures. Altough resctrl
> is supported on x86 and ARM, but arch_supports_noncont_cat() shows that
> only x86 for AMD and Intel are supported by the test.

One does not follow from the other. arch_supports_noncont_cat() is only 
small part of the tests so saying "This test" based on a small subset of 
all tests is bogus. Also, I don't see any reason why ARCH_ARM could not be 
added and arch_supports_noncont_cat() adapted accordingly.

> We get build
> errors when built for ARM and ARM64.

As this seems the real reason, please quote any errors when you use them 
as justification so it can be reviewed if the reasoning is sound or not.

-- 
 i.

> Hence add support in the Makefile to build this suite only for x86 and
> x86_64 architectures.
> 
> Fixes: b733143cc455 ("selftests/resctrl: Make resctrl_tests run using kselftest framework")
> Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
> ---
>  tools/testing/selftests/resctrl/Makefile | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/tools/testing/selftests/resctrl/Makefile b/tools/testing/selftests/resctrl/Makefile
> index f408bd6bfc3d4..d5cf96315ef9b 100644
> --- a/tools/testing/selftests/resctrl/Makefile
> +++ b/tools/testing/selftests/resctrl/Makefile
> @@ -3,7 +3,9 @@
>  CFLAGS = -g -Wall -O2 -D_FORTIFY_SOURCE=2
>  CFLAGS += $(KHDR_INCLUDES)
>  
> +ifeq ($(ARCH),$(filter $(ARCH),x86 x86_64))
>  TEST_GEN_PROGS := resctrl_tests
> +endif
>  
>  LOCAL_HDRS += $(wildcard *.h)
>  
> 


  reply	other threads:[~2024-08-09  7:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09  7:10 [PATCH] selftests: resctrl: ignore builds for unsupported architectures Muhammad Usama Anjum
2024-08-09  7:23 ` Ilpo Järvinen [this message]
2024-08-09  8:05   ` Muhammad Usama Anjum
2024-08-09  8:45     ` Ilpo Järvinen
2024-08-12 20:36       ` Reinette Chatre
2024-08-12 22:49       ` Shuah Khan
2024-08-13  0:05         ` Reinette Chatre
2024-08-13  7:39           ` Ilpo Järvinen
2024-08-13  8:27             ` Shuah Khan
2024-08-13  8:25           ` 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=d60cf782-9ab0-ed4a-0b3e-ba7a73ae8d51@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=kernel@collabora.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 \
    --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