From: Nikolai Zhubr <n-a-zhubr@yandex.ru>
To: OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
linux-mips@linux-mips.org
Subject: kexec on mips
Date: Mon, 20 Feb 2012 23:13:16 +0400 [thread overview]
Message-ID: <4F429B4C.9070600@yandex.ru> (raw)
Hello all,
I'm running both openwrt and debian on a mips-based wndr3800 netgear
router/ap and I'm using kexec to arrange kind of dual-boot in a safe and
comfortable manner.
Now, I've found that the following is critical for kexec to actually work:
--- arch/mips/kernel/machine_kexec.c.orig 2012-02-08
01:58:13.000000000 +0300
+++ arch/mips/kernel/machine_kexec.c 2012-02-20 22:19:11.000000000 +0300
@@ -52,7 +52,7 @@
reboot_code_buffer =
(unsigned long)page_address(image->control_code_page);
- kexec_start_address = image->start;
+ kexec_start_address = (unsigned long) phys_to_virt(image->start);
kexec_indirection_page =
(unsigned long) phys_to_virt(image->head & PAGE_MASK);
I've found that in openwrt repository this change was present (among
others) in a big patchset targeted for kernel 2.6.30 and now it is still
present as a small separate patch for 2.6.38
(target/linux/generic/patches-2.6.38/303-mips_fix_kexec.patch) and maybe
others. Meanwhile, the latest _stable_ openwrt for the moment (backfire
10.03.1) was released with kernel 2.6.32 without this patch so I had to
dig through some forums to find the reason of kexec not working
out-of-the-box. I've just now checked and the latest kernel.org's stable
kernel (3.2.6) does not seem to include this either. Ok, since I know
the secret already I'll fix it for myself anytime, but maybe some kind
soul could just submit this _one_ line upstream? I'd say this feature is
really handy in some cases.
Thank you.
(Please CC me, I'm not subscribed to linux-mips)
Nikolai
reply other threads:[~2012-02-20 19:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F429B4C.9070600@yandex.ru \
--to=n-a-zhubr@yandex.ru \
--cc=linux-mips@linux-mips.org \
--cc=openwrt-devel@lists.openwrt.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