public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: add kexec jump support V2
Date: Thu, 26 Mar 2009 02:22:26 +0000	[thread overview]
Message-ID: <49CAE6E2.1070409@renesas.com> (raw)
In-Reply-To: <20090318085129.5943.83795.sendpatchset@rx1.opensource.se>

Hi,all.

I'm sorry that I could not check this patch.

This patch became compilation error in SH2/SH2A, because there are
not a spc register and a ssr register in SH2.[0]
I don't have environment of SH2 and I don't know whether I work
by these measures.
Do you have somebody, environment?

[0]: http://kisskb.ellerman.id.au/kisskb/buildresult/271654/

Best regards,
 Nobuhiro

Magnus Damm wrote:
> From: Magnus Damm <damm@igel.co.jp>
> 
> Add kexec jump support to the SuperH architecture V2.
> 
> Similar to the x86 implementation, with the following
> exceptions:
> 
> - Instead of separating the assembly code flow into
> two parts for regular kexec and kexec jump we use a
> single code path. In the assembly snippet regular
> kexec is just kexec jump that never comes back.
> 
> - Instead of using a swap page when moving data between
> pages the page copy assembly routine has been modified
> to exchange the data between the pages using registers.
> 
> - We walk the page list twice in machine_kexec() to
> do and undo physical to virtual address conversion.
> 
> Signed-off-by: Magnus Damm <damm@igel.co.jp>



  reply	other threads:[~2009-03-26  2:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18  8:51 [PATCH] sh: add kexec jump support V2 Magnus Damm
2009-03-26  2:22 ` Nobuhiro Iwamatsu [this message]
2009-03-26  4:35 ` Paul Mundt
2009-03-26  8:09 ` Nobuhiro Iwamatsu

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=49CAE6E2.1070409@renesas.com \
    --to=iwamatsu.nobuhiro@renesas.com \
    --cc=linux-sh@vger.kernel.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