From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Thomas Hellström (VMware)" <thomas_os@shipmail.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Linux-MM <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: Ack to merge through DRM? WAS Re: [PATCH v2 1/5] mm: Add write-protect and clean utilities for address space ranges
Date: Thu, 26 Sep 2019 12:19:14 -0700 [thread overview]
Message-ID: <CAHk-=wifjLeeMEtMPytiMAKiWkqPorjf1P4PbB3dj17Y3Jcqag@mail.gmail.com> (raw)
In-Reply-To: <85e31bcf-d3c8-2fcf-e659-2c9f82ebedc7@shipmail.org>
On Thu, Sep 26, 2019 at 5:03 AM Thomas Hellström (VMware)
<thomas_os@shipmail.org> wrote:
>
> I wonder if I can get an ack from an mm maintainer to merge this through
> DRM along with the vmwgfx patches? Andrew? Matthew?
It would have helped to actually point to the patch itself, instead of
just quoting the commit message.
Looks like this:
https://lore.kernel.org/lkml/20190926115548.44000-2-thomas_os@shipmail.org/
but why is the code in question not just using the regular page
walkers. The commit log shows no explanation of what's so special
about this?
Is the only reason the locking magic? Because if that's the reason,
then afaik we already have a function for that: it's
__walk_page_range().
Yes, it's static right now, but that's imho not a reason to duplicate
all the walking (badly).
Is there some other magic reason that isn't documented?
Linus
next prev parent reply other threads:[~2019-09-26 19:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 11:55 [PATCH v2 0/5] Emulated coherent graphics memory take 2 Thomas Hellström (VMware)
2019-09-26 11:55 ` [PATCH v2 1/5] mm: Add write-protect and clean utilities for address space ranges Thomas Hellström (VMware)
2019-09-26 12:03 ` Ack to merge through DRM? WAS " Thomas Hellström (VMware)
2019-09-26 19:19 ` Linus Torvalds [this message]
2019-09-26 20:09 ` Thomas Hellström (VMware)
2019-09-26 20:16 ` Linus Torvalds
2019-09-26 20:55 ` Thomas Hellström (VMware)
2019-09-26 22:20 ` Linus Torvalds
2019-09-27 5:55 ` Thomas Hellström (VMware)
2019-09-27 9:27 ` Thomas Hellström (VMware)
2019-09-27 12:26 ` Kirill A. Shutemov
2019-09-27 12:17 ` Kirill A. Shutemov
2019-09-27 16:39 ` Linus Torvalds
2019-09-30 13:03 ` Kirill A. Shutemov
2019-09-30 17:12 ` Linus Torvalds
2019-09-30 17:38 ` Thomas Hellström (VMware)
2019-10-02 9:21 ` Thomas Hellström (VMware)
2019-10-02 13:18 ` Kirill A. Shutemov
2019-10-02 13:28 ` Thomas Hellström (VMware)
2019-09-26 11:55 ` [PATCH v2 2/5] drm/vmwgfx: Implement an infrastructure for write-coherent resources Thomas Hellström (VMware)
2019-09-26 11:55 ` [PATCH v2 3/5] drm/vmwgfx: Use an RBtree instead of linked list for MOB resources Thomas Hellström (VMware)
2019-09-26 11:55 ` [PATCH v2 4/5] drm/vmwgfx: Implement an infrastructure for read-coherent resources Thomas Hellström (VMware)
2019-09-26 11:55 ` [PATCH v2 5/5] drm/vmwgfx: Add surface dirty-tracking callbacks 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='CAHk-=wifjLeeMEtMPytiMAKiWkqPorjf1P4PbB3dj17Y3Jcqag@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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).