dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Hellstrom <thellstrom@vmware.com>
To: David Herrmann <dh.herrmann@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: [RFC v2 0/3] DRM Anonymous Inodes
Date: Thu, 16 Jan 2014 12:51:25 +0100	[thread overview]
Message-ID: <52D7C7BD.2080601@vmware.com> (raw)
In-Reply-To: <CANq1E4TuDyCSU=KHn-UCtV+dAHqZdOCVjoFHUM_ximHDuDZDgw@mail.gmail.com>

David,

I haven't had time to test on vmwgfx yet, but looking through the code
it looks good to me.

Acked-by: Thomas Hellstrom <thellstrom@vmware.com>

/Thomas

On 01/16/2014 12:29 PM, David Herrmann wrote:
> Hi
>
> On Fri, Jan 3, 2014 at 3:41 PM, David Herrmann <dh.herrmann@gmail.com> wrote:
>> Hi
>>
>> With 3.13-rc1 the required VFS core changes for anonymous backing inodes in DRM
>> got merged. This series reworks the previous patches (I think from early
>> August '13) and finally replaces the ugly drm_device->dev_mapping hack.
>>
>> The patches should be fairly obvious. As I currently only have nouveau here, I'd
>> be happy to get some more testers with other drivers.
>>
>> Patch #1 adds an internal private mount point to DRM core.
>> Patch #2 replaces ->dev_mapping with a private anonymous inode for each device.
>> Patch #3 removes the delayed dev_mapping initialization in TTM.
>>
>> The internal mnt-point is based on fs/aio.c and fs/anon_inode.c which do the
>> same. It's not clear to me why we cannot share the mnt-point between all these,
>> but Al Viro made clear that he will reject any patches on anon_inode.c which do
>> that. So lets follow his recommendation and use our own internal mnt-point.
> Also tested on i915 ivb now (before: nouveau+TTM). I think this is
> ready for 3.14 if nobody finds any issues.
>
> Thanks
> David
>
>> Thanks
>> David
>>
>> David Herrmann (3):
>>   drm: add pseudo filesystem for shared inodes
>>   drm: use anon-inode instead of relying on cdevs
>>   drm: init TTM dev_mapping in ttm_bo_device_init()
>>
>>  drivers/gpu/drm/ast/ast_ttm.c          |  5 +++--
>>  drivers/gpu/drm/cirrus/cirrus_ttm.c    |  5 +++--
>>  drivers/gpu/drm/drm_drv.c              | 37 ++++++++++++++++++++++++++++++++++
>>  drivers/gpu/drm/drm_fops.c             | 25 +++--------------------
>>  drivers/gpu/drm/drm_stub.c             | 12 ++++++++++-
>>  drivers/gpu/drm/i915/i915_gem.c        |  3 ++-
>>  drivers/gpu/drm/mgag200/mgag200_ttm.c  |  5 +++--
>>  drivers/gpu/drm/nouveau/nouveau_gem.c  |  2 --
>>  drivers/gpu/drm/nouveau/nouveau_ttm.c  |  4 +++-
>>  drivers/gpu/drm/omapdrm/omap_gem.c     | 34 +++++++++++++++----------------
>>  drivers/gpu/drm/qxl/qxl_object.c       |  2 --
>>  drivers/gpu/drm/qxl/qxl_ttm.c          |  6 +++---
>>  drivers/gpu/drm/radeon/radeon_object.c |  1 -
>>  drivers/gpu/drm/radeon/radeon_ttm.c    |  5 +++--
>>  drivers/gpu/drm/ttm/ttm_bo.c           |  3 ++-
>>  drivers/gpu/drm/vmwgfx/vmwgfx_drv.c    |  5 +++--
>>  include/drm/drmP.h                     |  3 ++-
>>  include/drm/drm_vma_manager.h          |  6 +++---
>>  include/drm/ttm/ttm_bo_driver.h        |  2 ++
>>  19 files changed, 100 insertions(+), 65 deletions(-)
>>
>> --
>> 1.8.5.2
>>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2014-01-16 11:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03 14:41 [RFC v2 0/3] DRM Anonymous Inodes David Herrmann
2014-01-03 14:41 ` [RFC v2 1/3] drm: add pseudo filesystem for shared inodes David Herrmann
2014-01-03 14:41 ` [RFC v2 2/3] drm: use anon-inode instead of relying on cdevs David Herrmann
2014-01-03 14:41 ` [RFC v2 3/3] drm: init TTM dev_mapping in ttm_bo_device_init() David Herrmann
2014-01-16 11:29 ` [RFC v2 0/3] DRM Anonymous Inodes David Herrmann
2014-01-16 11:51   ` Thomas Hellstrom [this message]
2014-01-20  2:00     ` Dave Airlie
2014-01-20 13:55       ` David Herrmann

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=52D7C7BD.2080601@vmware.com \
    --to=thellstrom@vmware.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dh.herrmann@gmail.com \
    --cc=dri-devel@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