linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Michael Ellerman <mpe@ellerman.id.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/8xx: Fix permanently mapped IMMR region.
Date: Tue, 26 Nov 2019 08:01:13 +0000	[thread overview]
Message-ID: <d22ac38c-0b03-fbc0-88d1-899e356fa487@c-s.fr> (raw)
In-Reply-To: <87sgmlcu1x.fsf@mpe.ellerman.id.au>



On 11/18/2019 11:17 AM, Michael Ellerman wrote:
> Christophe Leroy <christophe.leroy@c-s.fr> writes:
>> When not using large TLBs, the IMMR region is still
>> mapped as a whole block in the FIXMAP area.
>>
>> Do not remove pages mapped in the FIXMAP region when
>> initialising paging.
>>
>> Properly report that the IMMR region is block-mapped even
>> when not using large TLBs.
>>
>> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
>> ---
>>   arch/powerpc/mm/mem.c        |  8 --------
>>   arch/powerpc/mm/nohash/8xx.c | 13 +++++++------
>>   2 files changed, 7 insertions(+), 14 deletions(-)
> 
> This blows up pmac32_defconfig + qemu mac99 for me with:
> 
>    NET: Registered protocol family 1
>    RPC: Registered named UNIX socket transport module.
>    RPC: Registered udp transport module.
>    RPC: Registered tcp transport module.
>    RPC: Registered tcp NFSv4.1 backchannel transport module.
>    PCI: CLS 0 bytes, default 32
>    Trying to unpack rootfs image as initramfs...
>    BUG: Unable to handle kernel data access on write at 0xfffdf000

I tested it with pmac32_defconfig and qemu mac99 and don't get the problem:

NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 32
Initialise system trusted keyrings
workingset: timestamp_bits=30 max_order=15 bucket_order=0
NFS: Registering the id_resolver key type
Key type id_resolver registered
...

Looks like I don't get that 'Trying to unpack rootfs image as 
initramfs...', do you change anything to pmac32_defconfig ?

Anyway, when rebasing this patch on next branch, only the 
arch/powerpc/mm/nohash/8xx.c change remains. The other part is already 
applied through another patch.

So I believe the remaining part is safe to apply

Christophe


      parent reply	other threads:[~2019-11-26  8:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-23  9:56 [PATCH] powerpc/8xx: Fix permanently mapped IMMR region Christophe Leroy
2019-11-18 11:17 ` Michael Ellerman
2019-11-19 17:49   ` Christophe Leroy
2019-11-26  8:01   ` Christophe Leroy [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=d22ac38c-0b03-fbc0-88d1-899e356fa487@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.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).