From: "Thomas Hellström (VMware)" <thomas_os@shipmail.org>
To: dri-devel@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>
Subject: TTM or vmwgfx tree? Re: [PATCH v5 0/2] mm, drm/ttm: Fix pte insertion with customized protection
Date: Wed, 15 Jan 2020 13:45:41 +0100 [thread overview]
Message-ID: <01560aef-b21e-57b9-a7a1-fd7ff3aabfb2@shipmail.org> (raw)
In-Reply-To: <20200115124107.3845-1-thomas_os@shipmail.org>
Hi Christian,
On 1/15/20 1:41 PM, Thomas Hellström (VMware) wrote:
> From: Thomas Hellstrom <thellstrom@vmware.com>
>
> The drm/ttm module is using a modified on-stack copy of the
> struct vm_area_struct to be able to set a page protection with customized
> caching. Fix that by adding a vmf_insert_mixed_prot() function similar
> to the existing vmf_insert_pfn_prot() for use with drm/ttm.
>
> Patches are acked to be merged through a drm tree.
This small patchset should be ready to be merged now, with acks from Andrew.
Do you want to take it through the ttm tree, or should I ask Dave /
Daniel to pull it separately?
Note that similar to the vmwgfx coherent patches, Linus has indicated
that he wants separate pull requests for stuff like this that touches mm.
Thanks,
Thomas
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-01-15 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 12:41 [PATCH v5 0/2] mm, drm/ttm: Fix pte insertion with customized protection Thomas Hellström (VMware)
2020-01-15 12:41 ` [PATCH v5 1/2] mm: Add a vmf_insert_mixed_prot() function Thomas Hellström (VMware)
2020-01-15 12:41 ` [PATCH v5 2/2] mm, drm/ttm: Fix vm page protection handling Thomas Hellström (VMware)
2020-01-15 12:45 ` Thomas Hellström (VMware) [this message]
2020-01-15 12:54 ` TTM or vmwgfx tree? Re: [PATCH v5 0/2] mm, drm/ttm: Fix pte insertion with customized protection Christian König
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=01560aef-b21e-57b9-a7a1-fd7ff3aabfb2@shipmail.org \
--to=thomas_os@shipmail.org \
--cc=christian.koenig@amd.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;
as well as URLs for NNTP newsgroup(s).