Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: [PATCH 0/2] drm: mmap fixups
Date: Thu, 21 Nov 2019 11:38:05 +0100	[thread overview]
Message-ID: <20191121103807.18424-1-kraxel@redhat.com> (raw)

Tested on qemu, with bochs (vram helpers) and cirrus (shmem helpers).
Cc'ing intel-gfx for CI coverage.

Gerd Hoffmann (2):
  drm: call drm_gem_object_funcs.mmap with fake offset
  drm: share address space for dma bufs

 include/drm/drm_gem.h                  | 4 +---
 drivers/gpu/drm/drm_gem.c              | 3 ---
 drivers/gpu/drm/drm_gem_shmem_helper.c | 3 +++
 drivers/gpu/drm/drm_prime.c            | 7 ++++++-
 drivers/gpu/drm/ttm/ttm_bo_vm.c        | 7 -------
 5 files changed, 10 insertions(+), 14 deletions(-)

-- 
2.18.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@redhat.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: [Intel-gfx] [PATCH 0/2] drm: mmap fixups
Date: Thu, 21 Nov 2019 11:38:05 +0100	[thread overview]
Message-ID: <20191121103807.18424-1-kraxel@redhat.com> (raw)
Message-ID: <20191121103805.fHxFNz2wE69QfphOQ6q7-ZFkK9DYJkjkdRaHDQM5iIk@z> (raw)

Tested on qemu, with bochs (vram helpers) and cirrus (shmem helpers).
Cc'ing intel-gfx for CI coverage.

Gerd Hoffmann (2):
  drm: call drm_gem_object_funcs.mmap with fake offset
  drm: share address space for dma bufs

 include/drm/drm_gem.h                  | 4 +---
 drivers/gpu/drm/drm_gem.c              | 3 ---
 drivers/gpu/drm/drm_gem_shmem_helper.c | 3 +++
 drivers/gpu/drm/drm_prime.c            | 7 ++++++-
 drivers/gpu/drm/ttm/ttm_bo_vm.c        | 7 -------
 5 files changed, 10 insertions(+), 14 deletions(-)

-- 
2.18.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2019-11-21 10:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21 10:38 Gerd Hoffmann [this message]
2019-11-21 10:38 ` [Intel-gfx] [PATCH 0/2] drm: mmap fixups Gerd Hoffmann
2019-11-21 10:38 ` [PATCH 1/2] drm: call drm_gem_object_funcs.mmap with fake offset Gerd Hoffmann
2019-11-21 10:38   ` [Intel-gfx] " Gerd Hoffmann
2019-11-21 13:52   ` Daniel Vetter
2019-11-21 13:52     ` [Intel-gfx] " Daniel Vetter
2019-11-21 13:56     ` Daniel Vetter
2019-11-21 13:56       ` [Intel-gfx] " Daniel Vetter
2019-11-21 10:38 ` [PATCH 2/2] drm: share address space for dma bufs Gerd Hoffmann
2019-11-21 10:38   ` [Intel-gfx] " Gerd Hoffmann
2019-11-21 13:55   ` Daniel Vetter
2019-11-21 13:55     ` [Intel-gfx] " Daniel Vetter
2019-11-21 16:42   ` Ruhl, Michael J
2019-11-21 16:42     ` Ruhl, Michael J
2019-11-22  6:32     ` Gerd Hoffmann
2019-11-22  6:32       ` Gerd Hoffmann
2019-11-21 13:04 ` ✓ Fi.CI.BAT: success for drm: mmap fixups Patchwork
2019-11-21 13:04   ` [Intel-gfx] " Patchwork

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=20191121103807.18424-1-kraxel@redhat.com \
    --to=kraxel@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox