[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y10atFd3sn1s1C6x@hirez.programming.kicks-ass.net>
Date: Sat, 29 Oct 2022 14:21:08 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: x86@...nel.org, willy@...radead.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
aarcange@...hat.com, kirill.shutemov@...ux.intel.com,
jroedel@...e.de, ubizjak@...il.com
Subject: Re: [PATCH 00/13] Clean up pmd_get_atomic() and i386-PAE
On Sat, Oct 22, 2022 at 01:14:03PM +0200, Peter Zijlstra wrote:
> Hi,
>
> At long *long* last a respin of the patches that clean up pmd_get_atomic() and
> i386-PAE. I'd nearly forgotten why I did this, but the old posting gave clue
> that patch #7 was the whole purpose of me doing these patches.
>
> Having carried these patches for at least 2 years, they recently hit a rebase
> bump against the mg-lru patches, which is what prompted this repost.
>
> Linus' comment about try_cmpxchg64() (and Uros before him) made me redo those
> patches (see patch #10) which resulted in pxx_xchg64(). This in turn led to
> killing off set_64bit().
>
> The robot doesn't hate on these patches and they boot in kvm (because who still
> has i386 hardware).
>
> Patches also available at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git x86/mm.pae
Aside from the whole discussions about TLB invalidates; I mean to commit
these patches to tip/x86/mm next week somewhere since they do improve
the current situation.
Holler if there's objections.
Powered by blists - more mailing lists