From: Shawn Jin <shawnxjin@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Scott Wood <scottwood@freescale.com>, ppcdev <linuxppc-dev@ozlabs.org>
Subject: Re: Relocating bootwrapper causes kernel panic
Date: Sun, 8 Aug 2010 22:55:40 -0700 [thread overview]
Message-ID: <AANLkTikkRTNU=HWdpvTH-PryeL1mfA12HHFjkXUO8zaU@mail.gmail.com> (raw)
In-Reply-To: <1281134958.2168.39.camel@pasglop>
>> > >> I think the cause is clear now. But how to fix it? Two questions:
>> > >> 2. If the DTLB miss exception handler is not the right guy to load =
a
>> > >> proper TLB entry, how can I set one entry based on the link_address
>> > >> and the address of the flat dt blob?
>> > >
>> > > Given how early in the boot process it is, it's probably going to ne=
ed
>> > > to be handled specially.
>> >
>> > What APIs can I use to set up DTLBs?
>>
>> I don't think there is one that works on 8xx. =A0You'll could hack up
>> initial_mmu, or else write some C code to insert an 8xx TLB entry.
>
> Yup, I think he just ends up getting out of the initial mapping which is
> smallish on 8xx, no ? Might be worth sticking in one more entry during
> boot...
If CONFIG_PIN_TLB is on, two more entries are pinned down, which gives
16MB mappings. Just curious. Why is there only one entry by default?
what's the trade-off to pin down all 4 entries?
THanks,
-Shawn.
prev parent reply other threads:[~2010-08-09 5:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 4:11 Relocating bootwrapper causes kernel panic Shawn Jin
2010-08-05 5:13 ` Shawn Jin
2010-08-05 7:23 ` Shawn Jin
2010-08-05 17:37 ` Scott Wood
2010-08-05 18:33 ` Shawn Jin
2010-08-05 18:46 ` Scott Wood
2010-08-06 22:49 ` Benjamin Herrenschmidt
2010-08-09 5:55 ` Shawn Jin [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='AANLkTikkRTNU=HWdpvTH-PryeL1mfA12HHFjkXUO8zaU@mail.gmail.com' \
--to=shawnxjin@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).