From: Dmitry Osipenko <dmitry.osipenko@collabora.com> To: "Christian König" <ckoenig.leichtzumerken@gmail.com>, "Rob Clark" <robdclark@gmail.com>, "Christian König" <christian.koenig@amd.com> Cc: "David Airlie" <airlied@linux.ie>, "Gerd Hoffmann" <kraxel@redhat.com>, "Gurchetan Singh" <gurchetansingh@chromium.org>, "Chia-I Wu" <olvaffe@gmail.com>, "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>, "Maxime Ripard" <mripard@kernel.org>, "Thomas Zimmermann" <tzimmermann@suse.de>, "Emil Velikov" <emil.l.velikov@gmail.com>, "Thomas Hellström" <thomas_os@shipmail.org>, "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>, dri-devel <dri-devel@lists.freedesktop.org>, "open list:VIRTIO GPU DRIVER" <virtualization@lists.linux-foundation.org>, linux-tegra@vger.kernel.org, "Dmitry Osipenko" <digetx@gmail.com>, kernel@collabora.com, "Daniel Vetter" <daniel@ffwll.ch> Subject: Re: [PATCH v8 2/2] drm/gem: Don't map imported GEMs Date: Tue, 16 Aug 2022 22:55:52 +0300 [thread overview] Message-ID: <cf8cd8da-08d2-5e70-a239-2a67da37c9ea@collabora.com> (raw) In-Reply-To: <2ce5ff0a-9ab2-d146-04db-487a64714fce@gmail.com> On 8/16/22 15:03, Christian König wrote: > Am 16.08.22 um 13:44 schrieb Dmitry Osipenko: >> [SNIP] >>> The other complication I noticed is that we don't seem to keep around >>> the fd after importing to a GEM handle. And I could imagine that >>> doing so could cause issues with too many fd's. So I guess the best >>> thing is to keep the status quo and let drivers that cannot mmap >>> imported buffers just fail mmap? >> That actually should be all the drivers excluding those that use >> DRM-SHMEM because only DRM-SHMEM uses dma_buf_mmap(), that's why it >> works for Panfrost. I'm pretty sure mmaping of imported GEMs doesn't >> work for the MSM driver, isn't it? >> >> Intel and AMD drivers don't allow to map the imported dma-bufs. Both >> refuse to do the mapping. >> >> Although, AMDGPU "succeeds" to do the mapping using >> AMDGPU_GEM_DOMAIN_GTT, but then touching the mapping causes bus fault, >> hence mapping actually fails. I think it might be the AMDGPU >> driver/libdrm bug, haven't checked yet. > > That's then certainly broken somehow. Amdgpu should nerve ever have > allowed to mmap() imported DMA-bufs and the last time I check it didn't. I'll take a closer look. So far I can only tell that it's a kernel driver issue because once I re-applied this "Don't map imported GEMs" patch, AMDGPU began to refuse mapping AMDGPU_GEM_DOMAIN_GTT. >> So we're back to the point that neither of DRM drivers need to map >> imported dma-bufs and this was never tested. In this case this patch is >> valid, IMO. Actually, I'm now looking at Etnaviv and Nouveau and seems they should map imported dma-buf properly. I know that people ran Android on Etnaviv. So maybe devices with a separated GPU/display need to map imported display BO for Android support. Wish somebody who ran Android on one of these devices using upstream drivers could give a definitive answer. I may try to test Nouveau later on. -- Best regards, Dmitry
WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Osipenko <dmitry.osipenko@collabora.com> To: "Christian König" <ckoenig.leichtzumerken@gmail.com>, "Rob Clark" <robdclark@gmail.com>, "Christian König" <christian.koenig@amd.com> Cc: kernel@collabora.com, dri-devel <dri-devel@lists.freedesktop.org>, "David Airlie" <airlied@linux.ie>, "Emil Velikov" <emil.l.velikov@gmail.com>, "Thomas Hellström" <thomas_os@shipmail.org>, "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>, "Gurchetan Singh" <gurchetansingh@chromium.org>, "Gerd Hoffmann" <kraxel@redhat.com>, "Thomas Zimmermann" <tzimmermann@suse.de>, linux-tegra@vger.kernel.org, "Dmitry Osipenko" <digetx@gmail.com>, "open list:VIRTIO GPU DRIVER" <virtualization@lists.linux-foundation.org> Subject: Re: [PATCH v8 2/2] drm/gem: Don't map imported GEMs Date: Tue, 16 Aug 2022 22:55:52 +0300 [thread overview] Message-ID: <cf8cd8da-08d2-5e70-a239-2a67da37c9ea@collabora.com> (raw) In-Reply-To: <2ce5ff0a-9ab2-d146-04db-487a64714fce@gmail.com> On 8/16/22 15:03, Christian König wrote: > Am 16.08.22 um 13:44 schrieb Dmitry Osipenko: >> [SNIP] >>> The other complication I noticed is that we don't seem to keep around >>> the fd after importing to a GEM handle. And I could imagine that >>> doing so could cause issues with too many fd's. So I guess the best >>> thing is to keep the status quo and let drivers that cannot mmap >>> imported buffers just fail mmap? >> That actually should be all the drivers excluding those that use >> DRM-SHMEM because only DRM-SHMEM uses dma_buf_mmap(), that's why it >> works for Panfrost. I'm pretty sure mmaping of imported GEMs doesn't >> work for the MSM driver, isn't it? >> >> Intel and AMD drivers don't allow to map the imported dma-bufs. Both >> refuse to do the mapping. >> >> Although, AMDGPU "succeeds" to do the mapping using >> AMDGPU_GEM_DOMAIN_GTT, but then touching the mapping causes bus fault, >> hence mapping actually fails. I think it might be the AMDGPU >> driver/libdrm bug, haven't checked yet. > > That's then certainly broken somehow. Amdgpu should nerve ever have > allowed to mmap() imported DMA-bufs and the last time I check it didn't. I'll take a closer look. So far I can only tell that it's a kernel driver issue because once I re-applied this "Don't map imported GEMs" patch, AMDGPU began to refuse mapping AMDGPU_GEM_DOMAIN_GTT. >> So we're back to the point that neither of DRM drivers need to map >> imported dma-bufs and this was never tested. In this case this patch is >> valid, IMO. Actually, I'm now looking at Etnaviv and Nouveau and seems they should map imported dma-buf properly. I know that people ran Android on Etnaviv. So maybe devices with a separated GPU/display need to map imported display BO for Android support. Wish somebody who ran Android on one of these devices using upstream drivers could give a definitive answer. I may try to test Nouveau later on. -- Best regards, Dmitry
next prev parent reply other threads:[~2022-08-16 19:56 UTC|newest] Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-01 9:02 [PATCH v8 0/2] DRM GEM fixes Dmitry Osipenko 2022-07-01 9:02 ` Dmitry Osipenko 2022-07-01 9:02 ` [PATCH v8 1/2] drm/gem: Properly annotate WW context on drm_gem_lock_reservations() error Dmitry Osipenko 2022-07-01 9:02 ` Dmitry Osipenko 2022-07-05 11:33 ` Christian König 2022-07-05 11:33 ` Christian König 2022-07-05 11:33 ` Christian König via Virtualization 2022-08-09 16:44 ` Daniel Vetter 2022-08-09 16:44 ` Daniel Vetter 2022-08-09 16:44 ` Daniel Vetter 2022-08-10 6:52 ` Christian König 2022-08-10 6:52 ` Christian König via Virtualization 2022-08-10 8:33 ` Daniel Vetter 2022-08-10 8:33 ` Daniel Vetter 2022-08-10 8:33 ` Daniel Vetter 2022-08-10 9:04 ` Christian König via Virtualization 2022-08-10 9:04 ` Christian König 2022-08-10 9:04 ` Christian König 2022-07-01 9:02 ` [PATCH v8 2/2] drm/gem: Don't map imported GEMs Dmitry Osipenko 2022-07-01 9:02 ` Dmitry Osipenko 2022-07-05 11:39 ` Christian König 2022-07-05 11:39 ` Christian König 2022-07-05 11:39 ` Christian König via Virtualization 2022-07-05 21:48 ` Rob Clark 2022-07-05 21:48 ` Rob Clark 2022-07-05 21:48 ` Rob Clark 2022-07-06 7:02 ` Dmitry Osipenko 2022-07-06 7:02 ` Dmitry Osipenko 2022-08-10 11:47 ` Daniel Vetter 2022-08-10 11:47 ` Daniel Vetter 2022-08-10 11:47 ` Daniel Vetter 2022-08-10 15:08 ` Rob Clark 2022-08-10 15:08 ` Rob Clark 2022-08-10 15:08 ` Rob Clark 2022-08-10 19:26 ` Dmitry Osipenko 2022-08-10 19:26 ` Dmitry Osipenko 2022-08-10 22:03 ` Rob Clark 2022-08-10 22:03 ` Rob Clark 2022-08-10 22:03 ` Rob Clark 2022-08-10 22:23 ` Dmitry Osipenko 2022-08-10 22:23 ` Dmitry Osipenko 2022-08-10 23:19 ` Rob Clark 2022-08-10 23:19 ` Rob Clark 2022-08-10 23:19 ` Rob Clark 2022-08-12 11:26 ` Dmitry Osipenko 2022-08-12 11:26 ` Dmitry Osipenko 2022-08-12 14:57 ` Rob Clark 2022-08-12 14:57 ` Rob Clark 2022-08-12 14:57 ` Rob Clark 2022-08-12 15:01 ` Rob Clark 2022-08-12 15:01 ` Rob Clark 2022-08-12 15:01 ` Rob Clark 2022-08-16 11:44 ` Dmitry Osipenko 2022-08-16 11:44 ` Dmitry Osipenko 2022-08-16 11:52 ` Dmitry Osipenko 2022-08-16 11:52 ` Dmitry Osipenko 2022-08-16 12:03 ` Christian König 2022-08-16 12:03 ` Christian König 2022-08-16 12:03 ` Christian König 2022-08-16 19:55 ` Dmitry Osipenko [this message] 2022-08-16 19:55 ` Dmitry Osipenko 2022-08-22 17:26 ` Dmitry Osipenko 2022-08-22 17:26 ` Dmitry Osipenko 2022-08-23 10:01 ` Christian König 2022-08-23 10:01 ` Christian König 2022-08-23 10:01 ` Christian König 2022-08-23 16:47 ` Rob Clark 2022-08-23 16:47 ` Rob Clark 2022-08-23 16:47 ` Rob Clark 2022-09-07 10:25 ` Dmitry Osipenko 2022-09-07 10:25 ` Dmitry Osipenko 2022-09-11 18:00 ` Rob Clark 2022-09-11 18:00 ` Rob Clark 2022-09-11 18:00 ` Rob Clark 2022-08-16 22:18 ` Rob Clark 2022-08-16 22:18 ` Rob Clark 2022-08-16 22:18 ` Rob Clark 2022-08-10 19:27 ` Dmitry Osipenko 2022-07-22 11:49 ` [PATCH v8 0/2] DRM GEM fixes Dmitry Osipenko 2022-07-22 11:49 ` Dmitry Osipenko
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=cf8cd8da-08d2-5e70-a239-2a67da37c9ea@collabora.com \ --to=dmitry.osipenko@collabora.com \ --cc=airlied@linux.ie \ --cc=christian.koenig@amd.com \ --cc=ckoenig.leichtzumerken@gmail.com \ --cc=daniel@ffwll.ch \ --cc=digetx@gmail.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=emil.l.velikov@gmail.com \ --cc=gurchetansingh@chromium.org \ --cc=kernel@collabora.com \ --cc=kraxel@redhat.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-tegra@vger.kernel.org \ --cc=maarten.lankhorst@linux.intel.com \ --cc=mripard@kernel.org \ --cc=olvaffe@gmail.com \ --cc=robdclark@gmail.com \ --cc=thomas_os@shipmail.org \ --cc=tzimmermann@suse.de \ --cc=virtualization@lists.linux-foundation.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.