From: Sherry Yang <sherry.yang@oracle.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: "joerg.roedel@amd.com" <joerg.roedel@amd.com>,
"kevin.tian@intel.com" <kevin.tian@intel.com>,
"vasant.hegde@amd.com" <vasant.hegde@amd.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"will@kernel.org" <will@kernel.org>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iommupt/amdv1: avoid GCOV builds triggering FIELD_PREP build failure
Date: Tue, 10 Mar 2026 17:17:31 +0000 [thread overview]
Message-ID: <62EB69AA-FA3E-4820-B268-A207CCA6F23A@oracle.com> (raw)
In-Reply-To: <20260310164134.GA1410323@nvidia.com>
> On Mar 10, 2026, at 9:41 AM, Jason Gunthorpe <jgg@nvidia.com> wrote:
>
> On Tue, Mar 10, 2026 at 09:31:36AM -0700, Sherry Yang wrote:
>> After enabling CONFIG_GCOV_KERNEL and CONFIG_GCOV_PROFILE_ALL, following
>> build failure is observed:
>>
>> In function 'amdv1pt_install_leaf_entry',
>> inlined from '__do_map_single_page' at drivers/iommu/generic_pt/fmt/../iommu_pt.h:650:3,
>> inlined from '__map_single_page0' at drivers/iommu/generic_pt/fmt/../iommu_pt.h:661:1,
>> inlined from 'pt_descend' at drivers/iommu/generic_pt/fmt/../pt_iter.h:391:9,
>> inlined from '__do_map_single_page' at drivers/iommu/generic_pt/fmt/../iommu_pt.h:657:10,
>> inlined from '__map_single_page1.constprop' at drivers/iommu/generic_pt/fmt/../iommu_pt.h:661:1:
>> ././include/linux/compiler_types.h:706:45: error: call to '__compiletime_assert_71' declared with attribute error: FIELD_PREP: value too large for the field
>> 706 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
>> |
>>
>> ......
>>
>> drivers/iommu/generic_pt/fmt/amdv1.h:220:26: note: in expansion of macro 'FIELD_PREP'
>> 220 | FIELD_PREP(AMDV1PT_FMT_OA,
>> | ^~~~~~~~~~
>>
>> In the path '__do_map_single_page()', level 0 always invokes
>> 'pt_install_leaf_entry(&pts, map->oa, PAGE_SHIFT, …)'. At runtime that
>> lands in the 'if (oasz_lg2 == isz_lg2)' arm of 'amdv1pt_install_leaf_entry()';
>> the contiguous-only 'else' block is unreachable for 4 KiB pages.
>
> I think this is fixed already by
>
> commit 98d5110f90ae0dbc5f2f13f033e06f6d57009e0d
> Author: Jason Gunthorpe <jgg@ziepe.ca>
> Date: Mon Jan 19 20:19:49 2026 -0400
>
> iommupt: Make it clearer to the compiler that pts.level == 0 for single page
>
> Older versions of gcc and clang sometimes get tripped up by the build time
> assertion in FIELD_PREP because they can see that the argument to
> FIELD_PREP is constant but can't see that the if condition protecting it
> is also a constant false.
>
> In file included from <command-line>:
> In function 'amdv1pt_install_leaf_entry',
> inlined from '__do_map_single_page' at drivers/iommu/generic_pt/fmt/../iommu_pt.h:651:3,
> inlined from '__map_single_page0' at drivers/iommu/generic_pt/fmt/../iommu_pt.h:662:1,
> inlined from 'pt_descend' at drivers/iommu/generic_pt/fmt/../pt_iter.h:391:9,
> inlined from '__do_map_single_page' at drivers/iommu/generic_pt/fmt/../iommu_pt.h:658:10,
> inlined from '__map_single_page1.constprop' at drivers/iommu/generic_pt/fmt/../iommu_pt.h:662:1:
>
>
> ??
>
> Jason
Hi Jason,
Unfortunately, I ran into the FIELD_PREP build failure with 98d5110f90ae (“iommupt: Make it clearer to the compiler that pts.level == 0 for single page”) already merged, which means it doesn’t work for me. I noticed you mentioned clang 18 hit the same issue and fixed by the patch. We’re using GCC 14.2.1, looks like GCC still constant-folds the contiguous branch despite the change to pts.level.
Thanks,
Sherry
next prev parent reply other threads:[~2026-03-10 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 16:31 Sherry Yang
2026-03-10 16:41 ` Jason Gunthorpe
2026-03-10 17:17 ` Sherry Yang [this message]
2026-03-10 17:57 ` Jason Gunthorpe
2026-03-25 23:39 ` Sherry Yang
2026-03-26 12:01 ` Jason Gunthorpe
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=62EB69AA-FA3E-4820-B268-A207CCA6F23A@oracle.com \
--to=sherry.yang@oracle.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joerg.roedel@amd.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=vasant.hegde@amd.com \
--cc=will@kernel.org \
/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®