From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Maxim Uvarov <muvarov@gmail.com>
Cc: horms@verge.net.au, kexec@lists.infradead.org
Subject: Re: kexec powerpc booke
Date: Fri, 14 May 2010 10:14:55 +0200 [thread overview]
Message-ID: <4BED067F.9000902@linutronix.de> (raw)
In-Reply-To: <AANLkTikSH5inonuS6b1n_ZEmQLYoGN0Py0L_RMBEdwJS@mail.gmail.com>
Maxim Uvarov wrote:
> Sebastian,
Maxim,
> I saw you did a lot of work for powerpc booke boards. What is the
> current status of your patches?
They worked the last time I checked on v31. Userland is useable however
you have to tweak the dtb file. Recently I hacked kexec-tools so they can
suck the dtb from /proc/device-tree while I've been traveling but I had no
time to test it. Ah and initrd support as well.
> Will they be included to main line?
I hope so. I fixed what Kumar did not like in the last version. As far as
I know, he had no time review it.
>
> As I understand 8572 board has to work with your kernel:
>
> http://git.breakpoint.cc/cgi-bin/gitweb.cgi?p=bigeasy/linux.git;a=shortlog;h=refs/heads/kexec_booke
Not really. 8572 is SMP and SMP is not supported at the moment. The plan
for SMP was
- pin userland to the boot cpu
- halt the other cpu in kernel during kexec
- the what we do right now
- use the ipic to reset the cpu and bring it back to virgin state.
That was only the plan I made. Halt the CPU means spin I think so you
should respect the "reserved region" in dtb.
> I tried this kernel and result is hang after "Bye!". Which kexec-tools
> is suitable for your kernel? Can you please throw them to me?
[0] is what I used last time I checked and Simon merged it. So it should
work. I try to rebase the kernel to v33 and see if it got broken somehow.
Maybe I should merge console support so it is easier to debug. The plan
here was to set the uart type & address into the purgatory code from what
we know from the dtb. However I have no idea how to set the MMU mapping
for it.
> I posted the patch, which make 83xx classic powerpc work (not booke).
> Both kexec and kdump. Now I want to do booke boards workable.
> That's why I need to know how things are now. What is already done and
> what is needed.
I'm supprised that the UP part is not working. I look at it. I post the
proc/dtb-suck-in patches once they are tested. I could push it to my pubic
git tree if you want to look at them. SMP support is missing and I haven't
looked at kdump at all.
[0]
http://git.breakpoint.cc/cgi-bin/gitweb.cgi?p=bigeasy/kexec-tools.git;a=shortlog;h=refs/heads/ppc32
Sebastian
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next parent reply other threads:[~2010-05-14 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTikSH5inonuS6b1n_ZEmQLYoGN0Py0L_RMBEdwJS@mail.gmail.com>
2010-05-14 8:14 ` Sebastian Andrzej Siewior [this message]
2010-05-17 18:32 ` kexec powerpc booke Sebastian Andrzej Siewior
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=4BED067F.9000902@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=muvarov@gmail.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