From: Chris Wilson <chris@chris-wilson.co.uk>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/vgem: create a render node for vgem
Date: Mon, 29 Oct 2018 12:08:10 +0000 [thread overview]
Message-ID: <154081489066.14741.11312298085100503233@skylake-alporthouse-com> (raw)
In-Reply-To: <CACvgo52dszJfMe6ThUQ4q4SLwF5nzQjUT0=rVtDZLW76mMmD2Q@mail.gmail.com>
Quoting Emil Velikov (2018-10-29 12:00:17)
> On Fri, 26 Oct 2018 at 15:40, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> >
> > Quoting Daniel Vetter (2018-10-26 14:40:36)
> > > On Fri, Oct 26, 2018 at 01:06:47PM +0100, Emil Velikov wrote:
> > > > From: Emil Velikov <emil.velikov@collabora.com>
> > > >
> > > > VGEM doesn't do anything modeset specific, so in a way exposing a
> > > > primary node is 'wrong'. At the same time, we extensively use if for
> > > > creating dumb buffers, fences, prime fd <> handle imports/exports.
> >
> > What problem are you solving?
> Expose a render node, since only the first instance using the card
> node gets auth.
More accurately, the fence signal/attach do not need DRM_AUTH since they
are operating on resources private to the fd.
-Chris
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-10-29 12:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 12:06 [PATCH] drm/vgem: create a render node for vgem Emil Velikov
2018-10-26 13:40 ` Daniel Vetter
2018-10-26 14:40 ` Chris Wilson
2018-10-29 12:00 ` Emil Velikov
2018-10-29 12:08 ` Chris Wilson [this message]
2018-10-29 12:03 ` Emil Velikov
2018-10-29 13:51 ` Daniel Vetter
2018-10-26 15:55 ` kbuild test robot
2018-11-05 15:30 ` Chris Wilson
2018-11-05 15:35 ` Emil Velikov
2018-11-06 9:05 ` Daniel Vetter
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=154081489066.14741.11312298085100503233@skylake-alporthouse-com \
--to=chris@chris-wilson.co.uk \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.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.