From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/vgem: Replace vgem_object_funcs with the common drm shmem helper
Date: Mon, 12 Oct 2020 11:49:03 +0100 [thread overview]
Message-ID: <160249974352.30484.764236348954464063@build.alporthouse.com> (raw)
In-Reply-To: <CAKMK7uG51_t9988vTen2rK+gbwwjN0tLphpVhMd2nbsFTNi+GQ@mail.gmail.com>
Quoting Daniel Vetter (2020-10-09 17:16:06)
> On Fri, Oct 9, 2020 at 12:21 PM Chris Wilson <chris@chris-wilson.co.uk> wrote:
> >
> > vgem is a minimalistic driver that provides shmemfs objects to
> > userspace that may then be used as an in-memory surface and transported
> > across dma-buf to other drivers. Since it's introduction,
> > drm_gem_shmem_helper now provides the same shmemfs facilities and so we
> > can trim vgem to wrap the helper.
> >
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > ---
> > drivers/gpu/drm/Kconfig | 1 +
> > drivers/gpu/drm/vgem/vgem_drv.c | 281 ++------------------------------
> > drivers/gpu/drm/vgem/vgem_drv.h | 11 --
> > 3 files changed, 13 insertions(+), 280 deletions(-)
>
> Nice diffstat :-)
>
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Unfortunately I had to drop the drm_gem_prime_mmap() since the existing
expectation is that we hand the faulthandler off to shmemfs so we can
release the module while the memory is exported. The other issue happens
to be for arch/x86 where just setting PAT=WC on the PTE does not flush
the cache for that page, and the CPU will preferentially use the cache.
That has caught us out more than once.
-Chris
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/vgem: Replace vgem_object_funcs with the common drm shmem helper
Date: Mon, 12 Oct 2020 11:49:03 +0100 [thread overview]
Message-ID: <160249974352.30484.764236348954464063@build.alporthouse.com> (raw)
In-Reply-To: <CAKMK7uG51_t9988vTen2rK+gbwwjN0tLphpVhMd2nbsFTNi+GQ@mail.gmail.com>
Quoting Daniel Vetter (2020-10-09 17:16:06)
> On Fri, Oct 9, 2020 at 12:21 PM Chris Wilson <chris@chris-wilson.co.uk> wrote:
> >
> > vgem is a minimalistic driver that provides shmemfs objects to
> > userspace that may then be used as an in-memory surface and transported
> > across dma-buf to other drivers. Since it's introduction,
> > drm_gem_shmem_helper now provides the same shmemfs facilities and so we
> > can trim vgem to wrap the helper.
> >
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > ---
> > drivers/gpu/drm/Kconfig | 1 +
> > drivers/gpu/drm/vgem/vgem_drv.c | 281 ++------------------------------
> > drivers/gpu/drm/vgem/vgem_drv.h | 11 --
> > 3 files changed, 13 insertions(+), 280 deletions(-)
>
> Nice diffstat :-)
>
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Unfortunately I had to drop the drm_gem_prime_mmap() since the existing
expectation is that we hand the faulthandler off to shmemfs so we can
release the module while the memory is exported. The other issue happens
to be for arch/x86 where just setting PAT=WC on the PTE does not flush
the cache for that page, and the CPU will preferentially use the cache.
That has caught us out more than once.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-10-12 10:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 10:21 [PATCH] drm/vgem: Replace vgem_object_funcs with the common drm shmem helper Chris Wilson
2020-10-09 10:21 ` [Intel-gfx] " Chris Wilson
2020-10-09 11:40 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-10-09 12:04 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-10-09 16:16 ` [Intel-gfx] [PATCH] " Daniel Vetter
2020-10-09 16:16 ` Daniel Vetter
2020-10-09 22:43 ` Daniel Vetter
2020-10-09 22:43 ` Daniel Vetter
2020-10-12 10:49 ` Chris Wilson [this message]
2020-10-12 10:49 ` Chris Wilson
2020-10-12 13:55 ` Daniel Vetter
2020-10-12 13:55 ` Daniel Vetter
2020-10-12 14:01 ` Chris Wilson
2020-10-12 14:01 ` Chris Wilson
2020-10-12 14:12 ` Daniel Vetter
2020-10-12 14:12 ` Daniel Vetter
2020-10-12 14:17 ` Chris Wilson
2020-10-12 14:17 ` Chris Wilson
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=160249974352.30484.764236348954464063@build.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.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: link
Be 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.