From: "Garg, Shivank" <shivankg@amd.com>
To: Leo Yan <leo.yan@arm.com>,
linux-perf-users@vger.kernel.org,
James Clark <james.clark@linaro.org>
Cc: linux-kernel@vger.kernel.org, acme@redhat.com,
namhyung@kernel.org, yangyicong@hisilicon.com, bp@alien8.de,
mingo@kernel.org, xin@zytor.com, yosry.ahmed@linux.dev
Subject: Re: [PATCH] tools headers: Sync x86 cpufeatures and arm64 cputype headers
Date: Tue, 30 Sep 2025 12:10:00 +0530 [thread overview]
Message-ID: <fd09a708-bc70-4a49-a6c4-860f93ff8b4a@amd.com> (raw)
In-Reply-To: <2797b8f2-fc56-41a6-8ab3-dd298fd3ea36@amd.com>
On 9/29/2025 2:47 PM, Garg, Shivank wrote:
>
>
> On 9/29/2025 1:57 PM, Leo Yan wrote:
>> Hi Shivank,
>>
>> [ + James, perf-user ML ]
>>
>> On Mon, Sep 29, 2025 at 06:16:45AM +0000, Shivank Garg wrote:
>>> To pick up the changes in this cset:
>>>
>>> commit 2f8f173413f1 ("x86/vmscape: Add conditional IBPB mitigation")
>>> commit a508cec6e521 ("x86/vmscape: Enumerate VMSCAPE bug")
>>> commit c8c2647e69be ("arm64: Make _midr_in_range_list() an exported function")
>>> commit e3121298c7fc ("arm64: Modify _midr_range() functions to read MIDR/REVIDR internally")
>>>
>>> This addresses these perf build warnings:
>>> tools/perf$ ./check-headers.sh
>>> Warning: Kernel ABI header differences:
>>> diff -u tools/arch/x86/include/asm/cpufeatures.h arch/x86/include/asm/cpufeatures
>>> diff -u tools/arch/arm64/include/asm/cputype.h arch/arm64/include/asm/cputype.h
>>
>> Please drop arm64 related syncing, otherwise, it will break perf
>> building.
>
> Sure, I'll send V2 without arm64 sync.
>
> Thanks,
> Shivank
>>
>> At the meantime, James is working on refactoring cpu type definitions
>> for Arm64, we expect to avoid syncing cputype.h.
>>
>> Thanks,
>> Leo
>
tools/perf$ make
BUILD: Doing 'make -j128' parallel build
Warning: Kernel ABI header differences:
diff -u tools/include/linux/cfi_types.h include/linux/cfi_types.h
diff -u tools/arch/x86/include/asm/cpufeatures.h arch/x86/include/asm/cpufeatures.h
diff -u tools/include/asm-generic/bitops/__fls.h include/asm-generic/bitops/__fls.h
diff -u tools/include/asm-generic/bitops/fls.h include/asm-generic/bitops/fls.h
diff -u tools/include/asm-generic/bitops/fls64.h include/asm-generic/bitops/fls64.h
diff -u tools/arch/arm64/include/asm/cputype.h arch/arm64/include/asm/cputype.h
diff -u tools/perf/trace/beauty/include/uapi/linux/fcntl.h include/uapi/linux/fcntl.h
diff -u tools/perf/trace/beauty/include/uapi/linux/fs.h include/uapi/linux/fs.h
There are a lot of new ABI differences today, so I think it’s best to sync after the merge window?
Thanks,
Shivank
next prev parent reply other threads:[~2025-09-30 6:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 6:16 [PATCH] tools headers: Sync x86 cpufeatures and arm64 cputype headers Shivank Garg
2025-09-29 8:27 ` Leo Yan
2025-09-29 9:17 ` Garg, Shivank
2025-09-30 6:40 ` Garg, Shivank [this message]
2025-10-02 8:02 ` kernel test robot
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=fd09a708-bc70-4a49-a6c4-860f93ff8b4a@amd.com \
--to=shivankg@amd.com \
--cc=acme@redhat.com \
--cc=bp@alien8.de \
--cc=james.clark@linaro.org \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=xin@zytor.com \
--cc=yangyicong@hisilicon.com \
--cc=yosry.ahmed@linux.dev \
/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