[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3b9561d0-3bde-ef7a-0313-c2cc6216f94d@intel.com>
Date: Fri, 12 Apr 2019 07:44:37 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Steven Price <steven.price@....com>, linux-mm@...ck.org,
Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Mark Rutland <Mark.Rutland@....com>, x86@...nel.org,
Arnd Bergmann <arnd@...db.de>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Peter Zijlstra <peterz@...radead.org>,
Catalin Marinas <catalin.marinas@....com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Will Deacon <will.deacon@....com>,
linux-kernel@...r.kernel.org,
Jérôme Glisse <jglisse@...hat.com>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Andy Lutomirski <luto@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>,
James Morse <james.morse@....com>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-arm-kernel@...ts.infradead.org,
"Liang, Kan" <kan.liang@...ux.intel.com>
Subject: Re: [PATCH v8 00/20] Convert x86 & arm64 to use generic page walk
On 4/10/19 7:56 AM, Steven Price wrote:
> Gentle ping: who can take this? Is there anything blocking this series?
First of all, I really appreciate that you tried this. Every open-coded
page walk has a set of common pitfalls, but is pretty unbounded in what
kinds of bugs it can contain. I think this at least gets us to the
point where some of those pitfalls won't happen. That's cool, but I'm a
worried that it hasn't gotten easier in the end.
Linus also had some strong opinions in the past on how page walks should
be written. He needs to have a look before we go much further.
Powered by blists - more mailing lists