From: John Hubbard <jhubbard@nvidia.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
Shuah Khan <shuah@kernel.org>, Ingo Molnar <mingo@kernel.org>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: angquan yu <angquan21@gmail.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Binbin Wu <binbin.wu@linux.intel.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Sohil Mehta <sohil.mehta@intel.com>,
Yu-cheng Yu <yu-cheng.yu@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Valentin Obst <kernel@valentinobst.de>,
linux-kselftest@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
llvm@lists.linux.dev, x86@kernel.org
Subject: Re: [PATCH v2 0/6] selftests/x86: fix build errors and warnings found via clang
Date: Thu, 30 May 2024 12:21:40 -0700 [thread overview]
Message-ID: <3a67e1db-0945-4f68-948f-02fadfd6d25a@nvidia.com> (raw)
In-Reply-To: <f4877afd-dc2c-4e54-8b53-c681d3eed045@linuxfoundation.org>
On 5/30/24 7:58 AM, Shuah Khan wrote:
> On 5/27/24 15:00, John Hubbard wrote:
>> Hi,
>>
>> Just a bunch of build and warnings fixes that show up when
>> building with clang. Some of these depend on each other, so
>> I'm sending them as a series.
>>
>> Changes since the first version:
>>
>> 1) Rebased onto Linux 6.10-rc1
>
> x86 test patches usually go through x86 tree.
>
> This series requires x86 maintainer review and ack for me
> to take this through kselftest tree.
Hi Shuah,
Yes. I'm having some difficulty getting anyone from x86 to respond to
these. Let me add a few more x86 maintainers to this thread in hopes
of hearing something.
thanks,
--
John Hubbard
NVIDIA
...
>> John Hubbard (6):
>> selftests/x86: build test_FISTTP.c with clang
>> selftests/x86: build fsgsbase_restore.c with clang
>> selftests/x86: build sysret_rip.c with clang
>> selftests/x86: avoid -no-pie warnings from clang during compilation
>> selftests/x86: remove (or use) unused variables and functions
>> selftests/x86: fix printk warnings reported by clang
>>
>> tools/testing/selftests/x86/Makefile | 10 +++++++
>> tools/testing/selftests/x86/amx.c | 16 -----------
>> .../testing/selftests/x86/clang_helpers_32.S | 11 ++++++++
>> .../testing/selftests/x86/clang_helpers_64.S | 28 +++++++++++++++++++
>> tools/testing/selftests/x86/fsgsbase.c | 6 ----
>> .../testing/selftests/x86/fsgsbase_restore.c | 11 ++++----
>> tools/testing/selftests/x86/sigreturn.c | 2 +-
>> .../testing/selftests/x86/syscall_arg_fault.c | 1 -
>> tools/testing/selftests/x86/sysret_rip.c | 20 ++++---------
>> tools/testing/selftests/x86/test_FISTTP.c | 8 +++---
>> tools/testing/selftests/x86/test_vsyscall.c | 15 ++++------
>> tools/testing/selftests/x86/vdso_restorer.c | 2 ++
>> 12 files changed, 72 insertions(+), 58 deletions(-)
>> create mode 100644 tools/testing/selftests/x86/clang_helpers_32.S
>> create mode 100644 tools/testing/selftests/x86/clang_helpers_64.S
>>
>>
>> base-commit: 2bfcfd584ff5ccc8bb7acde19b42570414bf880b
>> prerequisite-patch-id: 39d606b9b165077aa1a3a3b0a3b396dba0c20070
>
> thanks,
> -- Shuah
>
next prev parent reply other threads:[~2024-05-30 19:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 21:00 [PATCH v2 0/6] selftests/x86: fix build errors and warnings found via clang John Hubbard
2024-05-27 21:00 ` [PATCH v2 1/6] selftests/x86: build test_FISTTP.c with clang John Hubbard
2024-05-27 21:00 ` [PATCH v2 2/6] selftests/x86: build fsgsbase_restore.c " John Hubbard
2024-05-27 21:00 ` [PATCH v2 3/6] selftests/x86: build sysret_rip.c " John Hubbard
2024-05-27 21:00 ` [PATCH v2 4/6] selftests/x86: avoid -no-pie warnings from clang during compilation John Hubbard
2024-05-27 21:00 ` [PATCH v2 5/6] selftests/x86: remove (or use) unused variables and functions John Hubbard
2024-05-27 21:00 ` [PATCH v2 6/6] selftests/x86: fix printk warnings reported by clang John Hubbard
2024-05-30 14:58 ` [PATCH v2 0/6] selftests/x86: fix build errors and warnings found via clang Shuah Khan
2024-05-30 19:21 ` John Hubbard [this message]
2024-05-30 19:46 ` Dave Hansen
2024-05-30 20:00 ` John Hubbard
2024-05-31 5:12 ` Muhammad Usama Anjum
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=3a67e1db-0945-4f68-948f-02fadfd6d25a@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=adobriyan@gmail.com \
--cc=angquan21@gmail.com \
--cc=binbin.wu@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kernel@valentinobst.de \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=sohil.mehta@intel.com \
--cc=x86@kernel.org \
--cc=yu-cheng.yu@intel.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