mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>,
	Shuah Khan <shuah@kernel.org>,
	Shuah Khan <skhan@linuxfoundation.org>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
	linux-kselftest@vger.kernel.org, loongarch@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] selftests/vDSO: Fix building errors on LoongArch
Date: Sat, 30 Dec 2023 11:56:45 +0500	[thread overview]
Message-ID: <b9bfa260-779a-493c-814e-13295203a5c4@collabora.com> (raw)
In-Reply-To: <20231213012300.5640-2-yangtiezhu@loongson.cn>

On 12/13/23 6:22 AM, Tiezhu Yang wrote:
> There exist the following errors when build vDSO selftests on LoongArch:
> 
>   # make headers && cd tools/testing/selftests/vDSO && make
>   ...
>   error: 'VDSO_VERSION' undeclared (first use in this function)
>   ...
>   error: 'VDSO_NAMES' undeclared (first use in this function)
> 
> We can see the following code in arch/loongarch/vdso/vdso.lds.S:
> 
> VERSION
> {
>         LINUX_5.10 {
>         global:
>                 __vdso_getcpu;
>                 __vdso_clock_getres;
>                 __vdso_clock_gettime;
>                 __vdso_gettimeofday;
>                 __vdso_rt_sigreturn;
>         local: *;
>         };
> }
> 
> so VDSO_VERSION should be 6 and VDSO_NAMES should be 1 for LoongArch,
> add them to fix the building errors on LoongArch.
> 
> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
Reviewed-by: Muhammad Usama Anjum <usama.anjum@collabora.com>

> ---
>  tools/testing/selftests/vDSO/vdso_config.h | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/tools/testing/selftests/vDSO/vdso_config.h b/tools/testing/selftests/vDSO/vdso_config.h
> index cdfed403ba13..7b543e7f04d7 100644
> --- a/tools/testing/selftests/vDSO/vdso_config.h
> +++ b/tools/testing/selftests/vDSO/vdso_config.h
> @@ -53,15 +53,19 @@
>  #if __riscv_xlen == 32
>  #define VDSO_32BIT		1
>  #endif
> +#elif defined(__loongarch__)
> +#define VDSO_VERSION		6
> +#define VDSO_NAMES		1
>  #endif
>  
> -static const char *versions[6] = {
> +static const char *versions[7] = {
>  	"LINUX_2.6",
>  	"LINUX_2.6.15",
>  	"LINUX_2.6.29",
>  	"LINUX_2.6.39",
>  	"LINUX_4",
>  	"LINUX_4.15",
> +	"LINUX_5.10"
>  };
>  
>  static const char *names[2][6] = {

-- 
BR,
Muhammad Usama Anjum

  reply	other threads:[~2023-12-30  6:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13  1:22 [PATCH v3 0/2] selftests/vDSO: Fix " Tiezhu Yang
2023-12-13  1:22 ` [PATCH v3 1/2] selftests/vDSO: Fix building " Tiezhu Yang
2023-12-30  6:56   ` Muhammad Usama Anjum [this message]
2023-12-13  1:23 ` [PATCH v3 2/2] selftests/vDSO: Fix runtime " Tiezhu Yang
2023-12-30  7:04   ` Muhammad Usama Anjum
2023-12-27  7:55 ` [PATCH v3 0/2] selftests/vDSO: Fix " Tiezhu Yang
2023-12-30  7:07   ` Muhammad Usama Anjum
2023-12-31 15:51     ` Tiezhu Yang
2024-01-29  8:27   ` Tiezhu Yang
2024-02-29  9:13     ` Tiezhu Yang
2024-03-07  9:20       ` Tiezhu Yang

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=b9bfa260-779a-493c-814e-13295203a5c4@collabora.com \
    --to=usama.anjum@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=yangtiezhu@loongson.cn \
    /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

all inboxes | Powered by JetHome®