linux-toradex.git/drivers/gpu/drm/drm_gem.c, branch v2.6.33.1

drm/i915: Selectively enable self-reclaim

2010-01-27T17:26:43+00:00

Having missed the ENOMEM return via i915_gem_fault(), there are probably
other paths that I also missed. By not enabling NORETRY by default these
paths can run the shrinker and take memory from the system (but not from
our own inactive lists because our shrinker can not run whilst we hold
the struct mutex) and this may allow the system to survive a little longer
whilst our drivers consume all available memory.

References:
  OOM killer unexpectedly called with kernel 2.6.32
  http://bugzilla.kernel.org/show_bug.cgi?id=14933

v2: Pass gfp into page mapping.
v3: Use new read_cache_page_gfp() instead of open-coding.

Signed-off-by: Chris Wilson 
Cc: KOSAKI Motohiro 
Cc: Hugh Dickins 
Cc: Jesse Barnes 
Cc: Eric Anholt 
Cc: stable@kernel.org
Signed-off-by: Linus Torvalds

drm: make sure page protections are updated after changing vm_flags

2009-11-24T03:02:30+00:00

Some architectures compute ->vm_page_prot depending on ->vm_flags, so we
need to update the protections after adjusting the flags.

AFAIK this only affects running X under Xen; without this patch you get
lots of coloured blobs on the screen, or maybe a complete lockup.  Or
anything really.

But that still depends on lots of out-of-tree stuff, so I don't think
there are any consequences for anyone else.  But it is wrong in principle.

Reported-by: Jan Beulich 
Signed-off-by: Jeremy Fitzhardinge 
Signed-off-by: Andrew Morton 
Signed-off-by: Dave Airlie

drm/i915: Improve behaviour under memory pressure

2009-09-17T21:43:32+00:00

Due to the necessity of having to take the struct_mutex, the i915
shrinker can not free the inactive lists if we fail to allocate memory
whilst processing a batch buffer, triggering an OOM and an ENOMEM that
is reported back to userspace. In order to fare better under such
circumstances we need to manually retry a failed allocation after
evicting inactive buffers.

To do so involves 3 steps:
1. Marking the backing shm pages as NORETRY.
2. Updating the get_pages() callers to evict something on failure and then
   retry.
3. Revamping the evict something logic to be smarter about the required
   buffer size and prefer to use volatile or clean inactive pages.

Signed-off-by: Chris Wilson 
Signed-off-by: Jesse Barnes

drm: GEM handles are u32, not int

2009-08-27T01:21:08+00:00

Several functions in the GEM kernel API used int as handle type, but
user API has it __u32 which is also the intended type.

Replace int with u32.

Signed-off-by: Pekka Paalanen 
Signed-off-by: Dave Airlie

drm: drm_gem, check kzalloc retval

2009-07-15T05:56:12+00:00

Check kzalloc retval against NULL in drm_gem_object_alloc and bail out
appropriately.

While at it merge the fail paths and jump to them by gotos at the end
of the function.

Signed-off-by: Jiri Slaby 
Signed-off-by: Dave Airlie

drm: Remove memory debugging infrastructure.

2009-06-18T20:00:33+00:00

It hasn't been used in ages, and having the user tell your how much
memory is being freed at free time is a recipe for disaster even if it
was ever used.

Signed-off-by: Eric Anholt

drm: simplify kcalloc() call to kzalloc().

2009-06-11T06:10:30+00:00

Calls to kcalloc() for a single element can be simplified to calls to
kzalloc().

Signed-off-by: Robert P. J. Day 
Cc: Dave Airlie 
Cc: Eric Anholt 
Signed-off-by: Andrew Morton 
Signed-off-by: Dave Airlie

drm: Use pgprot_writecombine in GEM GTT mapping to get the right bits for !PAT.

2009-04-02T21:28:32+00:00

Otherwise, the PAGE_CACHE_WC would end up getting us a UC-only mapping, and
the write performance of GTT maps dropped 10x.

Signed-off-by: Jesse Barnes 
[anholt: cleaned up unused var]
Signed-off-by: Eric Anholt

drm: Split drm_map and drm_local_map

2009-03-13T04:23:56+00:00

Once upon a time, the DRM made the distinction between the drm_map
data structure exchanged with user space and the drm_local_map used
in the kernel.

For some reasons, while the BSD port still has that "feature", the
linux part abused drm_map for kernel internal usage as the local
map only existed as a typedef of the struct drm_map.

This patch fixes it by declaring struct drm_local_map separately
(though its content is currently identical to the userspace variant),
and changing the kernel code to only use that, except when it's a
user<->kernel interface (ie. ioctl).

This allows subsequent changes to the in-kernel format

I've also replaced the use of drm_local_map_t with struct drm_local_map
in a couple of places. Mostly by accident but they are the same (the
former is a typedef of the later) and I have some remote plans and
half finished patch to completely kill the drm_local_map_t typedef
so I left those bits in.

Signed-off-by: Benjamin Herrenschmidt 
Acked-by: Eric Anholt 
Signed-off-by: Dave Airlie

drm/i915: Keep refs on the object over the lifetime of vmas for GTT mmap.

2009-02-20T02:21:13+00:00

This fixes potential fault at fault time if the object was unreferenced
while the mapping still existed.  Now, while the mmap_offset only lives
for the lifetime of the object, the object also stays alive while a vma
exists that needs it.

Signed-off-by: Jesse Barnes 
Signed-off-by: Eric Anholt 
Signed-off-by: Dave Airlie