From: Hillf Danton <hdanton@sina.com>
To: Thomas Hellstrom <thellstrom@vmware.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-mm@kvack.org
Subject: Re: [RFC PATCH 0/7] Emulated coherent graphics memory take 2
Date: Sun, 15 Sep 2019 11:34:50 +0800 [thread overview]
Message-ID: <20190915033450.14008-1-hdanton@sina.com> (raw)
On Fri, 13 Sep 2019 11:32:06 +0200
>
> The mm patch page walk interface has been reworked to be similar to the
> reworked page-walk code (mm/pagewalk.c). There have been two other solutions
> to consider:
> 1) Using the page-walk code. That is currently not possible since it requires
> the mmap-sem to be held for the struct vm_area_struct vm_flags and for huge
> page splitting. The pagewalk code in this patchset can't hold the mmap sems
> since it will lead to locking inversion.
Specify the locking scenario, if non-rfc is planned, to help understand
the new wheel this patchset looks to create, as two days of finding it in
the works after ba4e7d973dd0 failed.
next reply other threads:[~2019-09-15 3:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-15 3:34 Hillf Danton [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-13 9:32 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=20190915033450.14008-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox