dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Hellstrom <thellstrom@vmware.com>
To: airlied@redhat.com, airlied@gmail.com
Cc: Thomas Hellstrom <thellstrom@vmware.com>,
	dri-devel@lists.freedesktop.org
Subject: [PULL] vmwgfx vmwgfx-next-3.13
Date: Wed,  6 Nov 2013 05:45:12 -0800	[thread overview]
Message-ID: <1383745512-4530-1-git-send-email-thellstrom@vmware.com> (raw)

Hi, Dave

Pull requst for TTM. 
- A couple of fixes that never made it into fixes-3.12
- Make NO_EVICT bo's available for shrinkers when on delayed-delete list
- Allow retrying page-faults that need to wait for GPU.

/Thomas

The following changes since commit 4695b03970df378dcb93fe3e7158381f1e980fa2:

  qxl: add a connector property to denote hotplug should rescan modes. (2013-11-06 15:23:26 +1000)

are available in the git repository at:

  git://people.freedesktop.org/~thomash/linux ttm-next-3.13

for you to fetch changes up to 59c8e66378fb78adbcd05f0d09783dde6fef282b:

  drm/ttm: Fix memory type compatibility check (2013-11-06 04:36:22 -0800)

----------------------------------------------------------------
Jakob Bornecrantz (1):
      drm/ttm: Handle in-memory region copies

Thomas Hellstrom (4):
      drm/ttm: Allow vm fault retries
      drm/ttm: Make NO_EVICT bos available to shrinkers pending destruction
      drm/ttm: Fix ttm_bo_move_memcpy
      drm/ttm: Fix memory type compatibility check

 drivers/gpu/drm/ttm/ttm_bo.c      |   46 +++++++++++++++++++--------
 drivers/gpu/drm/ttm/ttm_bo_util.c |   30 +++++++++++-------
 drivers/gpu/drm/ttm/ttm_bo_vm.c   |   62 ++++++++++++++++++++++++++++++-------
 3 files changed, 102 insertions(+), 36 deletions(-)

             reply	other threads:[~2013-11-06 13:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06 13:45 Thomas Hellstrom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-11-06 13:33 [PULL] vmwgfx vmwgfx-next-3.13 Thomas Hellstrom

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=1383745512-4530-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 \
    /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