Re: [Xen-users] Starting to port xen on beagleboard-x15 (GSoC 2019 project)

[Iain Hunter <drhunter95@xxxxxxxxx>]

I can't remember the history of that patch. What I couldn't figure out
today was what its effect would be.  I could not find any u-boot code
that used the CONFIG_XXX values added in the patch.
So, best ignore it.

Do you have an emulator available yet?
If so the easiest way I found to debug this type of issue was to:

1. Insert an infinite loop just before where I thought I had a problem
   - in a .S file with
 loopHere: b loopHere

- in a C file with

volatile unsigned char loopHere=1;

function()
{  ....
   while(loopHere);
   ....
}

2 boot the board
3 connect the emulator to the target and then load the symbols for the
executable (u-boot.img or xen)
4 in the emulator set the PC to first instruction after the loop and
then step over the code. Then you can check the register values to see
if hypevisor is enabled etc

Iain

On Mon, 17 Jun 2019 at 09:53, Denis Obrezkov <denisobrezkov@xxxxxxxxx> wrote:
>
> Hi,
>
> On 6/17/19 10:11 AM, Iain Hunter wrote:
> > Hi Denis,
> >
> > patch 0004 was not actually applied to the u-boot build (and should
> > have been removed from the patch set). The only change that was
> > applied was 0001-for-xen-build-set-envboot-as-default-mmc.patch (line
> > 123 in build-x15-xen.sh).
> But only the fourth patch changes something related to hypervisor?
> Also, I boot via tftp not via mmc. Should I use the patch?
> >
> > Do you have CONFIG_ARMV7_LPAE=y in your configs/am57xx_evm_defconfig
> > file? and is this the defconfig you have selected?
> > Iain
> yes, to both questions.
> >
> >
> > On Sun, 16 Jun 2019 at 23:29, Denis Obrezkov <denisobrezkov@xxxxxxxxx> 
> > wrote:
> >>
> >> Hi,
> >>
> >> On 6/16/19 10:53 PM, Julien Grall wrote:
> >>> Hi,
> >>>
> >>> On 6/16/19 9:46 PM, Denis Obrezkov wrote:
> >>>> On 6/16/19 10:18 PM, Julien Grall wrote:
> >>>>>
> >>>>>
> >>>>> On 6/16/19 4:19 PM, Denis Obrezkov wrote:
> >>>>>> Hello,
> >>>>>> I was trying to boot xen on bb-x15, here is my starting point:
> >>>>>> I built xen with:
> >>>>>> make dist-xen debug=y XEN_TARGET_ARCH=arm32
> >>>>>> CROSS_COMPILE=arm-linux-gnueabihf- CONFIG_EARLY_PRINTK=omap5432
> >>>>>> (omap5432 and omap5729 have the same serial debug address)
> >>>>>> and I got the output:
> >>>>>> https://pastebin.com/FdmGz6i2
> >>>>>
> >>>>>  From the log
> >>>>>
> >>>>> - CPU 00000001 booting -
> >>>>> - Xen must be entered in NS Hyp mode -
> >>>>> - Please update the bootloader -
> >>>>> - Boot failed
> >>>>>
> >>>>> This means that U-boot bring-up secondary CPU in hypervisor mode
> >>>>> (probably it is in secure mode or kernel mode). Which U-boot are you
> >>>>> using?
> >>>> I use the latest u-boot - 2019.04.
> >>>
> >>> lain suggested to use a patched version of U-boot (See his e-mail for
> >>> the 29th of May). So one possibility is some of the patches didn't reach
> >>> upstream.
> >>>
> >>> I would recommend to try the same U-boot version first to see if
> >>> secondary CPUs are brought up in Hyp mode.
> >> I will try to apply 0004 patch to the modern u-boot, I think it will
> >> have the similar effect.
> >> I don't quite understand how to use Kconfig. I can't find some options
> >> with menuconfig, so, I am interested in how programmers find out what
> >> options they need to choose?
> >>>
> >>> Cheers,
> >>>
> >>
> >> --
> >> Regards, Denis Obrezkov
> >>
>
> --
> Regards, Denis Obrezkov
>

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