History log of /external/libdrm/nouveau/pushbuf.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
4283e3f656541c4533c89b2cdc501aa6dc7da3dc 24-Nov-2015 Ben Skeggs <bskeggs@redhat.com> nouveau: make use of nouveau_drm::fd instead of nouveau_device::fd

The latter is deprecated, and will not be valid for newer clients.

v2.
- split out nouveau_object_find removal

Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
Tested-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>
Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com>
/external/libdrm/nouveau/pushbuf.c
203983f842a889b279698fdea46e83ee4450a1db 22-Jun-2015 Ilia Mirkin <imirkin@alum.mit.edu> nouveau: add asserts to make sure krefs are there

This should help catch odd bugs at the callsites rather than much later
on with completely bogus bo indices.

Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
/external/libdrm/nouveau/pushbuf.c
0f8da82500ec542e269092c0718479e25eaff5f6 31-Mar-2015 Emil Velikov <emil.l.velikov@gmail.com> drm: remove drm_public macro

Some compilers (like the Oracle Studio), require that the function
declaration must be annotated with the same visibility attribute as the
definition. As annotating functions with drm_public is no longer
required just remove the macro.

Cc: Ben Skeggs <bskeggs@redhat.com>
Cc: Damien Lespiau <damien.lespiau@intel.com>
Cc: Maarten Lankhorst <maarten.lankhorst@canonical.com>
Cc: Michel Dänzer <michel.daenzer@amd.com>
Cc: Rob Clark <robdclark@gmail.com>
Cc: Thierry Reding <treding@nvidia.com>
Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
/external/libdrm/nouveau/pushbuf.c
56c4857f1763b40e566839bdc6fa14f873baf9b8 31-Jul-2014 Maarten Lankhorst <maarten.lankhorst@canonical.com> nouveau: Only export public functions.

This hides all the abi16_* functions and the nouveau_debug variable,
they should have been private to begin with.

Signed-off-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com>
/external/libdrm/nouveau/pushbuf.c
482abbfafb56cbceaf5355c026434e638cddd0f1 07-Nov-2013 Maarten Lankhorst <maarten.lankhorst@canonical.com> nouveau: prevent undefined behavior in nouveau_pushbuf_reloc with gcc-4.8

Reported-by: ronald645@gmail.com
Bisected-by (gcc): Andreas Radke <a.radke@arcor.de>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=71116
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
/external/libdrm/nouveau/pushbuf.c
f92d7969bf6ba636d193423cf2388956badde3ff 03-Mar-2013 Marcin Slusarz <marcin.slusarz@gmail.com> nouveau: add a way to override single pushbuffer memory limits

Currently single pushbuffer can take up to 80% of VRAM and 80% of GART.
As this value seems to be arbitrary (and user may need to set it differently)
this patch adds support for 2 environment variables:
NOUVEAU_LIBDRM_VRAM_LIMIT_PERCENT (default 80)
NOUVEAU_LIBDRM_GART_LIMIT_PERCENT (default 80)
which will let users override pushbuffer VRAM/GART limits.

Signed-off-by: Marcin Slusarz <marcin.slusarz@gmail.com>
/external/libdrm/nouveau/pushbuf.c
284421a56921337aaabcec7ad2790034249c7b31 03-Mar-2013 Marcin Slusarz <marcin.slusarz@gmail.com> nouveau: return error from pushbuf_validate

Signed-off-by: Marcin Slusarz <marcin.slusarz@gmail.com>
/external/libdrm/nouveau/pushbuf.c
891517f5111cd82909906d5e8ee0299db0d46762 07-Jan-2013 Ben Skeggs <bskeggs@redhat.com> nouveau: disallow pushbuf BOs in multiple memory types

Under certain circumstances it's possible for libdrm to decide to move
a GART|VRAM pushbuf to be VRAM-only. This causes the kernel to reject
the command submission on GF8 and up, due to a stricter policy where
buffers are only allowed to move to memory types that were specified
at creation time.

The simplest fix for this is to force the creation-time memory type for
the lifetime of the push buffer.

Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
/external/libdrm/nouveau/pushbuf.c
9e0026d35c56374b53a0b3837e24412bc9a4d8c9 09-Jun-2012 Marcin Slusarz <marcin.slusarz@gmail.com> nouveau: silence some remaining valgrind warnings

Valgrind can't understand some of the fields passed to ioctls are overwritten
by kernel, so we need to initialize them. Almost all of our ioctl wrappers
already do it and the cost of remaining 3 is very small.

Signed-off-by: Marcin Slusarz <marcin.slusarz@gmail.com>
/external/libdrm/nouveau/pushbuf.c
d954648b4872e6b40ec8768a14eee818bc7613a8 23-Apr-2012 Marcin Slusarz <marcin.slusarz@gmail.com> nouveau: remove unnecessary EAGAIN loops

drmCommandWrite / drmCommandWriteRead already loop on EAGAIN.

Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
/external/libdrm/nouveau/pushbuf.c
292da616fe1f936ca78a3fa8e1b1b19883e343b6 09-Dec-2011 Ben Skeggs <bskeggs@redhat.com> nouveau: pull in major libdrm rewrite

Redesigned primarily to allow us to better take advantage of BO's having
fixed GPU virtual addresses on GeForce 8 and up, and to reduce the overhead
of handling relocations on earlier chipsets.

Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
Signed-off-by: Christoph Bumiller <e0425955@student.tuwien.ac.at>
/external/libdrm/nouveau/pushbuf.c