tree 1c21aa2aee3380f34cfa8f2802b7c07bb22d0640
parent b11b88ef0e07a1ea9a3df6666ba8e15833facc67
author Dave Airlie <airlied@redhat.com> 1367470321 -0400
committer Dave Airlie <airlied@redhat.com> 1367462799 +1000

drm/mgag200: deal with bo reserve fail in dirty update path

On F19 testing, it was noticed we get a lot of errors in dmesg
about being unable to reserve the buffer when plymouth starts,
this is due to the buffer being in the process of migrating,
so it makes sense we can't reserve it.

In order to deal with it, this adds delayed updates for the dirty
updates, when the bo is unreservable, in the normal console case
this shouldn't ever happen, its just when plymouth or X is
pushing the console bo to system memory.

Cc: stable@vger.kernel.org
Signed-off-by: Dave Airlie <airlied@redhat.com>