From: geoff@infradead.org (Geoff Levand)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/4] arm64: Add support for binary image files
Date: Fri, 29 Jul 2016 10:19:55 -0700 [thread overview]
Message-ID: <1469812795.16559.42.camel@infradead.org> (raw)
In-Reply-To: <20160729171552.GB478@localhost.localdomain>
On Fri, 2016-07-29 at 22:45 +0530, Pratyush Anand wrote:
> Hi Geoff,
>
> On 29/07/2016:10:02:40 AM, Geoff Levand wrote:
> > On Fri, 2016-07-29 at 09:05 +0530, Pratyush Anand wrote:
> >
> > > See kexec/crashdump-elf.c:FUNC()
> > > We have:
> > > 223 phdr->p_vaddr = phys_to_virt(elf_info,
> > > mstart);
> > >
> >
> > These patches don't support kdump.
>
> OK, so you suggest that I should keep this patch as it is and add -
> -page-offset
> in corresponding kdump patch. I can do that, no issue.
Yes, this is an issue related to kdump, so let's discuss it in that
context.
-Geoff
next prev parent reply other threads:[~2016-07-29 17:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 20:18 [PATCH v2 0/4] arm64 kexec-tools patches Geoff Levand
2016-07-26 20:18 ` [PATCH v2 1/4] kexec: (bugfix) calc correct end address of memory ranges in device tree Geoff Levand
2016-07-26 20:18 ` [PATCH v2 4/4] arm64: Add support for binary image files Geoff Levand
2016-07-28 4:01 ` Pratyush Anand
2016-07-28 18:04 ` Geoff Levand
2016-07-29 3:35 ` Pratyush Anand
2016-07-29 17:02 ` Geoff Levand
2016-07-29 17:15 ` Pratyush Anand
2016-07-29 17:19 ` Geoff Levand [this message]
2016-08-04 4:51 ` AKASHI Takahiro
2016-08-04 5:11 ` Pratyush Anand
2016-07-26 20:18 ` [PATCH v2 3/4] arm64: Add arm64 kexec support Geoff Levand
2016-07-28 4:10 ` Pratyush Anand
2016-07-28 17:33 ` Geoff Levand
2016-07-26 20:18 ` [PATCH v2 2/4] kexec: Add common device tree routines 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=1469812795.16559.42.camel@infradead.org \
--to=geoff@infradead.org \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).