Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Nan <wangnan0@huawei.com>
To: Dave Young <dyoung@redhat.com>
Cc: Simon Horman <horms@verge.net.au>,
	kexec@lists.infradead.org, Geng Hui <hui.geng@huawei.com>
Subject: Re: [PATCH 0/3] kexec-tools: fix bugs and pass initrd position for arm
Date: Thu, 23 Jan 2014 12:17:10 +0800	[thread overview]
Message-ID: <52E097C6.9090509@huawei.com> (raw)
In-Reply-To: <20140123033851.GG3768@dhcp-16-126.nay.redhat.com>

On 2014/1/23 11:38, Dave Young wrote:
> On 01/23/14 at 10:56am, Wang Nan wrote:
>> On 2014/1/23 10:47, Dave Young wrote:
>>> On 01/22/14 at 06:52pm, Wang Nan wrote:
>>>> Hi,
>>>>
>>>> This patch series contains following bug fixes and cleanups for
>>>> kexec-tools on arm platform:
>>>>
>>>> Wang Nan (3):
>>>>   kexec: align initrd when no --image-size
>>>>   kexec: pass initrd position in dtb
>>>>   kexec: increase zImage compress ratio from 4 to 5
>>>
>>> One question:
>>> Is these kexec-tools patches enough for kexec work or still need the
>>> kernel patches you sent?
>>>
>>> Thanks
>>> Dave
>>>
>>
>> kexec will work without the kernel side patches, but the atag, kernel
>> cmdline, dtb information and kernel configuration must be carefully
>> adjusted.
>>
> 
> It does not work for me with below:
> kexec -l /boot/vmlinuz-`uname -r` --append=`cat /proc/cmdline` --dtb vexpress-v2p-ca9.dtb
> 
> The dtb and kexec kernel are exactly same with the 1st kernel.
> Is there any other things for setup in qemu, but probably it's different from your hardware
> setup..
> 
> Thanks
> Dave
> 

I only tried crash dump case. In my testing, following things need to be check:

1. When using dtb, the second kernel should disable CONFIG_ATAGS and CONFIG_ARM_APPENDED_DTB
2. In the second kernel, the memory information must be reconfigured using dtb or cmdline.

for example:

first kernel:
 memory {
  device_type = "memory";
  reg = <0x80000000 0x40000000>;
 };

if you want to load the second kernel at 0xa0000000: second kernel:
 memory {
  device_type = "memory";
  reg = <0xa0000000 0x20000000>;
 };

Pass a mem= option may also work, but when loading crash kernel, kexec-tools also append mem=
option to cmdline, they may conflict with each other.

The 3rd patch of my kernel patch is used to avoid the device tree reconfiguration, but it has not been
accepted.

Another thing: arm kernel must be loaded at a 128MB aligned position.





_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2014-01-23  4:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22 10:52 [PATCH 0/3] kexec-tools: fix bugs and pass initrd position for arm Wang Nan
2014-01-22 10:52 ` [PATCH 1/3] kexec: align initrd when no --image-size Wang Nan
2014-02-06  3:44   ` Dave Young
2014-01-22 10:52 ` [PATCH 2/3] kexec: pass initrd position in dtb Wang Nan
2014-02-06  3:58   ` Dave Young
2014-01-22 10:52 ` [PATCH 3/3] kexec: increase zImage compression ratio from 4 to 5 Wang Nan
2014-02-06  4:01   ` Dave Young
2014-01-23  2:02 ` [PATCH 0/3] kexec-tools: fix bugs and pass initrd position for arm Dave Young
2014-01-23  2:47 ` Dave Young
2014-01-23  2:56   ` Wang Nan
2014-01-23  3:38     ` Dave Young
2014-01-23  4:17       ` Wang Nan [this message]
2014-01-23  5:00         ` Dave Young

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=52E097C6.9090509@huawei.com \
    --to=wangnan0@huawei.com \
    --cc=dyoung@redhat.com \
    --cc=horms@verge.net.au \
    --cc=hui.geng@huawei.com \
    --cc=kexec@lists.infradead.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