linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: geoff@infradead.org (Geoff Levand)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/3] arm64: Add arm64 kexec support
Date: Wed, 10 Aug 2016 09:54:53 -0700	[thread overview]
Message-ID: <1470848093.19503.54.camel@infradead.org> (raw)
In-Reply-To: <20160810035743.GA27500@localhost.localdomain>

On Wed, 2016-08-10 at 09:27 +0530, Pratyush Anand wrote:
> This is what is being printed by kexec-tools:
> 
> elf_arm64_load: e_entry:       fffffc0008080000 -> 0000004000080000
> elf_arm64_load: p_vaddr:       fffffc0008080000 -> 0000004000080000
> elf_arm64_load: header_offset: 0000000000000000
> elf_arm64_load: text_offset:   0000000000080000
> elf_arm64_load: image_size:    00000000013a0000
> elf_arm64_load: phys_offset:   0000004000000000
> elf_arm64_load: page_offset:   fffffc0008000000
> 
> kernel is having 42 VA Bits, so a debug print in kernel says that
> PAGE_OFFSET=fffffe0000000000. Notice the difference between the values
> calculated by kernel and kexec-tools. Isn't it confusing? 

I renamed page_offset to vp_offset.

-Geoff

  reply	other threads:[~2016-08-10 16:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-08 22:19 [PATCH v3 0/3] arm64 kexec-tools patches Geoff Levand
2016-08-08 22:19 ` [PATCH v3 2/3] arm64: Add arm64 kexec support Geoff Levand
2016-08-09  3:05   ` AKASHI Takahiro
2016-08-09 18:30     ` Geoff Levand
2016-08-09 19:05   ` [PATCH v3.1 " Geoff Levand
2016-08-10  3:57   ` [PATCH v3 " Pratyush Anand
2016-08-10 16:54     ` Geoff Levand [this message]
2016-08-08 22:19 ` [PATCH v3 1/3] kexec: Add common device tree routines Geoff Levand
2016-08-08 22:19 ` [PATCH v3 3/3] arm64: Add support for binary image files 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=1470848093.19503.54.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).