From: Julien Grall <julien.grall@arm.com>
To: Brian Woods <brian.woods@xilinx.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, nd <nd@arm.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [Xen-devel] Errors with Loading Xen at a Certain Address
Date: Thu, 3 Oct 2019 22:20:36 +0100 [thread overview]
Message-ID: <3764ed03-e2a8-31e4-0e73-0bd3d88434ca@arm.com> (raw)
In-Reply-To: <20191003202457.GA4040@xilinx.com>
Hi Brian,
On 10/3/19 9:24 PM, Brian Woods wrote:
> On Thu, Oct 03, 2019 at 07:23:23PM +0000, Julien Grall wrote:
> There's a WARN_ON() between the two debug printks calls I shared above.
Looking at the log, the MFN seems to correspond to the one right after
Xen (0000000001400000 - 00000000015328f1) in memory.
So it is normal to have the page given to the boot allocator. However, I
am not entirely sure which bit of init_done() is giving the page again
to xenheap.
It is unlikely to be free_init_memory() because it deal with the init
section that is not at the end of the binary.
This would leave discard_initial_modules() but there are a check to skip
Xen module.
The call stack only print the address and not the symbol because it
unregistered the symbols for init. See unregister_init_virtual_memory().
(XEN) Xen call trace:
(XEN) [<000000000021c1a8>] page_alloc.c#free_heap_pages+0x1a8/0x614 (PC)
(XEN) [<000000000021c1a8>] page_alloc.c#free_heap_pages+0x1a8/0x614 (LR)
(XEN) [<000000000021e900>] page_alloc.c#init_heap_pages+0x3d4/0x564
(XEN) [<000000000021eb24>] init_domheap_pages+0x94/0x9c
(XEN) [<00000000002b83ec>] 00000000002b83ec
(XEN) [<00000000002b8904>] 00000000002b8904
(XEN) [<0000000000260a3c>] setup.c#init_done+0x10/0x20
(XEN) [<00000000002b99ac>] 00000000002b99ac
You should be able to use addr2line on the address with Xen binary.
I have the feeling this will point to discard_initial_modules() as this
is an init function and the symbol should not be printed.
But, I can't see anything obviously wrong in the function... So I am not
entirely sure what could be the next steps.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-10-03 21:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 0:32 [Xen-devel] Errors with Loading Xen at a Certain Address Brian Woods
[not found] ` <48c9fc54-553e-3b6b-bad2-dbad35991df0@arm.com>
2019-10-02 16:52 ` Julien Grall
2019-10-02 18:56 ` Brian Woods
2019-10-02 19:59 ` Julien Grall
2019-10-02 21:22 ` Brian Woods
2019-10-02 23:20 ` Brian Woods
2019-10-03 17:08 ` Julien Grall
2019-10-03 18:15 ` Brian Woods
2019-10-03 19:23 ` Julien Grall
2019-10-03 20:24 ` Brian Woods
2019-10-03 21:20 ` Julien Grall [this message]
2019-10-04 0:25 ` Brian Woods
2019-10-04 9:49 ` Julien Grall
2019-10-04 15:36 ` Brian Woods
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=3764ed03-e2a8-31e4-0e73-0bd3d88434ca@arm.com \
--to=julien.grall@arm.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=brian.woods@xilinx.com \
--cc=nd@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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.