linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "wilbur.chan" <wilbur512@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re:[PATCH 1/2] powerpc: add kexec support on FSL-Book-E
Date: Wed, 26 Aug 2009 00:09:36 +0800	[thread overview]
Message-ID: <e997b7420908250909k74208353v81240eebd3d0896a@mail.gmail.com> (raw)
In-Reply-To: <20090804194135.GA19171@www.tglx.de>

2009/8/5, Sebastian Andrzej Siewior <bigeasy@linutronix.de>:

> There is no SMP support. The other CPUs are not halted/resumed. At the
> time of writing it I did not have a SMP machine so I did not implement
> it.
> Sebastian
>
Hi  Sebastian,

Recently I've implemented  non-SMP kexec on MPC8572 and P2020ds(2G ram).



I modified your

misc_32.S that , I setuped  two '1G' entries  after the "rfi"
instruction, so that I did

not  need to setup  mapping for instruction address.

As for SMP supporting,I tried to close one of the CPUs in
default_machine_kexec,

and found that , when cpu1  closed  ,and if the second kernel is NON-

SMP,everything went well.so I added some code in

kexec-tools, to make sure the 'kexec' process was running on CPU 0.


So, there left one problem, I can not start the second SMP-kernel,
even if I  closed

CPU1.  Any suggestions?


PTW:

no-smp ---> no-smp.........OK
no-smp --->smp...............OK

smp(with cpu1 closed)---->no-smp..............OK
smpw(with cpu1 closed)---->smp ................FAILED


regards,

wilbur

  reply	other threads:[~2009-08-25 16:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-02  1:25 Re:[PATCH 1/2] powerpc: add kexec support on FSL-Book-E wilbur.chan
2009-08-04 19:41 ` Sebastian Andrzej Siewior
2009-08-25 16:09   ` wilbur.chan [this message]
2009-08-28 19:35     ` [PATCH " Sebastian Andrzej Siewior
2009-09-06 14:27       ` wilbur.chan

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=e997b7420908250909k74208353v81240eebd3d0896a@mail.gmail.com \
    --to=wilbur512@gmail.com \
    --cc=bigeasy@linutronix.de \
    --cc=linuxppc-dev@lists.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).