All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Hellstrom <thomas@shipmail.org>
To: David Herrmann <dh.herrmann@gmail.com>
Cc: Thomas Hellstrom <thellstrom@vmware.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH RFC] drm: Make the drm_vma_manager authentication mechanism a bit more versatile
Date: Wed, 19 Mar 2014 13:39:57 +0100	[thread overview]
Message-ID: <5329901D.6000508@shipmail.org> (raw)
In-Reply-To: <CANq1E4QOL+wVpBoRxiCgZm6JypO2L3n1mjmScxwx=NuW80S8=g@mail.gmail.com>

On 03/19/2014 12:45 PM, David Herrmann wrote:
> Hi
>
> On Wed, Mar 19, 2014 at 12:33 PM, Thomas Hellstrom
> <thellstrom@vmware.com> wrote:
>> By handing the authentication mechanism tokens in the form of const void
>> pointers instead of struct file pointers, drivers are free to provide whatever
>> file pointers they find appropriate. The pointers are never dereferenced in
>> the drm_vma_manager so that shouldn't be a problem.
>>
>> As an example, the vmwgfx driver would like to provide struct ttm_object_file
>> pointers.
> I guess a "struct file*" pointer in tmm_object_file would be easier,
> but if that reverse dependency is not wanted, I'm fine with that. Just
> make sure you don't use drm_vma_node_verify_access for TTM directly as
> TTM passes in a file pointer.
>
> Reviewed-by: David Herrmann <dh.herrmann@gmail.com>
>
> Thanks
> David

Thanks for reviewing, David.

Although it turned out that I won't be needing this, ATM
since the TTM object mechanism already has a per file object-to-handle
mapping that I could reuse for this.

Thanks,
Thomas

      reply	other threads:[~2014-03-19 12:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19 11:33 [PATCH RFC] drm: Make the drm_vma_manager authentication mechanism a bit more versatile Thomas Hellstrom
2014-03-19 11:45 ` David Herrmann
2014-03-19 12:39   ` Thomas Hellstrom [this message]

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=5329901D.6000508@shipmail.org \
    --to=thomas@shipmail.org \
    --cc=dh.herrmann@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=thellstrom@vmware.com \
    /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.