From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2,6/7] mm: convert generic code to 5-level paging
Date: Tue, 14 Mar 2017 19:55:07 +0100 [thread overview]
Message-ID: <15847703.KEZMYLnFVy@diego> (raw)
In-Reply-To: <20170314170625.gwlfjlxooij3elsd@node.shutemov.name>
Am Dienstag, 14. M?rz 2017, 20:06:25 CET schrieb Kirill A. Shutemov:
> On Tue, Mar 14, 2017 at 05:14:22PM +0100, Heiko St?bner wrote:
> > [added arm64 maintainers and arm list to recipients]
> >
> > Hi,
> >
> > Am Donnerstag, 9. M?rz 2017, 17:24:07 CET schrieb Kirill A. Shutemov:
> > > Convert all non-architecture-specific code to 5-level paging.
> > >
> > > It's mostly mechanical adding handling one more page table level in
> > > places where we deal with pud_t.
> > >
> > > Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> > > Acked-by: Michal Hocko <mhocko@suse.com>
> >
> > This breaks (at least) arm64 Rockchip platforms it seems.
> >
> > 4.11-rc1 worked just fine, while 4.11-rc2 kills the systems and I've
> > bisected it down to this one commit.
>
> Have you tried current Linus' tree? There is important fix:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i
> d=ce70df089143c49385b4f32f39d41fb50fbf6a7c
thanks for the pointer ... my arm64 board seem to boot now again.
While I did look for responses to the original series [0] + [1], where there
weren't any, I didn't think to just look into Linus' tree if there was some
fixup already.
So sorry for the noise and all seems well now
Heiko
[0] https://lkml.org/lkml/2017/3/9/442
[1] https://patchwork.kernel.org/patch/9613445/
prev parent reply other threads:[~2017-03-14 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170309142408.2868-7-kirill.shutemov@linux.intel.com>
2017-03-14 16:14 ` [PATCHv2,6/7] mm: convert generic code to 5-level paging Heiko Stübner
2017-03-14 17:06 ` Kirill A. Shutemov
2017-03-14 18:55 ` Heiko Stübner [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=15847703.KEZMYLnFVy@diego \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.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).