All of lore.kernel.org
 help / color / mirror / Atom feed
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 19:23:23 +0000	[thread overview]
Message-ID: <c2ea24d9-6bd0-a5b2-9ea1-b3bfe5e30a02@arm.com> (raw)
In-Reply-To: <20191003181547.GA13953@xilinx.com>

Hi,

On 03/10/2019 19:15, Brian Woods wrote:
> On Thu, Oct 03, 2019 at 06:08:45PM +0100, Julien Grall wrote:
> (XEN) BW_DEBUG: .6 count_info=0x0000000000000000
> (XEN) Domain heap initialised
> (XEN) BW_DEBUG: 01 count_info=0x0180000000000000
> 
> Those debug messages sandwich end_boot_allocator() in start_xen().

hmmm, looking back at the thread, the WARN_ON() I suggested is actually 
incorrect. :/ Sorry for that. It should be:

WARN_ON(mfn_x(page_to_mfn(pg + i)) == 0x01533);

Note the "i" instead of "1".

If the WARN_ON() is triggered between the two calls, then it would mean 
we are giving page to the boot allocator.

This would imply that next_modules() or dt_unreserved_regions() is not 
working as expected (i.e. carving out any modules).

Also, could you send your log with early printk enabled?

Cheers,

-- 
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-10-03 19:24 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 [this message]
2019-10-03 20:24                   ` Brian Woods
2019-10-03 21:20                     ` Julien Grall
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=c2ea24d9-6bd0-a5b2-9ea1-b3bfe5e30a02@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.