From: "Keith Packard" <keithp@keithp.com>
To: Daniel Vetter <daniel@ffwll.ch>,
linux-kernel@vger.kernel.org, Dave Airlie <airlied@redhat.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/6] drm: Allow render nodes to query display objects
Date: Thu, 12 Oct 2017 14:04:59 -0700 [thread overview]
Message-ID: <87infk5b7o.fsf@keithp.com> (raw)
In-Reply-To: <20171012194543.vpsaxt4xitv4muz6@phenom.ffwll.local>
[-- Attachment #1: Type: text/plain, Size: 706 bytes --]
Daniel Vetter <daniel@ffwll.ch> writes:
> One more that came up on irc after discussion why this is needed: The
> userspace side using this won't work on split gpus where the render node
> has 0 displays, and hence where you really need to query the compositor
> anyway.
Agreed -- using the X connection to get the information should let this
work on split systems. Within the Vulkan code, I already have to move
objects from the render node to the display node. Hrm. That exposes a
weakness in the kms_display extension I've proposed; that only allows
you to pass a single fd. Passing separate display and render fds through
that interface seems like a pretty useful change.
--
-keith
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-10-12 21:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 0:48 [PATCH 0/6] drm: Add drm mode object leases Keith Packard
2017-10-11 0:48 ` [PATCH 1/6] drm: Pass struct drm_file * to __drm_mode_object_find [v2] Keith Packard
2017-10-11 0:48 ` [PATCH 2/6] drm: Allow render nodes to query display objects Keith Packard
2017-10-12 18:41 ` Daniel Vetter
2017-10-12 19:45 ` Daniel Vetter
2017-10-12 21:04 ` Keith Packard [this message]
2017-10-12 21:02 ` Keith Packard
2017-10-11 0:48 ` [PATCH 3/6] drm: Add new LEASE debug level Keith Packard
2017-10-11 0:48 ` [PATCH 4/6] drm: Add drm_object lease infrastructure [v4] Keith Packard
2017-10-11 0:48 ` [PATCH 5/6] drm: Check mode object lease status in all master ioctl paths [v2] Keith Packard
2017-10-11 0:48 ` [PATCH 6/6] drm: Add four ioctls for managing drm mode object leases [v5] Keith Packard
-- strict thread matches above, loose matches on Subject: below --
2017-10-05 6:13 [PATCH 0/6] drm: Add leases [v4] Keith Packard
2017-10-05 6:13 ` [PATCH 2/6] drm: Allow render nodes to query display objects Keith Packard
2017-07-05 22:24 [PATCH 0/6] drm: Add mode object leases [v3] Keith Packard
2017-07-05 22:24 ` [PATCH 2/6] drm: Allow render nodes to query display objects Keith Packard
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=87infk5b7o.fsf@keithp.com \
--to=keithp@keithp.com \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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