From: Michal Hocko <mhocko@kernel.org>
To: "Thomas Hellström (VMware)" <thomas_os@shipmail.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, pv-drivers@vmware.com,
linux-graphics-maintainer@vmware.com,
"Thomas Hellstrom" <thellstrom@vmware.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
"Ralph Campbell" <rcampbell@nvidia.com>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH v2 1/2] mm: Add and export vmf_insert_mixed_prot()
Date: Wed, 4 Dec 2019 14:48:50 +0100 [thread overview]
Message-ID: <20191204134850.GG25242@dhcp22.suse.cz> (raw)
In-Reply-To: <20191203104853.4378-2-thomas_os@shipmail.org>
On Tue 03-12-19 11:48:52, Thomas Hellström (VMware) wrote:
> From: Thomas Hellstrom <thellstrom@vmware.com>
>
> The TTM module today uses a hack to be able to set a different page
> protection than struct vm_area_struct::vm_page_prot. To be able to do
> this properly, add and export vmf_insert_mixed_prot().
A new symbol should be added in a patch that adds a new user which is
not the case here.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-12-04 13:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 10:48 [PATCH v2 0/2] mm, drm/ttm: Fix pte insertion with customized protection Thomas Hellström (VMware)
2019-12-03 10:48 ` [PATCH v2 1/2] mm: Add and export vmf_insert_mixed_prot() Thomas Hellström (VMware)
2019-12-04 13:48 ` Michal Hocko [this message]
2019-12-03 10:48 ` [PATCH v2 2/2] drm/ttm: Fix vm page protection handling Thomas Hellström (VMware)
2019-12-04 13:52 ` Michal Hocko
2019-12-04 14:16 ` Thomas Hellström (VMware)
2019-12-04 14:35 ` Michal Hocko
2019-12-04 14:36 ` Thomas Hellström (VMware)
2019-12-04 14:42 ` Michal Hocko
2019-12-04 15:19 ` Thomas Hellström (VMware)
2019-12-04 15:26 ` Michal Hocko
2019-12-04 15:29 ` Thomas Hellström (VMware)
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=20191204134850.GG25242@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jglisse@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pv-drivers@vmware.com \
--cc=rcampbell@nvidia.com \
--cc=thellstrom@vmware.com \
--cc=thomas_os@shipmail.org \
--cc=willy@infradead.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).