[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0a29389e-8ba2-48c5-bb26-381de58a62fb@broadcom.com>
Date: Mon, 17 Jun 2024 13:51:23 -0700
From: Alexey Makhalov <alexey.makhalov@...adcom.com>
To: Borislav Petkov <bp@...en8.de>
Cc: linux-kernel@...r.kernel.org, bcm-kernel-feedback-list@...adcom.com,
lkp@...el.com, zack.rusin@...adcom.com, dri-devel@...ts.freedesktop.org,
daniel@...ll.ch, airlied@...il.com, tzimmermann@...e.de, mripard@...nel.org,
maarten.lankhorst@...ux.intel.com, linux-iio@...r.kernel.org,
jic23@...nel.org, lars@...afoo.de, nuno.sa@...log.com,
dragos.bogdan@...log.com, anshulusr@...il.com, andrea.collamati@...il.com,
oe-kbuild-all@...ts.linux.dev, x86@...nel.org
Subject: Re: [PATCH 1/2] drm/vmwgfx: Fix missing HYPERVISOR_GUEST dependency
On 6/17/24 2:07 AM, 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 <lkp@...el.com>
>> Closes: https://lore.kernel.org/oe-kbuild-all/202406152104.FxakP1MB-lkp@intel.com/
>> Signed-off-by: Alexey Makhalov <alexey.makhalov@...adcom.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...
>
Not really a gcc related, but the matter of a config file. It is
reproducible if CONFIG_HYPERVISOR_GUEST not set, but
CONFIG_DRM_VMWGFX=y. And this combination was allowed before the fix.
Regards,
--Alexey
Powered by blists - more mailing lists