From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@alien8.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] x86/mm changes for v4.12
Date: Wed, 24 May 2017 11:17:19 +0300 [thread overview]
Message-ID: <20170524081719.hwwlfkg7ckfjmtfd@node.shutemov.name> (raw)
In-Reply-To: <20170524062526.bti7xfj3cgi4lk75@gmail.com>
On Wed, May 24, 2017 at 08:25:26AM +0200, Ingo Molnar wrote:
>
> * Kirill A. Shutemov <kirill@shutemov.name> wrote:
>
> > On Mon, May 01, 2017 at 02:00:53PM +0200, Ingo Molnar wrote:
> > > - Continued Intel 5-level paging enablement: in particular the conversion
> > > of x86 GUP to the generic GUP code. (Kirill A. Shutemov)
> > >
> > ...
> > >
> > > I'd like to draw special attention to this late MM commit:
> > >
> > > 71389703839e: mm, zone_device: Replace {get, put}_zone_device_page() with a single reference to fix pmem crash
> > >
> > > ... which is a late fix, and which I believe is the right thing to do - but please
> > > double check.
> >
> > I've just noticied that the x86 GUP conversion haven't made it's way to
> > v4.12: the fix got applied (71389703839e), but the final commit that does
> > convertion keeped reverted -- 6dd29b3df975.
> >
> > I guess it's too late for v4.12...
> >
> > Ingo could you re-apply 2947ba054a4d ("x86/mm/gup: Switch GUP to the
> > generic get_user_page_fast() implementation") to be queued to v4.13?
>
> There were some late problems and I wanted x86/mm to be regression-free - we don't
> have all the 5-level paging patches applied yet so the exact cut we made at v4.12
> does not matter much - v4.13 is going to be the real deal.
>
> Could you please make the re-application part of the remaining 5-level paging
> patches?
Sure. Will post later today.
--
Kirill A. Shutemov
prev parent reply other threads:[~2017-05-24 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 12:00 [GIT PULL] x86/mm changes for v4.12 Ingo Molnar
2017-05-23 14:24 ` Kirill A. Shutemov
2017-05-24 6:25 ` Ingo Molnar
2017-05-24 8:17 ` Kirill A. Shutemov [this message]
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=20170524081719.hwwlfkg7ckfjmtfd@node.shutemov.name \
--to=kirill@shutemov.name \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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).