From: Michael Ellerman <mpe@ellerman.id.au>
To: Andreas Schwab <schwab@linux-m68k.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: linuxppc-dev@lists.ozlabs.org, Paul Mackerras <paulus@samba.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/32s: Setup the early hash table at all time.
Date: Fri, 30 Oct 2020 16:19:07 +1100 [thread overview]
Message-ID: <87y2jouw8k.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <87wnz8vizm.fsf@igel.home>
Andreas Schwab <schwab@linux-m68k.org> writes:
> On Okt 01 2020, Christophe Leroy wrote:
>
>> At the time being, an early hash table is set up when
>> CONFIG_KASAN is selected.
>>
>> There is nothing wrong with setting such an early hash table
>> all the time, even if it is not used. This is a statically
>> allocated 256 kB table which lies in the init data section.
>>
>> This makes the code simpler and may in the future allow to
>> setup early IO mappings with fixmap instead of hard coding BATs.
>>
>> Put create_hpte() and flush_hash_pages() in the .ref.text section
>> in order to avoid warning for the reference to early_hash[]. This
>> reference is removed by MMU_init_hw_patch() before init memory is
>> freed.
>
> This breaks booting on the iBook G4.
Do you get an oops or anything?
cheers
next prev parent reply other threads:[~2020-10-30 5:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 15:35 [PATCH] powerpc/32s: Setup the early hash table at all time Christophe Leroy
2020-10-09 6:03 ` Michael Ellerman
2020-10-29 21:07 ` Andreas Schwab
2020-10-30 5:19 ` Michael Ellerman [this message]
2020-10-30 9:09 ` Andreas Schwab
2020-10-30 13:00 ` Christophe Leroy
2020-10-30 13:11 ` Andreas Schwab
2020-11-03 7:41 ` Christophe Leroy
2020-11-03 8:43 ` Andreas Schwab
2020-11-03 8:56 ` Andreas Schwab
2020-11-03 18:58 ` Serge Belyshev
2020-11-04 6:44 ` Christophe Leroy
2020-11-04 7:57 ` Serge Belyshev
2020-11-04 9:28 ` Serge Belyshev
2020-11-04 14:53 ` Serge Belyshev
2020-11-07 9:12 ` Christophe Leroy
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=87y2jouw8k.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=schwab@linux-m68k.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).