dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström (VMware)" <thomas@shipmail.org>
To: airlied@gmail.com, daniel@ffwll.ch, dri-devel@lists.freedesktop.org
Cc: pv-drivers@vmware.com, "Thomas Hellström" <thomas@shipmail.org>,
	linux-graphics-maintainer@vmware.com
Subject: [git pull] vmwgfx-next
Date: Wed, 19 Jun 2019 09:25:31 +0200	[thread overview]
Message-ID: <20190619072531.4026-1-thomas@shipmail.org> (raw)

Dave, Daniel

- The coherent memory changes including mm changes.
- Some vmwgfx debug fixes.
- Removal of vmwgfx legacy security checks.

The following changes since commit 561564bea3248293398dc32ec36da40fb71faed0:

  Merge tag 'omapdrm-5.3' of git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux into drm-next (2019-06-11 13:29:33 +0200)

are available in the Git repository at:

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

for you to fetch changes up to 9bbfda544ed79e8e9abde27bfe2c85428d582e7b:

  drm/vmwgfx: Kill unneeded legacy security features (2019-06-18 15:22:48 +0200)

----------------------------------------------------------------
Deepak Rawat (2):
      drm/vmwgfx: Add debug message for layout change ioctl
      drm/vmwgfx: Use VMW_DEBUG_KMS for vmwgfx mode-setting user errors

Thomas Hellstrom (11):
      drm/vmwgfx: Assign eviction priorities to resources
      mm: Allow the [page|pfn]_mkwrite callbacks to drop the mmap_sem
      mm: Add an apply_to_pfn_range interface
      mm: Add write-protect and clean utilities for address space ranges
      drm/ttm: Allow the driver to provide the ttm struct vm_operations_struct
      drm/ttm: TTM fault handler helpers
      drm/vmwgfx: Implement an infrastructure for write-coherent resources
      drm/vmwgfx: Use an RBtree instead of linked list for MOB resources
      drm/vmwgfx: Implement an infrastructure for read-coherent resources
      drm/vmwgfx: Add surface dirty-tracking callbacks
      drm/vmwgfx: Kill unneeded legacy security features

 MAINTAINERS                                        |   1 +
 drivers/gpu/drm/ttm/ttm_bo.c                       |   1 +
 drivers/gpu/drm/ttm/ttm_bo_vm.c                    | 169 +++++---
 drivers/gpu/drm/vmwgfx/Kconfig                     |   1 +
 drivers/gpu/drm/vmwgfx/Makefile                    |   2 +-
 .../drm/vmwgfx/device_include/svga3d_surfacedefs.h | 233 +++++++++-
 drivers/gpu/drm/vmwgfx/ttm_lock.c                  | 100 -----
 drivers/gpu/drm/vmwgfx/ttm_lock.h                  |  30 --
 drivers/gpu/drm/vmwgfx/vmwgfx_bo.c                 |  12 +-
 drivers/gpu/drm/vmwgfx/vmwgfx_context.c            |   4 +
 drivers/gpu/drm/vmwgfx/vmwgfx_cotable.c            |  13 +-
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.c                | 167 +-------
 drivers/gpu/drm/vmwgfx/vmwgfx_drv.h                | 139 ++++--
 drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c            |   1 -
 drivers/gpu/drm/vmwgfx/vmwgfx_kms.c                |  23 +-
 drivers/gpu/drm/vmwgfx/vmwgfx_page_dirty.c         | 472 +++++++++++++++++++++
 drivers/gpu/drm/vmwgfx/vmwgfx_resource.c           | 245 +++++++++--
 drivers/gpu/drm/vmwgfx/vmwgfx_resource_priv.h      |  15 +
 drivers/gpu/drm/vmwgfx/vmwgfx_shader.c             |   8 +-
 drivers/gpu/drm/vmwgfx/vmwgfx_surface.c            | 405 +++++++++++++++++-
 drivers/gpu/drm/vmwgfx/vmwgfx_validation.c         |  74 +++-
 drivers/gpu/drm/vmwgfx/vmwgfx_validation.h         |  16 +-
 include/drm/ttm/ttm_bo_api.h                       |  10 +
 include/drm/ttm/ttm_bo_driver.h                    |   6 +
 include/linux/mm.h                                 |  19 +-
 include/uapi/drm/vmwgfx_drm.h                      |   4 +-
 mm/Kconfig                                         |   3 +
 mm/Makefile                                        |   1 +
 mm/as_dirty_helpers.c                              | 300 +++++++++++++
 mm/memory.c                                        | 145 +++++--
 30 files changed, 2136 insertions(+), 483 deletions(-)
 create mode 100644 drivers/gpu/drm/vmwgfx/vmwgfx_page_dirty.c
 create mode 100644 mm/as_dirty_helpers.c
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-06-19  7:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19  7:25 Thomas Hellström (VMware) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-01-16  9:29 [git pull] vmwgfx-next Thomas Hellström (VMware)
2020-01-20 21:09 ` Dave Airlie
2020-01-20 21:42   ` Thomas Hellström (VMware)
2020-01-21  9:49   ` Thomas Hellström (VMware)
2019-11-14 13:17 Thomas Hellström (VMware)
2019-08-15  7:15 Thomas Hellström (VMware)
     [not found] <20190814073152.3120-1-thomas@shipmail.org>
2019-08-14 17:35 ` Thomas Hellström (VMware)
2018-12-05 10:35 Thomas Hellstrom
2018-09-28 13:11 Thomas Hellstrom
2017-08-28 20:22 [Git PULL] vmwgfx-next Sinclair Yeh
2017-08-28 20:35 ` Dave Airlie
2017-08-28 20:39   ` Sinclair Yeh
2017-04-21 17:18 [git pull] vmwgfx-next Sinclair Yeh
2017-03-31 23:32 Sinclair Yeh
2017-04-02 18:11 ` Daniel Vetter
2017-04-03 19:00   ` Sinclair Yeh
2017-01-30 19:46 Sinclair Yeh
2015-11-06 15:29 Thomas Hellstrom
2015-11-02  8:23 Thomas Hellstrom
2015-08-06 12:54 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=20190619072531.4026-1-thomas@shipmail.org \
    --to=thomas@shipmail.org \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --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