On Wed, Nov 29, 2023, Michael Ellerman wrote:
> Sean Christopherson <seanjc@xxxxxxxxxx> writes:
> > On Fri, Nov 10, 2023, Michael Ellerman wrote:
> >> Jason Gunthorpe <jgg@xxxxxxxxxx> writes:
> >> > There are a bunch of reported randconfig failures now because of this,
> >> > something like:
> >> >
> >> >>> arch/powerpc/kvm/../../../virt/kvm/vfio.c:89:7: warning: attribute declaration must precede definition [-Wignored-attributes]
> >> > fn = symbol_get(vfio_file_iommu_group);
> >> > ^
> >> > include/linux/module.h:805:60: note: expanded from macro 'symbol_get'
> >> > #define symbol_get(x) ({ extern typeof(x) x __attribute__((weak,visibility("hidden"))); &(x); })
> >> >
> >> > It happens because the arch forces KVM_VFIO without knowing if VFIO is
> >> > even enabled.
> >>
> >> This is still breaking some builds. Can we get this fix in please?
> >>
> >> cheers
> >>
> >> > Split the kconfig so the arch selects the usual HAVE_KVM_ARCH_VFIO and
> >> > then KVM_VFIO is only enabled if the arch wants it and VFIO is turned on.
> >
> > Heh, so I was trying to figure out why things like vfio_file_set_kvm() aren't
> > problematic, i.e. why the existing mess didn't cause failures. I can't repro the
> > warning (requires clang-16?), but IIUC the reason only the group code is problematic
> > is that vfio.h creates a stub for vfio_file_iommu_group() and thus there's no symbol,
> > whereas vfio.h declares vfio_file_set_kvm() unconditionally.
>
> That warning I'm unsure about.
Ah, it's the same warning, I just missed the CONFIG_MODULES=n requirement.
