From: "Thomas Hellström (VMware)" <thomas_os@shipmail.org>
To: airlied@gmail.com, airlied@redhat.com, daniel@ffwll.ch
Cc: pv-drivers@vmware.com, "Thomas Hellström" <thellstrom@vmware.com>,
linux-graphics-maintainer@vmware.com,
dri-devel@lists.freedesktop.org
Subject: [git pull] ttm-prot-fix
Date: Thu, 16 Jan 2020 11:24:11 +0100 [thread overview]
Message-ID: <20200116102411.3056-1-thomas_os@shipmail.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1435 bytes --]
From: Thomas Hellström (VMware) <thellstrom@vmware.com>
Dave, Daniel,
A small fix for the long-standing ttm vm page protection hack.
I'm sending this a separate pull request since it is touching mm code and
similar to the vmwgfx coherent stuff, Linus might want this as a separate
pull request. If sent separate it'd be good if it could still spend some
time in linux-next.
The mm changes have been acked by Andrew for merging through drm.
The ttm changes have been OK'd by Christian for a direct pull.
The following changes since commit 71e7274066c646bb3d9da39d2f4db0a6404c0a2d:
Merge tag 'drm-intel-next-2020-01-14' of git://anongit.freedesktop.org/drm/drm-intel into drm-next (2020-01-15 16:57:54 +1000)
are available in the Git repository at:
git://people.freedesktop.org/~thomash/linux ttm-prot-fix
for you to fetch changes up to 5379e4dd3220e23f68ce70b76b3a52a9a68cee05:
mm, drm/ttm: Fix vm page protection handling (2020-01-16 10:32:41 +0100)
----------------------------------------------------------------
Thomas Hellstrom (2):
mm: Add a vmf_insert_mixed_prot() function
mm, drm/ttm: Fix vm page protection handling
drivers/gpu/drm/ttm/ttm_bo_vm.c | 22 ++++++++++++++-------
include/linux/mm.h | 2 ++
include/linux/mm_types.h | 7 ++++++-
mm/memory.c | 44 +++++++++++++++++++++++++++++++++++++----
4 files changed, 63 insertions(+), 12 deletions(-)
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2020-01-16 10:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200116102411.3056-1-thomas_os@shipmail.org \
--to=thomas_os@shipmail.org \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=pv-drivers@vmware.com \
--cc=thellstrom@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.