From: Thomas Hellstrom <thellstrom@vmware.com>
To: airlied@gmail.com, airlied@redhat.com
Cc: pv-drivers@vmware.com, Thomas Hellstrom <thellstrom@vmware.com>,
linux-graphics-maintainer@vmware.com,
dri-devel@lists.freedesktop.org
Subject: [PULL] vmwgfx-next request 1
Date: Mon, 13 Jan 2014 12:17:22 +0100 [thread overview]
Message-ID: <1389611842-4659-1-git-send-email-thellstrom@vmware.com> (raw)
Dave,
First 3.14 pull request for vmwgfx,
I hope to be able squeeze in one more with a huge device update,
but lets see what happens.
Anyway, nothing big here, Three more code cleanup patches from Rashika
Kheria, and one TTM/vmwgfx patch from me that tightens security around TTM
objects enough for them to opened using prime objects from render nodes:
Previously any client could access a shared buffer using the "name", also
without actually opening it. Now a reference is required, and for render nodes
such a reference is intended to only be obtainable using a prime fd.
/Thomas
The following changes since commit 859ae233cd0ee76b6143f948ba1cb6b0b4c342f8:
Merge tag 'drm-intel-next-2013-12-13' of git://people.freedesktop.org/~danvet/drm-intel into drm-next (2013-12-23 10:46:07 +1000)
are available in the git repository at:
git://people.freedesktop.org/~thomash/linux tags/vmwgfx-next-2014-01-13
for you to fetch changes up to 94844cf06568d9592f985e4bd0b9d759a56043c6:
drivers: gpu: Mark functions as static in vmwgfx_fence.c (2014-01-08 13:45:56 +0100)
----------------------------------------------------------------
vmwgfx-next 2014-01-13 pull request
----------------------------------------------------------------
Rashika Kheria (3):
drivers: gpu: Mark functions as static in vmwgfx_kms.c
drivers: gpu: Mark functions as static in vmwgfx_buffer.c
drivers: gpu: Mark functions as static in vmwgfx_fence.c
Thomas Hellstrom (1):
drm/ttm: ttm object security fixes for render nodes
drivers/gpu/drm/ttm/ttm_object.c | 90 ++++++++++++++++++-------------
drivers/gpu/drm/vmwgfx/vmwgfx_buffer.c | 8 +--
drivers/gpu/drm/vmwgfx/vmwgfx_fence.c | 9 ++--
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 12 ++---
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c | 3 +-
include/drm/ttm/ttm_object.h | 18 ++++++-
6 files changed, 87 insertions(+), 53 deletions(-)
reply other threads:[~2014-01-13 11:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1389611842-4659-1-git-send-email-thellstrom@vmware.com \
--to=thellstrom@vmware.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=pv-drivers@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).