[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180912072541.nagfrr2dgy34szcx@sirius.home.kraxel.org>
Date: Wed, 12 Sep 2018 09:25:41 +0200
From: Gerd Hoffmann <kraxel@...hat.com>
To: Jiandi An <jiandi@....com>
Cc: Dave Airlie <airlied@...il.com>,
dri-devel <dri-devel@...ts.freedesktop.org>,
virtio-dev@...ts.oasis-open.org, Dave Airlie <airlied@...ux.ie>,
"open list:VIRTIO CORE, NET..."
<virtualization@...ts.linux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [virtio-dev] [PATCH 2/2] drm/virtio: add iommu support.
Hi,
> I attempted to fix it in the ttm layer and here is the discussion
> https://lore.kernel.org/lkml/b44280d7-eb13-0996-71f5-3fbdeb466801@amd.com/
>
> The ttm maintainer Christian is suggesting to map and set ttm->pages as decrypted
> right after ttm->pages are allocated.
>
> Just checking with you guys maybe there is a better way to handle this in
> the virtio gpu layer instead of the common ttm layer. Could you guys shine some
> light on this? Thanks.
I think the tty layer is the right place to fix this. virtio just calls
down to ttm for mappings. I think virtio should just hint to ttm using
a flag in some struct, probably ttm_buffer_object or
ttm_mem_type_manager, that the objects need decrypted mappings.
cheers,
Gerd
Powered by blists - more mailing lists