On Mon, Jun 17, 2024 at 11:07:09AM +0200, Borislav Petkov wrote:
> On Sat, Jun 15, 2024 at 06:25:10PM -0700, Alexey Makhalov wrote:
> > VMWARE_HYPERCALL alternative will not work as intended without
> > VMware guest code initialization.
> >
> > Reported-by: kernel test robot <l...@intel.com>
> > Closes:
> > https://lore.kernel.org/oe-kbuild-all/202406152104.fxakp1mb-...@intel.com/
> > Signed-off-by: Alexey Makhalov <alexey.makha...@broadcom.com>
> > ---
> > drivers/gpu/drm/vmwgfx/Kconfig | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/vmwgfx/Kconfig b/drivers/gpu/drm/vmwgfx/Kconfig
> > index faddae3d6ac2..6f1ac940cbae 100644
> > --- a/drivers/gpu/drm/vmwgfx/Kconfig
> > +++ b/drivers/gpu/drm/vmwgfx/Kconfig
> > @@ -2,7 +2,7 @@
> > config DRM_VMWGFX
> > tristate "DRM driver for VMware Virtual GPU"
> > depends on DRM && PCI && MMU
> > - depends on X86 || ARM64
> > + depends on (X86 && HYPERVISOR_GUEST) || ARM64
> > select DRM_TTM
> > select DRM_TTM_HELPER
> > select MAPPING_DIRTY_HELPERS
> > --
>
> Right, I'll queue this soon but it doesn't reproduce here with gcc-11 or
> gcc-13.
> This must be something gcc-9 specific or so...
Actually, that's a DRM patch.
Folks in To: ok to carry this though the tip tree?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
