[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200516125641.GK8135@suse.de>
Date: Sat, 16 May 2020 14:56:41 +0200
From: Joerg Roedel <jroedel@...e.de>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Joerg Roedel <joro@...tes.org>, x86@...nel.org, hpa@...or.com,
Dave Hansen <dave.hansen@...ux.intel.com>,
Andy Lutomirski <luto@...nel.org>,
Peter Zijlstra <peterz@...radead.org>, rjw@...ysocki.net,
Arnd Bergmann <arnd@...db.de>,
Steven Rostedt <rostedt@...dmis.org>,
Vlastimil Babka <vbabka@...e.cz>,
Michal Hocko <mhocko@...nel.org>,
Matthew Wilcox <willy@...radead.org>,
linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
linux-arch@...r.kernel.org, linux-mm@...ck.org,
Christoph Hellwig <hch@...radead.org>
Subject: Re: [PATCH v3 2/7] mm/vmalloc: Track which page-table levels were
modified
Hi Andrew,
On Fri, May 15, 2020 at 01:01:42PM -0700, Andrew Morton wrote:
> On Fri, 15 May 2020 16:00:18 +0200 Joerg Roedel <joro@...tes.org> wrote:
> Lots of collisions here with Christoph's "decruft the vmalloc API" series
> (http://lkml.kernel.org/r/20200414131348.444715-1-hch@lst.de).
>
> I attempted to fix things up.
>
> unmap_kernel_range_noflush() needed to be redone.
>
> map_kernel_range_noflush() might need the arch_sync_kernel_mappings() call?
Yes, map_kernel_range_noflush() needs the arch_sync_kernel_mappings()
call as well.
Regards,
Joerg
Powered by blists - more mailing lists