[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200229200432.55b5b64f46dc2f2f80fa7461@linux-foundation.org>
Date: Sat, 29 Feb 2020 20:04:32 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Thomas Hellström (VMware)
<thomas_os@...pmail.org>
Cc: Michal Hocko <mhocko@...e.com>, linux-mm@...ck.org,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
Ralph Campbell <rcampbell@...dia.com>, pv-drivers@...are.com,
Dan Williams <dan.j.williams@...el.com>,
"Matthew Wilcox (Oracle)" <willy@...radead.org>,
Jérôme Glisse <jglisse@...hat.com>,
linux-graphics-maintainer@...are.com,
Christian König <christian.koenig@....com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
Subject: Re: [PATCH v4 0/9] Huge page-table entries for TTM
On Fri, 28 Feb 2020 14:08:04 +0100 Thomas Hellström (VMware) <thomas_os@...pmail.org> wrote:
> I'm wondering what's the best way here to get the patches touching mm
> reviewed and accepted?
> While drm people and VMware internal people have looked at them, I think
> the huge_fault() fallback splitting and the introduction of
> vma_is_special_huge() needs looking at more thoroughly.
>
> Apart from that, if possible, I think the best way to merge this series
> is also through a DRM tree.
Patches 1-3 look OK to me. I just had a few commenting/changelogging
niggles.
Powered by blists - more mailing lists