From: Keith Packard <keithp@keithp.com> To: linux-kernel@vger.kernel.org, Dave Airlie <airlied@redhat.com>, Daniel Vetter <daniel@ffwll.ch> Cc: Keith Packard <keithp@keithp.com>, dri-devel@lists.freedesktop.org Subject: [PATCH 0/6] drm: Add mode object leases [v3] Date: Wed, 5 Jul 2017 15:24:00 -0700 [thread overview] Message-ID: <20170705222406.28124-1-keithp@keithp.com> (raw) Here's a third version of my DRM mode object leases series. Since v2: * Add revocation. This allows leases to be effectively revoked by removing all of the objects they have access to. The lease itself hangs around as it's hanging off a file. * Allow non-master files to look at all DRM mode objects. This lets the Vulkan code provide information about the display environment before the lease is created. * Free the leases IDR when the master is destroyed. Just a bug fix. * _drm_lease_held should look at lessees, not lessor. Just a bug fix. I've also rebased it to a more recent version of Dave's drm-next branch. With this and my CRTC-id based vblank series (posted separately), I'm now running "real" applications on a leased output and can fully support the following Vulkan extensions: EXT_direct_mode_display EXT_acquire_xlib_display EXT_display_surface_counter KEITHP_kms_display -keith
WARNING: multiple messages have this Message-ID (diff)
From: Keith Packard <keithp@keithp.com> To: linux-kernel@vger.kernel.org, Dave Airlie <airlied@redhat.com>, Daniel Vetter <daniel@ffwll.ch> Cc: Keith Packard <keithp@keithp.com>, dri-devel@lists.freedesktop.org Subject: [PATCH 0/6] drm: Add mode object leases [v3] Date: Wed, 5 Jul 2017 15:24:00 -0700 [thread overview] Message-ID: <20170705222406.28124-1-keithp@keithp.com> (raw) Here's a third version of my DRM mode object leases series. Since v2: * Add revocation. This allows leases to be effectively revoked by removing all of the objects they have access to. The lease itself hangs around as it's hanging off a file. * Allow non-master files to look at all DRM mode objects. This lets the Vulkan code provide information about the display environment before the lease is created. * Free the leases IDR when the master is destroyed. Just a bug fix. * _drm_lease_held should look at lessees, not lessor. Just a bug fix. I've also rebased it to a more recent version of Dave's drm-next branch. With this and my CRTC-id based vblank series (posted separately), I'm now running "real" applications on a leased output and can fully support the following Vulkan extensions: EXT_direct_mode_display EXT_acquire_xlib_display EXT_display_surface_counter KEITHP_kms_display -keith _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-07-05 22:24 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-07-05 22:24 Keith Packard [this message] 2017-07-05 22:24 ` [PATCH 0/6] drm: Add mode object leases [v3] Keith Packard 2017-07-05 22:24 ` [PATCH 1/6] drm: Pass struct drm_file * to __drm_mode_object_find Keith Packard 2017-07-05 22:24 ` Keith Packard 2017-07-05 22:24 ` [PATCH 2/6] drm: Allow render nodes to query display objects Keith Packard 2017-07-05 22:24 ` Keith Packard 2017-07-05 22:24 ` [PATCH 3/6] drm: Add new LEASE debug level Keith Packard 2017-07-05 22:24 ` Keith Packard 2017-07-05 22:24 ` [PATCH 4/6] drm: Add drm_object lease infrastructure [v3] Keith Packard 2017-10-05 3:55 ` Dave Airlie 2017-10-05 3:55 ` Dave Airlie 2017-07-05 22:24 ` [PATCH 5/6] drm: Check mode object lease status in all master ioctl paths [v2] Keith Packard 2017-07-05 22:24 ` Keith Packard 2017-07-05 22:24 ` [PATCH 6/6] drm: Add four ioctls for managing drm mode object leases [v3] Keith Packard 2017-07-05 22:24 ` Keith Packard 2017-07-06 0:42 ` Dave Airlie 2017-07-06 0:42 ` Dave Airlie 2017-07-06 3:38 ` Keith Packard 2017-07-06 3:38 ` Keith Packard 2017-10-05 3:17 ` Dave Airlie 2017-10-05 3:24 ` Dave Airlie 2017-10-05 3:24 ` Dave Airlie 2017-10-05 3:37 ` Dave Airlie 2017-10-05 3:37 ` Dave Airlie 2017-10-05 6:23 ` Keith Packard 2017-10-05 6:23 ` 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=20170705222406.28124-1-keithp@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: linkBe 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.