linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Paul Mackerras <paulus@samba.org>
Cc: Milton Miller <miltonm@bga.com>, linuxppc-dev@ozlabs.org
Subject: [PATCH 0/3] Kexec for PPC32 (6xx) machines
Date: Tue, 16 Dec 2008 19:22:17 +0300	[thread overview]
Message-ID: <20081216162217.GA3885@oksana.dev.rtsoft.ru> (raw)

Hi all,

This is Kexec part of the larger series[1] posted few months ago.
I eliminated Kdump part in this resend (will post it as a separate
entity later).

Milton Miller hinted that current PPC32 Kexec implementation may
not work on SMP hardware. I don't have any multi-core machines
handy to actually try and/or fix it, but support for SMP should be
straightforward: just need to bring the secondary CPUs down before
Kexec'ing (the code is already in the machine_kexec_64.c, just
needs to be factored out).

The arch/powerpc/Kconfig already states that the Kexec support
is experimental and may not work on certain hardware, so I don't
see any reason to add !SMP dependency.

Anyway, the majority of boards are UP and they don't need any fancy
care to work. So let's support them.

[1] http://ozlabs.org/pipermail/linuxppc-dev/2008-August/061161.html

-- 
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2

             reply	other threads:[~2008-12-16 16:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16 16:22 Anton Vorontsov [this message]
2008-12-16 16:22 ` [PATCH 1/3] powerpc: Setup OF properties for ppc32 kexec Anton Vorontsov
2008-12-16 16:23 ` [PATCH 2/3] powerpc: Make default kexec/crash_kernel ops implicit Anton Vorontsov
2008-12-21 23:08   ` Michael Ellerman
2008-12-22  0:11     ` Anton Vorontsov
2008-12-23  0:15       ` Michael Ellerman
2008-12-16 16:23 ` [PATCH 3/3] powerpc: Remove default kexec/crash_kernel ops assignments Anton Vorontsov

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=20081216162217.GA3885@oksana.dev.rtsoft.ru \
    --to=avorontsov@ru.mvista.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=miltonm@bga.com \
    --cc=paulus@samba.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).