From: Michael Ellerman <mpe@ellerman.id.au>
To: Mike Rapoport <rppt@kernel.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Mike Rapoport <rppt@linux.ibm.com>
Subject: Re: [PATCH] powerpc: add support for folded p4d page tables
Date: Tue, 07 Jan 2020 15:24:15 +1100 [thread overview]
Message-ID: <87tv5728sw.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20200106060217.GA5444@rapoport-lnx>
Mike Rapoport <rppt@kernel.org> writes:
> On Mon, Jan 06, 2020 at 02:31:41PM +1100, Michael Ellerman wrote:
>> Mike Rapoport <rppt@kernel.org> writes:
>> > Any updates on this?
>>
>> It's very ... big, and kind of intrusive.
>
> I've tried to split it to several smaller ones, but I couldn't find a way
> to do it without breaking bisectability.
Yeah I didn't necessarily mean splitting it, it's just a lot of churn.
It seems to break qemu mac99 booting pmac32 defconfig, haven't had time
to look any further:
Loading compiled-in X.509 certificates
rtc-generic rtc-generic: setting system clock to 2020-01-07T02:42:59 UTC (1578364979)
BUG: Unable to handle kernel unaligned access at 0xf10af004
Faulting instruction address: 0xc01cc6c4
Vector: 600 (Alignment) at [ef0b5de0]
pc: c01cc6c4: f_dupfd+0x6c/0xb8
lr: c01cc698: f_dupfd+0x40/0xb8
sp: ef0b5e98
msr: 9032
dar: f10af004
dsisr: 40000140
current = 0xef0b0000
pid = 1, comm = swapper
Linux version 5.5.0-rc2+ (michael@alpine1-p1) (gcc version 9.2.1 20191127 (Ubuntu 9.2.1-20ubuntu3)) #8 Tue Jan 7 13:38:04 AEDT 2020
enter ? for help
[ef0b5eb8] c000550c console_on_rootfs+0x44/0x90
[ef0b5ed8] c090d7c0 kernel_init_freeable+0x1a4/0x24c
[ef0b5f18] c0005770 kernel_init+0x18/0x108
[ef0b5f38] c0017274 ret_from_kernel_thread+0x14/0x1c
FAIL! Booting BE pmac32
cheers
prev parent reply other threads:[~2020-01-07 4:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 15:09 Mike Rapoport
2019-12-09 17:46 ` Christophe Leroy
2019-12-09 18:33 ` Matthew Wilcox
2020-01-02 8:11 ` Mike Rapoport
2020-01-02 16:42 ` Christophe Leroy
2020-01-05 7:02 ` Mike Rapoport
2020-01-07 11:12 ` Christophe Leroy
2020-01-06 3:31 ` Michael Ellerman
2020-01-06 6:02 ` Mike Rapoport
2020-01-07 4:24 ` Michael Ellerman [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=87tv5728sw.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=rppt@kernel.org \
--cc=rppt@linux.ibm.com \
/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