From: Ingo Molnar <mingo@kernel.org>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Andi Kleen <ak@linux.intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Andy Lutomirski <luto@amacapital.net>,
linux-arch@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] Last bits for initial 5-level paging enabling
Date: Fri, 30 Jun 2017 08:59:26 +0200 [thread overview]
Message-ID: <20170630065926.fcwax3odtla4dp4t@gmail.com> (raw)
In-Reply-To: <20170629150657.urgapbzmf3jy6jgp@node.shutemov.name>
* Kirill A. Shutemov <kirill@shutemov.name> wrote:
> > > Can I apply them in this order cleanly, without breaking bisection:
> > >
> > > > x86/mm: Rename tasksize_32bit/64bit to task_size_32bit/64bit
> > > > x86/mpx: Do not allow MPX if we have mappings above 47-bit
> > > > x86/mm: Prepare to expose larger address space to userspace
> > > > x86/mm: Allow userspace have mapping above 47-bit
> > > > x86: Enable 5-level paging support
> > >
> > > ?
> > >
> > > I.e. I'd like to move the first patch last.
> > >
> > > The reason is that we should first get all quirks and assumptions fixed, all
> > > facilities implemented - and only then enable 5-level paging as a final step which
> > > produces a well working kernel.
> > >
> > > (This should also make it slightly easier to analyze any potential regressions in
> > > earlier patches.)
> >
> > Just checked bisectability with this order on allmodconfig -- works fine.
>
> Ingo, if there's no objections, can we get these applied?
Just this week, which is the final week of the development window, we had two
fixes for the 5-level pagetables commits, so we need to delay the rest to right
after -rc1.
Could you please resend them them (and any followup patches), in the suggested
order? I don't see any conceptual problems, so this is only about timing and
maximizing stability.
Thanks,
Ingo
next prev parent reply other threads:[~2017-06-30 6:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 12:26 [PATCH 0/5] Last bits for initial 5-level paging enabling Kirill A. Shutemov
2017-06-22 12:26 ` [PATCH 1/5] x86: Enable 5-level paging support Kirill A. Shutemov
2017-06-22 12:26 ` [PATCH 2/5] x86/mm: Rename tasksize_32bit/64bit to task_size_32bit/64bit Kirill A. Shutemov
2017-06-22 12:26 ` [PATCH 3/5] x86/mpx: Do not allow MPX if we have mappings above 47-bit Kirill A. Shutemov
2017-06-22 12:26 ` [PATCH 4/5] x86/mm: Prepare to expose larger address space to userspace Kirill A. Shutemov
2017-06-22 12:26 ` [PATCH 5/5] x86/mm: Allow userspace have mapping above 47-bit Kirill A. Shutemov
2017-06-23 9:06 ` [PATCH 0/5] Last bits for initial 5-level paging enabling Ingo Molnar
2017-06-23 14:49 ` Kirill A. Shutemov
2017-06-29 15:06 ` Kirill A. Shutemov
2017-06-30 6:59 ` Ingo Molnar [this message]
2017-06-28 12:17 ` [PATCH 6/5] x86/KASLR: Fix detection 32/64 bit bootloaders for 5-level paging Kirill A. Shutemov
2017-06-28 16:39 ` Kees Cook
2017-06-30 13:08 ` [tip:x86/mm] " tip-bot for Kirill A. Shutemov
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=20170630065926.fcwax3odtla4dp4t@gmail.com \
--to=mingo@kernel.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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).