From: John Hubbard <jhubbard@nvidia.com>
To: Shuah Khan <shuah@kernel.org>, Dave Hansen <dave.hansen@linux.intel.com>
Cc: angquan yu <angquan21@gmail.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>,
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>,
Muhammad Usama Anjum <usama.anjum@collabora.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 v3 0/7] selftests/x86: fix build errors and warnings found via clang
Date: Fri, 28 Jun 2024 13:06:18 -0700 [thread overview]
Message-ID: <d9c56b70-6120-4de7-920b-9ece52905c00@nvidia.com> (raw)
In-Reply-To: <20240531193838.108454-1-jhubbard@nvidia.com>
On 5/31/24 12:38 PM, John Hubbard wrote:
> Hi,
>
> Dave Hansen, Muhammad Usama Anjum, here is the combined series that we
> discussed yesterday [1].
Hi Dave, Shuah,
Are either of you planning to take this series? I ask because I have a
very slightly overlapping series that enhances the LLVM/clang checks,
that I'm about to post. And I'm not sure if I should try to include
a small fix that would apply to patch 5/7 here.
(This is not urgent, because it's merely a deferral of adding LLVM/clang
support to these kselftests.)
thanks,
--
John Hubbard
NVIDIA
>
> As I mentioned then, this is a bit intrusive--but no more than
> necessary, IMHO. Specifically, it moves some clang-un-inlineable things
> out to "pure" assembly code files.
>
> I've tested this by building with clang, then running each binary on my
> x86_64 test system with today's 6.10-rc1, and comparing the console and
> dmesg output to a gcc-based build without these patches applied. Aside
> from timestamps and virtual addresses, it looks identical.
>
> Earlier cover letter:
>
> 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 v2:
>
> 1) Dropped my test_FISTTP.c patch, and picked up Muhammad's fix instead,
> seeing as how that was posted first.
>
> 2) Updated patch descriptions to reflect that Valentin Obst's build fix
> for LLVM [1] has already been merged into Linux main.
>
> 3) Minor wording and typo corrections in the commit logs throughout.
>
> Changes since the first version:
> 1) Rebased onto Linux 6.10-rc1
>
> Enjoy!
>
> [1] https://lore.kernel.org/44428518-4d21-4de7-8587-04eceefb330d@nvidia.com
>
> thanks,
> John Hubbard
>
> John Hubbard (6):
> selftests/x86: fix Makefile dependencies to work 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
>
> Muhammad Usama Anjum (1):
> selftests: x86: test_FISTTP: use fisttps instead of ambiguous fisttp
>
> tools/testing/selftests/x86/Makefile | 31 +++++++++++++++----
> 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, 87 insertions(+), 64 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: 4a4be1ad3a6efea16c56615f31117590fd881358
next prev parent reply other threads:[~2024-06-28 20:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 19:38 [PATCH v3 0/7] selftests/x86: fix build errors and warnings found via clang John Hubbard
2024-05-31 19:38 ` [PATCH v3 1/7] selftests/x86: fix Makefile dependencies to work with clang John Hubbard
2024-05-31 19:38 ` [PATCH v3 2/7] selftests: x86: test_FISTTP: use fisttps instead of ambiguous fisttp John Hubbard
2024-05-31 19:38 ` [PATCH v3 3/7] selftests/x86: build fsgsbase_restore.c with clang John Hubbard
2024-05-31 19:38 ` [PATCH v3 4/7] selftests/x86: build sysret_rip.c " John Hubbard
2024-05-31 19:38 ` [PATCH v3 5/7] selftests/x86: avoid -no-pie warnings from clang during compilation John Hubbard
2024-06-07 22:23 ` John Hubbard
2024-05-31 19:38 ` [PATCH v3 6/7] selftests/x86: remove (or use) unused variables and functions John Hubbard
2024-05-31 19:38 ` [PATCH v3 7/7] selftests/x86: fix printk warnings reported by clang John Hubbard
2024-06-28 20:06 ` John Hubbard [this message]
2024-07-02 10:28 ` [PATCH v3 0/7] selftests/x86: fix build errors and warnings found via clang Muhammad Usama Anjum
2024-07-04 3:08 ` John Hubbard
2024-07-04 5:48 ` 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=d9c56b70-6120-4de7-920b-9ece52905c00@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=mingo@kernel.org \
--cc=rick.p.edgecombe@intel.com \
--cc=shuah@kernel.org \
--cc=sohil.mehta@intel.com \
--cc=usama.anjum@collabora.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;
as well as URLs for NNTP newsgroup(s).