Re: [Xen-devel] Errors with Loading Xen at a Certain Address

[Brian Woods <brian.woods@xxxxxxxxxx>]

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@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel