[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAK8P3a05c8nyYXwy0L65vZaAofdjD3DzuKiyNVsUVeWWQaQDEA@mail.gmail.com>
Date: Thu, 11 Mar 2021 11:02:44 +0100
From: Arnd Bergmann <arnd@...nel.org>
To: Christian König <christian.koenig@....com>
Cc: Alex Deucher <alexdeucher@...il.com>,
Jean-Philippe Brucker <jean-philippe@...aro.org>,
Felix Kuehling <felix.kuehling@....com>,
David Airlie <airlied@...ux.ie>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
dri-devel <dri-devel@...ts.freedesktop.org>,
"open list:IOMMU DRIVERS" <iommu@...ts.linux-foundation.org>,
amd-gfx list <amd-gfx@...ts.freedesktop.org>,
"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@....com>,
Alex Deucher <alexander.deucher@....com>,
Will Deacon <will@...nel.org>
Subject: Re: [PATCH 1/1] drm/amdkfd: fix build error with AMD_IOMMU_V2=m
On Tue, Mar 9, 2021 at 7:34 PM Christian König <christian.koenig@....com> wrote:
> Am 09.03.21 um 18:59 schrieb Alex Deucher:
>
> There has been quite some effort for this already for generic PASID
> interface etc.. But it looks like that effort is stalled by now.
>
> Anyway at least I'm perfectly fine to have the IOMMUv2 || !IOMMUv2
> dependency on the core amdgpu driver for x86.
>
> That should solve the build problem at hand quite nicely.
Right, that sounds better than the IS_REACHABLE() hack, and would fix
the immediate build regression until the driver is changed to use the proper
IOMMU interfaces.
Arnd
Powered by blists - more mailing lists