From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jimi Xenidis <jimix@watson.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Kexec initial registers
Date: Sun, 16 Jul 2006 11:59:15 -0400 [thread overview]
Message-ID: <1153065556.5905.4.camel@localhost.localdomain> (raw)
In-Reply-To: <28C15305-BE9F-4EE7-93A2-437EAEA7B886@watson.ibm.com>
On Sat, 2006-07-15 at 22:10 -0400, Jimi Xenidis wrote:
> On Jul 14, 2006, at 5:08 PM, Benjamin Herrenschmidt wrote:
>
> > On Fri, 2006-07-14 at 12:02 -0400, Jimi Xenidis wrote:
> >> This is what I have so far:
> >>
> >> r3: address of device tree blob
> >> r4: address that kernel was loaded
> >> r5: not OF (=0)
> >
> > Correct and that's all that should be needed
> >
> >> r13: local_paca address (0?)
> >
> > You shouldn't have to care about r13 at all, it should be set by the
> > kernel before it's used. If not, please let us know as that means
> > there
> > is a bug :)
>
> Not! 99.99% :)
> When loading a kernel under Xen using kexec we set r1-r5 and set all
> other GPRS to all 5's (cuz we can) with CONFIG_PPC_EARLY_DEBUG=y and
> all hell breaks loose in the first printk()/DBG() from early_setup()
> for:
> kernel/printk.c:506
> 506 spin_lock_irqsave(&logbuf_lock, flags);
>
> where is access local_paca.
>
> I think everyone else (ot just the sane ones) just sets all GPRS to 0
Then we have a bug and we need to initialize local_paca before we call
early_setup...
Ben.
next prev parent reply other threads:[~2006-07-16 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 16:02 Kexec initial registers Jimi Xenidis
2006-07-14 21:08 ` Benjamin Herrenschmidt
2006-07-16 2:10 ` Jimi Xenidis
2006-07-16 15:59 ` Benjamin Herrenschmidt [this message]
2006-07-16 16:18 ` Benjamin Herrenschmidt
2006-07-17 1:22 ` Michael Ellerman
2006-07-19 17:17 ` Milton Miller
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=1153065556.5905.4.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=jimix@watson.ibm.com \
--cc=linuxppc-dev@ozlabs.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).