All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Anand <panand@redhat.com>
To: Baoquan He <bhe@redhat.com>, Geoff Levand <geoff@infradead.org>
Cc: kexec@lists.infradead.org, kexec@lists.fedoraproject.org
Subject: Re: [PATCH RFC 5/6] arm64: Add support for binary image
Date: Wed, 22 Apr 2015 16:49:20 +0530	[thread overview]
Message-ID: <553783B8.1040304@redhat.com> (raw)
In-Reply-To: <20150422025305.GB4458@dhcp-16-116.nay.redhat.com>



On Wednesday 22 April 2015 08:23 AM, Baoquan He wrote:
> On 04/21/15 at 10:12am, Pratyush Anand wrote:
>>
>>
>> On Monday 20 April 2015 12:54 PM, Baoquan He wrote:
>>> On 04/16/15 at 10:17pm, Pratyush Anand wrote:
>>>>> This patch adds support to use binary image ie arch/arm64/boot/Image.
>>>>>
>>>>> Binary image does not have sufficient knowledge to extract page offset
>>>>> information, which is needed by kexec tool. Use a new command parameter
>>>>> --page-offset, so that user can provide page offset information for
>>>>> liner mapping.
>>>>>
>>>>> Signed-off-by: Pratyush Anand<panand@redhat.com>
>>>>> ---
>>> Seems there's a function get_kernel_page_offset used to get page_offset
>>> automatically in arm. arm64 should have it either.
>>>
>>>
>>
>> ARM still takes user option for --page-offset in user_page_offset
>> variable and then cross check that value with one found in
>> /proc/kallsyms.
>
> Well, this looks good. Try --page-offset and then fetch it in
> /proc/kallsysms if not specificed by user. ARM64 should have this too.
>
>>

OK... Will do that.

@Geoff: I will send this patch in two parts. First will apply on top of 
your patches. Second will apply after Takahiro's patch.

~Pratyush

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

  reply	other threads:[~2015-04-22 11:19 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 16:47 [PATCH RFC 0/6] Various fixes for purgatory and ARM64 Pratyush Anand
2015-04-16 16:47 ` [PATCH RFC 1/6] purgatory: Fix memcmp for src address increment Pratyush Anand
2015-04-17 16:55   ` Geoff Levand
2015-04-20  0:25     ` Simon Horman
2015-04-22 11:19       ` Pratyush Anand
2015-04-23  2:23         ` Simon Horman
2015-04-16 16:47 ` [PATCH RFC 2/6] purgatory: No need to sha256 update if ptr->len is zero Pratyush Anand
2015-04-17 16:58   ` Geoff Levand
2015-04-17 23:26     ` Pratyush Anand
2015-04-20  3:01   ` Baoquan He
2015-04-20  3:18     ` Pratyush Anand
2015-04-16 16:47 ` [PATCH RFC 3/6] arm64: allocate memory for other segments after kernel Pratyush Anand
2015-04-17 16:59   ` Geoff Levand
2015-04-20  3:21   ` Baoquan He
2015-04-21  4:19     ` Pratyush Anand
2015-04-21 10:06       ` AKASHI Takahiro
2015-04-22  6:16         ` AKASHI Takahiro
2015-04-16 16:47 ` [PATCH RFC 4/6] arm64: support reuse-cmdline option Pratyush Anand
2015-04-17 17:02   ` Geoff Levand
2015-04-16 16:47 ` [PATCH RFC 5/6] arm64: Add support for binary image Pratyush Anand
2015-04-17 17:07   ` Geoff Levand
2015-04-17 18:00     ` Geoff Levand
2015-04-17 23:27       ` Pratyush Anand
2015-04-20  7:24   ` Baoquan He
2015-04-21  4:42     ` Pratyush Anand
2015-04-22  2:53       ` Baoquan He
2015-04-22 11:19         ` Pratyush Anand [this message]
2015-04-16 16:47 ` [PATCH RFC 6/6] arm64: wait for transmit completion before next character transmission Pratyush Anand
2015-04-17  5:36   ` Minfei Huang
2015-04-17  5:37     ` Pratyush Anand
2015-04-20  2:58       ` Baoquan He
2015-04-20  3:34         ` Pratyush Anand
2015-04-17 17:22   ` Geoff Levand
2015-04-17 23:31     ` Pratyush Anand
2015-04-16 23:54 ` [PATCH RFC 0/6] Various fixes for purgatory and ARM64 Simon Horman
2015-04-17  1:27 ` Dave Young
2015-04-17  2:48   ` Pratyush Anand
2015-04-17 17:27 ` Geoff Levand

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=553783B8.1040304@redhat.com \
    --to=panand@redhat.com \
    --cc=bhe@redhat.com \
    --cc=geoff@infradead.org \
    --cc=kexec@lists.fedoraproject.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.