From: Brian Woods <brian.woods@xilinx.com>
To: Julien Grall <julien.grall@arm.com>
Cc: Brian Woods <brian.woods@xilinx.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] Errors with Loading Xen at a Certain Address
Date: Thu, 3 Oct 2019 11:15:47 -0700 [thread overview]
Message-ID: <20191003181547.GA13953@xilinx.com> (raw)
In-Reply-To: <ade177bc-003f-edcc-47fe-d1014d638990@arm.com>
On Thu, Oct 03, 2019 at 06:08:45PM +0100, Julien Grall wrote:
> Hi,
>
> On 03/10/2019 00:20, Brian Woods wrote:
> >On Wed, Oct 02, 2019 at 02:22:49PM -0700, Brian Woods wrote:
> >>That's odd. I know I copied your and Stefano's email addresses from the
> >>MAINTAINERS file but under my sent emails it shows it has having no
> >>CCs... PEBCAK I guess. My apologies.
> >>
> >>I'll go ahead add those and see if that leads to anything.
> >>
> >>--
> >>Brian Woods
> >
> >Ok, I added:
> > printk("BW_DEBUG: 01 count_info=0x%016lx\n",
> > mfn_to_page(_mfn(0x01533))->count_info);
> >In some places. I'm not sure about some of the earlier ones (the ones
> >before the UART is set up), but all of the ones afterwards that
> >actually get output are:
> > BW_DEBUG: 11 count_info=0x0180000000000000
> >
> >Is it worth trying to figure out where the printk buffer is and reading
> >it really early on?
> >
>
> If you haven't enable EARLY_PRINTK in Xen, then you may want to do it. This
> would help you to understand where the page->count_info is not zeroed.
>
>
> Cheers,
>
> --
> Julien Grall
Ah, I'm not used to some of the Arm-isms in Xen yet.
(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().
--
Brian Woods
_______________________________________________
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 18:16 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 [this message]
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
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=20191003181547.GA13953@xilinx.com \
--to=brian.woods@xilinx.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=julien.grall@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.