All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Woods <brian.woods@xilinx.com>
To: Julien Grall <julien.grall@arm.com>
Cc: Brian Woods <brian.woods@xilinx.com>, nd <nd@arm.com>,
	Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] Errors with Loading Xen at a Certain Address
Date: Fri, 4 Oct 2019 08:36:55 -0700	[thread overview]
Message-ID: <20191004153655.GA5856@xilinx.com> (raw)
In-Reply-To: <edb70263-f98c-da0b-0e6a-859d6808b438@arm.com>

On Fri, Oct 04, 2019 at 10:49:28AM +0100, Julien Grall wrote:
> Hi Brian,
> 
> On 04/10/2019 01:25, Brian Woods wrote:
> >
> >In the log, there's:
> >(XEN) MODULE[0]: 0000000001400000 - 00000000015328f1 Xen
> >(XEN) MODULE[1]: 00000000076d2000 - 00000000076dc080 Device Tree
> >(XEN) MODULE[2]: 00000000076df000 - 0000000007fff364 Ramdisk
> >(XEN) MODULE[3]: 0000000000080000 - 0000000003180000 Kernel
> >(XEN)  RESVD[0]: 00000000076d2000 - 00000000076dc000
> >(XEN)  RESVD[1]: 00000000076df000 - 0000000007fff364
> >
> >Linux kernel	->   8_0000 - 318_0000
> >Xen		-> 140_0000 - 153_28f1
> >
> >There's something not quite right here... I'm guessing Xen was working
> >at the address before because it was out of the "range" of the Linux
> >kernel.  Now I guess I need to look into if it's a Xen or u-boot issue.
> 
> The loading address you wrote match the ones you seem to have requested in U-boot:
> 
> Filename 'yocto-Image'.
> Load address: 0x80000
> 
> Filename 'xen-custom.ub'.
> Load address: 0x1400000
> 
> But the size does not match the one you provided in the Device-Tree:
> 
> Bytes transferred = 18215424 (115f200 hex)
> 
> vs
> 
> 0x0000000003180000 - 0x0000000000080000 = 0x3100000
> 
> This is always a risk when you write in advance the size of the binaries and
> location in the Device-Tree. If you are using tftp/load from FS, it is much
> less risky to provide a U-boot script that will generate the Xen DT node.
> 
> Cheers,
> 
> -- 
> Julien Grall

Yeah.  When I went in and changed the end address in the device tree and
it all worked.  I'm guessing Xen could use some warnings and some other
things to alert the user that the device tree may need tweaking or at
the very least some checks.  It seems that the blame wasn't primarily on
Xen, although it didn't do anyone any favors.

-- 
Brian Woods

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

      reply	other threads:[~2019-10-04 15:37 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
2019-10-04  0:25                       ` Brian Woods
2019-10-04  9:49                         ` Julien Grall
2019-10-04 15:36                           ` Brian Woods [this message]

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=20191004153655.GA5856@xilinx.com \
    --to=brian.woods@xilinx.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=julien.grall@arm.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.