dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Hellstrom <thellstrom@vmware.com>
To: airlied@gmail.com, airlied@redhat.com
Cc: pv-drivers@vmware.com, Thomas Hellstrom <thellstrom@vmware.com>,
	linux-graphics-maintainer@vmware.com,
	dri-devel@lists.freedesktop.org
Subject: [PULL] ttm-next
Date: Mon, 13 Jan 2014 12:01:26 +0100	[thread overview]
Message-ID: <1389610886-4486-1-git-send-email-thellstrom@vmware.com> (raw)

Dave,

Some code cleanup by Rashika Keria,
VM stuff for ttm:
-Use PFNMAP instead of MIXEDMAP where possible for performance
-Refuse to fault imported pages, an initial step to support dma-bufs
better from within TTM.
-Correctly set page mapping and -index members. These are needed in various
places in the vm subsystem that we are not using yet, but plan to use soonish:
For example unmap-mapping-range keeping COW pages, and dirty tracking
fbdefio style, but also for PCI memory.

The following changes since commit 859ae233cd0ee76b6143f948ba1cb6b0b4c342f8:

  Merge tag 'drm-intel-next-2013-12-13' of git://people.freedesktop.org/~danvet/drm-intel into drm-next (2013-12-23 10:46:07 +1000)

are available in the git repository at:


  git://people.freedesktop.org/~thomash/linux tags/ttm-next-2014-01-13

for you to fetch changes up to 52028704126b5597775cc788028385556af1f85c:

  drivers: gpu: Remove unused function in ttm_lock.c (2014-01-08 13:24:14 +0100)

----------------------------------------------------------------
ttm-next 2013-01-14 pull request

----------------------------------------------------------------
Rashika Kheria (3):
      drivers: gpu: Mark function as static in ttm_bo.c
      drivers: gpu: Mark function as static in ttm_bo_util.c
      drivers: gpu: Remove unused function in ttm_lock.c

Thomas Hellstrom (3):
      drm/ttm: Use VM_PFNMAP for shared bo maps
      drm/ttm: Refuse to fault (prime-) imported pages
      drm/ttm: Correctly set page mapping and -index members

 drivers/gpu/drm/ttm/ttm_bo.c      |    2 +-
 drivers/gpu/drm/ttm/ttm_bo_util.c |    4 ++--
 drivers/gpu/drm/ttm/ttm_bo_vm.c   |   32 +++++++++++++++++++++++++++++---
 drivers/gpu/drm/ttm/ttm_lock.c    |    8 --------
 drivers/gpu/drm/ttm/ttm_tt.c      |   27 +++++++++++++++++++++++----
 include/drm/ttm/ttm_bo_driver.h   |    9 +++++++++
 6 files changed, 64 insertions(+), 18 deletions(-)

             reply	other threads:[~2014-01-13 11:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 11:01 Thomas Hellstrom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-04-04  6:08 [PULL] ttm-next 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=1389610886-4486-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 \
    --cc=linux-graphics-maintainer@vmware.com \
    --cc=pv-drivers@vmware.com \
    /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