linux-stable.git/drivers/gpu/drm/vmwgfx, branch linux-3.4.y

drm/vmwgfx: Reorder device takedown somewhat

2015-06-19T03:40:24+00:00

commit 3458390b9f0ba784481d23134798faee27b5f16f upstream.

To take down the MOB and GMR memory types, the driver may have to issue
fence objects and thus make sure that the fence manager is taken down
after those memory types.
Reorder device init accordingly.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Sinclair Yeh 
Signed-off-by: Zefan Li

drm/vmwgfx: Fix fence event code

2015-04-14T09:33:44+00:00

commit 89669e7a7f96be3ee8d9a22a071d7c0d3b4428fc upstream.

The commit "vmwgfx: Rework fence event action" introduced a number of bugs
that are fixed with this commit:

a) A forgotten return stateemnt.
b) An if statement with identical branches.

Reported-by: Rob Clark 
Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Reviewed-by: Sinclair Yeh 
Signed-off-by: Zefan Li

drm/vmwgfx: Don't use memory accounting for kernel-side fence objects

2015-04-14T09:33:44+00:00

commit 1f563a6a46544602183e7493b6ef69769d3d76d9 upstream.

Kernel side fence objects are used when unbinding resources and may thus be
created as part of a memory reclaim operation. This might trigger recursive
memory reclaims and result in the kernel running out of stack space.

So a simple way out is to avoid accounting of these fence objects.
In principle this is OK since while user-space can trigger the creation of
such objects, it can't really hold on to them. However, their lifetime is
quite long, so some form of accounting should perhaps be implemented in the
future.

Fixes kernel crashes when running, for example viewperf11 ensight-04 test 3
with low system memory settings.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Reviewed-by: Sinclair Yeh 
[lizf: Backported to 3.4: adjust context]
Signed-off-by: Zefan Li

drm/vmwgfx: Filter out modes those cannot be supported by the current VRAM size.

2015-02-02T09:05:09+00:00

commit 9a72384d86b26cb8a2b25106677e1197f606668f upstream.

When screen objects are enabled, the bpp is assumed to be 32, otherwise
it is set to 16.

v2:
* Use u32 instead of u64 for assumed_bpp.
* Fixed mechanism to check for screen objects
* Limit the back buffer size to VRAM.

Signed-off-by: Sinclair Yeh 
Reviewed-by: Thomas Hellstrom 
[lizf: Backported to 3.4: drop the changes to vmw_driver_load()]
Signed-off-by: Zefan Li

drm/vmwgfx: Fix a potential infinite spin waiting for fifo idle

2014-12-01T10:02:21+00:00

commit f01ea0c3d9db536c64d47922716d8b3b8f21d850 upstream.

The code waiting for fifo idle was incorrect and could possibly spin
forever under certain circumstances.

Signed-off-by: Thomas Hellstrom 
Reported-by: Mark Sheldon 
Reviewed-by: Jakob Bornecrantz 
Reivewed-by: Mark Sheldon 
Signed-off-by: Zefan Li

drm/vmwgfx: Fix incorrect write to read-only register v2:

2014-07-09T17:51:20+00:00

commit 4e578080ed3262ed2c3985868539bc66218d25c0 upstream.

Commit "drm/vmwgfx: correct fb_fix_screeninfo.line_length", while fixing a
vmwgfx fbdev bug, also writes the pitch to a supposedly read-only register:
SVGA_REG_BYTES_PER_LINE, while it should be (and also in fact is) written to
SVGA_REG_PITCHLOCK.

This patch is Cc'd stable because of the unknown effects writing to this
register might have, particularly on older device versions.

v2: Updated log message.

Cc: Christopher Friedt 
Tested-by: Christopher Friedt 
Signed-off-by: Thomas Hellstrom 
Reviewed-by: Jakob Bornecrantz 
Signed-off-by: Greg Kroah-Hartman

drm/vmwgfx: correct fb_fix_screeninfo.line_length

2014-06-07T23:01:58+00:00

commit aa6de142c901cd2d90ef08db30ae87da214bedcc upstream.

Previously, the vmwgfx_fb driver would allow users to call FBIOSET_VINFO, but it would not adjust
the FINFO properly, resulting in distorted screen rendering. The patch corrects that behaviour.

See https://bugs.gentoo.org/show_bug.cgi?id=494794 for examples.

Signed-off-by: Christopher Friedt 
Reviewed-by: Thomas Hellstrom 
Signed-off-by: Greg Kroah-Hartman

drm/vmwgfx: Split GMR2_REMAP commands if they are to large

2013-09-08T04:58:15+00:00

commit 6e4dcff3adbf25acb87e74500a58e3c07bdec40f upstream.

This fixes the piglit test texturing/max-texture-size
causing the VM to die due to a too large SVGA command.

Signed-off-by: Jakob Bornecrantz 
Reviewed-by: Biran Paul 
Reviewed-by: Zack Rusin 
Signed-off-by: Dave Airlie 
Signed-off-by: Greg Kroah-Hartman

drm/vmwgfx: Fix a case where the code would BUG when trying to pin GMR memory

2012-11-17T21:16:34+00:00

commit afcc87aa6a233e52df73552dc1dc9ae3881b7cc8 upstream.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Brian Paul 
Reviewed-by: Dmitry Torokhov 
Cc: linux-graphics-maintainer@vmware.com
Signed-off-by: Dave Airlie 
Signed-off-by: Greg Kroah-Hartman

drm/vmwgfx: Fix hibernation device reset

2012-11-17T21:16:34+00:00

commit 95e8f6a21996c4cc2c4574b231c6e858b749dce3 upstream.

The device would not reset properly when resuming from hibernation.

Signed-off-by: Thomas Hellstrom 
Reviewed-by: Brian Paul 
Reviewed-by: Dmitry Torokhov 
Cc: linux-graphics-maintainer@vmware.com
Signed-off-by: Dave Airlie 
Signed-off-by: Greg Kroah-Hartman