Re: [Xen-devel] Armv8-A: Not able to enable secondary CPUs in Hikey960 board

2018-08-21 Thread Julien Grall



On 08/20/2018 10:46 AM, Omkar Bolla wrote:

Hi Julien,


Hello,



I tried today with your patch in xen-4.11


Can you please bisect Xen tree?

Cheers,

--
Julien Grall

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

Re: [Xen-devel] Armv8-A: Not able to enable secondary CPUs in Hikey960 board

2018-08-20 Thread Omkar Bolla
Hi Julien,

I tried today with your patch in xen-4.11

Still has secondary cpus problems,

Please find below log after that patch in xen-4.11

Loading driver at 0x000B03B5000 EntryPoint=0x000B044907C
Loading driver at 0x000B03B5000 EntryPoint=0x000B044907C
Using modules provided by bootloader in FDT
Xen 4.11.1-pre (c/s Mon Jul 30 11:30:09 2018 +0200 git:33ced72-dirty) EFI
loader

- UART enabled -
- CPU  booting -
- Current EL 0008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) Checking for initrd in /chosen
(XEN) RAM:  - 1abf
(XEN) RAM: 1ad88000 - 31ff
(XEN) RAM: 32101000 - 3dff
(XEN) RAM: 4000 - 4cfa3fff
(XEN) RAM: 89cc - b03a3fff
(XEN) RAM: b1af - b9af0fff
(XEN) RAM: b9af1000 - b9af8fff
(XEN) RAM: b9b09000 - b9bc
(XEN) RAM: b9c7 - b9c71fff
(XEN) RAM: b9c74000 - b9d5
(XEN) RAM: ba125000 - ba12bfff
(XEN) RAM: ba12c000 - bd9b7fff
(XEN) RAM: bd9b8000 - bd9b9fff
(XEN) RAM: bd9ba000 - bd9c3fff
(XEN) RAM: bd9c4000 - bef5
(XEN) RAM: bef6 - bf0e
(XEN) RAM: bf0f - bf13
(XEN) RAM: bf19 - bf193fff
(XEN) RAM: bf194000 - bfff
(XEN) RAM: c000 - dfff
(XEN) RAM: 0002 - 00021fff
(XEN)
(XEN) MODULE[0]: b03a4000 - b03b5000 Device Tree
(XEN) MODULE[1]: b04be000 - b1975a00 Kernel
 console=tty0 console=hvc0 root=/dev/sdd10 rootwait rw rootfstype=ext4
efi=noruntime video=HDMI-A
-1:1280x720@60
(XEN)
(XEN) Command line: loglvl=all console=dtuart dtuart=/soc/serial@fff32000
dom0_mem=2048M efi=no-rs
(XEN) parameter "efi" unknown!
(XEN) Placing Xen at 0xdfe0-0xe000
(XEN) Update BOOTMOD_XEN from b03b5000-b04bdd81 =>
dfe0-dff08d81
(XEN) Domain heap initialised
(XEN) Booting using Device Tree
(XEN) Platform: Generic System
(XEN) Looking for dtuart at "/soc/serial@fff32000", options ""
 Xen 4.11.1-pre
(XEN) Xen version 4.11.1-pre (omkar.bolla@) (aarch64-linux-gnu-gcc (Linaro
GCC 7.1-2017.05) 7.1.1 20170510) debug=n  Mon Aug 20 15:11:16 IST 2018
(XEN) Latest ChangeSet: Mon Jul 30 11:30:09 2018 +0200 git:33ced72-dirty
(XEN) Processor: 410fd034: "ARM Limited", variant: 0x0, part 0xd03, rev 0x4
(XEN) 64-bit Execution:
(XEN)   Processor Features:  
(XEN) Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
(XEN) Extensions: FloatingPoint AdvancedSIMD
(XEN)   Debug Features: 10305106 
(XEN)   Auxiliary Features:  
(XEN)   Memory Model Features: 1122 
(XEN)   ISA Features:  00011120 
(XEN) 32-bit Execution:
(XEN)   Processor Features: 0131:00011011
(XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
(XEN) Extensions: GenericTimer Security
(XEN)   Debug Features: 03010066
(XEN)   Auxiliary Features: 
(XEN)   Memory Model Features: 10201105 4000 0126 02102211
(XEN)  ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
(XEN) Using SMC Calling Convention v1.1
(XEN) Using PSCI v1.1
(XEN) SMP: Allowing 8 CPUs
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 1920 KHz
(XEN) GICv2 initialization:
(XEN) gic_dist_addr=e82b1000
(XEN) gic_cpu_addr=e82b2000
(XEN) gic_hyp_addr=e82b4000
(XEN) gic_vcpu_addr=e82b6000
(XEN) gic_maintenance_irq=25
(XEN) GICv2: 384 lines, 8 cpus, secure (IID 0200143b).
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Allocated console ring of 64 KiB.
(XEN) Bringing up CPU1
(XEN) Failed to bring up CPU1
(XEN) Failed to bring up CPU 1 (error -9)
(XEN) Bringing up CPU2
(XEN) Failed to bring up CPU2
(XEN) Failed to bring up CPU 2 (error -9)
(XEN) Bringing up CPU3
(XEN) Failed to bring up CPU3
(XEN) Failed to bring up CPU 3 (error -9)
(XEN) Bringing up CPU4
(XEN) Failed to bring up CPU4
(XEN) Failed to bring up CPU 4 (error -9)
(XEN) Bringing up CPU5
(XEN) Failed to bring up CPU5
(XEN) Failed to bring up CPU 5 (error -9)
(XEN) Bringing up CPU6
(XEN) Failed to bring up CPU6
(XEN) Failed to bring up CPU 6 (error -9)
(XEN) Bringing up CPU7
(XEN) Failed to bring up CPU7
(XEN) Failed to bring up CPU 7 (error -9)
(XEN) Brought up 1 CPUs
(XEN) P2M: 40-bit IPA with 40-bit PA and 8-bit VMID
(XEN) P2M: 3 levels with order-1 root, VTCR 0x80023558
(XEN) I/O virtualisation disabled
(XEN) build-id: 361a7d1197ce6c845658fa3210780d1751b7103a
(XEN) alternatives: Patching with alt table 400acff8 ->
400ad568
(XEN) *** LOADING DOMAIN 0 

Re: [Xen-devel] Armv8-A: Not able to enable secondary CPUs in Hikey960 board

2018-08-15 Thread Julien Grall

On 08/15/2018 10:15 AM, Omkar Bolla wrote:

HI Julien,


Hello,

As you suggested, I enabled early printk for hikey960 in xen-4.8 stable 
branch and xen-4.11 stable branch.


Looking at the logs, Xen is placed differently in the memory:
- Xen 4.8:  0x1aa0
- Xen 4.11: 0x00021fe0

With Xen 4.11, the binary will be placed above 4GB. There was some 
change in the way to place Xen in the memory in 2016 allowing to place 
Xen at the end of the usable RAM.


I suspect the firmware does not support 64-bit address entry point for 
secondary CPU. This would explain the ADDRESS_INVALID from PSCI CPU UP 
call. Can you give a try to this patch:


diff --git a/xen/arch/arm/setup.c b/xen/arch/arm/setup.c
index 7d40a8466b..13318da6b1 100644
--- a/xen/arch/arm/setup.c
+++ b/xen/arch/arm/setup.c
@@ -408,13 +408,11 @@ static paddr_t __init get_xen_paddr(void)
 if ( !e )
 continue;

-#ifdef CONFIG_ARM_32
 /* Xen must be under 4GB */
 if ( e > 0x1ULL )
 e = 0x1ULL;
 if ( e < bank->start )
 continue;
-#endif

 s = e - min_size;


Cheers,

--
Julien Grall

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

Re: [Xen-devel] Armv8-A: Not able to enable secondary CPUs in Hikey960 board

2018-08-15 Thread Omkar Bolla
HI Julien,

As you suggested, I enabled early printk for hikey960 in xen-4.8 stable
branch and  xen-4.11 stable branch.



Please find below xen-4.8 log after early printk:
--
Using modules provided by bootloader in FDT
Xen 4.8.5-pre (c/s Mon Jul 30 12:10:58 2018 +0200 git:aa45015-dirty) EFI
loader
- UART enabled -
- CPU  booting -
- Current EL 0008 -
- Xen starting at EL2 -
- Zero BSS -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) Checking for initrd in /chosen
(XEN) RAM:  - 1abf
(XEN) RAM: 1ad88000 - 31ff
(XEN) RAM: 32101000 - 3dff
(XEN) RAM: 4000 - 4ae9
(XEN) RAM: 89cc - b83bdfff
(XEN) RAM: b9b09000 - b9bc
(XEN) RAM: b9c7 - b9c72fff
(XEN) RAM: b9c74000 - b9d5
(XEN) RAM: ba125000 - ba12bfff
(XEN) RAM: ba12c000 - bdd1bfff
(XEN) RAM: bdd1c000 - bddccfff
(XEN) RAM: bddcd000 - bde82fff
(XEN) RAM: bde83000 - bef5
(XEN) RAM: bef6 - bf0e
(XEN) RAM: bf0f - bf13
(XEN) RAM: bf19 - bf193fff
(XEN) RAM: bf194000 - bfff
(XEN) RAM: c000 - dfff
(XEN) RAM: 0002 - 00021fff
(XEN)
(XEN) MODULE[0]: b83be000 - b83cf000 Device Tree
(XEN) MODULE[1]: b84e - b9996200 Kernel
 console=tty0 console=hvc0 root=/dev/sdd10 rw efi=noruntime
(XEN)
(XEN) Command line: loglvl=all console=dtuart dtuart=/soc/serial@fff32000
efi=no-rs
(XEN) Placing Xen at 0x1aa0-0x1ac0
(XEN) Update BOOTMOD_XEN from b83cf000-b84cfd81 =>
1aa0-1ab00d81
(XEN) Domain heap initialised
(XEN) Platform: Generic System
(XEN) Looking for dtuart at "/soc/serial@fff32000", options ""
 Xen 4.8.5-pre
(XEN) Xen version 4.8.5-pre (omkar.bolla@) (aarch64-linux-gnu-gcc (Linaro
GCC 7.1-2017.05) 7.1.1 20170510) debug=n  Wed Aug 15 13:20:23 IST 2018
(XEN) Latest ChangeSet: Mon Jul 30 12:10:58 2018 +0200 git:aa45015-dirty
(XEN) Processor: 410fd034: "ARM Limited", variant: 0x0, part 0xd03, rev 0x4
(XEN) 64-bit Execution:
(XEN)   Processor Features:  
(XEN) Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
(XEN) Extensions: FloatingPoint AdvancedSIMD
(XEN)   Debug Features: 10305106 
(XEN)   Auxiliary Features:  
(XEN)   Memory Model Features: 1122 
(XEN)   ISA Features:  00011120 
(XEN) 32-bit Execution:
(XEN)   Processor Features: 0131:00011011
(XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
(XEN) Extensions: GenericTimer Security
(XEN)   Debug Features: 03010066
(XEN)   Auxiliary Features: 
(XEN)   Memory Model Features: 10201105 4000 0126 02102211
(XEN)  ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
(XEN) Using PSCI-1.1 for SMP bringup
(XEN) SMP: Allowing 8 CPUs
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 1920 KHz
(XEN) GICv2 initialization:
(XEN) gic_dist_addr=e82b1000
(XEN) gic_cpu_addr=e82b2000
(XEN) gic_hyp_addr=e82b4000
(XEN) gic_vcpu_addr=e82b6000
(XEN) gic_maintenance_irq=25
(XEN) GICv2: 384 lines, 8 cpus, secure (IID 0200143b).
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Allocated console ring of 64 KiB.
(XEN) Bringing up CPU1
- CPU 0001 booting -
- Current EL 0008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 1 booted.
(XEN) Bringing up CPU2
- CPU 0002 booting -
- Current EL 0008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 2 booted.
(XEN) Bringing up CPU3
- CPU 0003 booting -
- Current EL 0008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 3 booted.
(XEN) Bringing up CPU4
- CPU 0100 booting -
- Current EL 0008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 4 booted.
(XEN) Bringing up CPU5
- CPU 0101 booting -
- Current EL 0008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 5 booted.
(XEN) Bringing up CPU6
- CPU 0102 booting -
- Current EL 0008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 6 booted.
(XEN) Bringing up CPU7
- CPU 0103 booting -
- Current EL 0008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 7 booted.
(XEN) Brought up 8 CPUs
(XEN) P2M: 40-bit IPA with 

Re: [Xen-devel] Armv8-A: Not able to enable secondary CPUs in Hikey960 board

2018-08-15 Thread Omkar Bolla
Hi Konrad,

Thank you Konrad.
I tried other versions also, and Xen 4.8.5 stable branch is working
properly.

And i will investigate which patch causing this issue between xen-4.8 and
xen-4.9 branch.

Thank you,
Omkar B

-- 






This
message contains confidential information and is intended only 
for the
individual(s) named. If you are not the intended
recipient, you are 
notified that disclosing, copying, distributing or taking any
action in 
reliance on the contents of this mail and attached file/s is strictly

prohibited. Please notify the
sender immediately and delete this e-mail 
from your system. E-mail transmission
cannot be guaranteed to be secured or 
error-free as information could be
intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain
viruses. The sender therefore does 
not accept liability for any errors or
omissions in the contents of this 
message, which arise as a result of e-mail
transmission.
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [Xen-devel] Armv8-A: Not able to enable secondary CPUs in Hikey960 board

2018-08-13 Thread Julien Grall

Hello,

On 13/08/18 14:01, Konrad Rzeszutek Wilk wrote:

On Mon, Aug 13, 2018 at 11:16:14AM +0530, Omkar Bolla wrote:

Please check below log:

  Using modules provided by bootloader in FDT
Xen 4.11.1-pre (c/s Mon Jul 30 11:30:09 2018 +0200 git:33ced72) EFI

loader

  Xen 4.11.1-pre
(XEN) Xen version 4.11.1-pre (omkar.bolla@) (aarch64-linux-gnu-gcc

(Linaro

GCC 7.1-2017.05) 7.1.1 20170510) debug=n  Sat Aug 11 20:35:10 IST 201
8
(XEN) Latest ChangeSet: Mon Jul 30 11:30:09 2018 +0200 git:33ced72
(XEN) Processor: 410fd034: "ARM Limited", variant: 0x0, part 0xd03, rev

0x4

(XEN) 64-bit Execution:
(XEN)   Processor Features:  
(XEN) Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
(XEN) Extensions: FloatingPoint AdvancedSIMD
(XEN)   Debug Features: 10305106 
(XEN)   Auxiliary Features:  
(XEN)   Memory Model Features: 1122 
(XEN)   ISA Features:  00011120 
(XEN) 32-bit Execution:
(XEN)   Processor Features: 0131:00011011
(XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
(XEN) Extensions: GenericTimer Security
(XEN)   Debug Features: 03010066
(XEN)   Auxiliary Features: 
(XEN)   Memory Model Features: 10201105 4000 0126 02102211
(XEN)  ISA Features: 02101110 13112111 21232042 01112131 00011142

00011121

(XEN) Using SMC Calling Convention v1.1
(XEN) Using PSCI v1.1
(XEN) SMP: Allowing 8 CPUs
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 1920 KHz
(XEN) GICv2 initialization:
(XEN) gic_dist_addr=e82b1000
(XEN) gic_cpu_addr=e82b2000
(XEN) gic_hyp_addr=e82b4000
(XEN) gic_vcpu_addr=e82b6000
(XEN) gic_maintenance_irq=25
(XEN) GICv2: 384 lines, 8 cpus, secure (IID 0200143b).
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Allocated console ring of 64 KiB.
(XEN) Bringing up CPU1
(XEN) Failed to bring up CPU1
(XEN) Failed to bring up CPU 1 (error -9)


I think the -9 is coming from PSCI which means INVALID_ADDRESS. This 
means Xen gave an invalid entry point to PSCI CPU_UP.


It would be interesting to know where Xen is loaded in memory with Xen 
4.8 and Xen 4.11. This will be printed when early printk is enabled as 
the console is not yet setup.


To get early printk, you could use CONFIG_EARLY_PRINTK=hikey960 on the 
make command line. Note this requires to have debug enabled.


Once you have early printk setup you should have a message similar to 
"Update BOOTMOD_XEN from ... to ...".


Also, as Konrad suggested it, I would recommend to bisect Xen and see if 
you can pin point a commit.


Cheers,

--
Julien Grall

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

Re: [Xen-devel] Armv8-A: Not able to enable secondary CPUs in Hikey960 board

2018-08-13 Thread Konrad Rzeszutek Wilk
On Mon, Aug 13, 2018 at 11:16:14AM +0530, Omkar Bolla wrote:
> Hi,
> 
> Thankyou very much Konrad,
> As you suggested, I just have started testing previous versions of Xen, and
> it is working with xen-4.7 stable branch.

Does Xen 4.8 or Xen 4.9 or Xen 4.10 work? Trying to get a bisection point 
working.
(My box is right now packed in a box - moving so can't help rightn ow).
> All secondary CPUs got enabled and started.
> 
> If you any idea, please tell me Why latest xen is not working?

Adding xen-devel back.
> 
> Thank you,
> Omkar B
> 
> On Sat, Aug 11, 2018 at 10:36 PM, Konrad Rzeszutek Wilk <
> konrad.w...@oracle.com> wrote:
> 
> > On Sat, Aug 11, 2018 at 08:44:42PM +0530, Omkar Bolla wrote:
> > > Hi,
> > >
> > > I am using Hikey960 board and i started trying to port xen on hykey960.
> > >
> > > I followed all procedure has given in
> > > https://wiki.xenproject.org/wiki/HiKey960 link.
> > > And using *Xen version 4.11.1-pre *and linux as mentioned in above link.
> > >
> > > But, After flashing, I ended up with secondary CPUs errors and linux Dom0
> > > errors.
> > > Please give some suggestions to start xen with all CPUs.
> >
> > Oh that is weird. What happens if you use an older Xen release?
> >
> > >
> > > Please check below log:
> > > 
> > >  Using modules provided by bootloader in FDT
> > > Xen 4.11.1-pre (c/s Mon Jul 30 11:30:09 2018 +0200 git:33ced72) EFI
> > loader
> > >  Xen 4.11.1-pre
> > > (XEN) Xen version 4.11.1-pre (omkar.bolla@) (aarch64-linux-gnu-gcc
> > (Linaro
> > > GCC 7.1-2017.05) 7.1.1 20170510) debug=n  Sat Aug 11 20:35:10 IST 201
> > > 8
> > > (XEN) Latest ChangeSet: Mon Jul 30 11:30:09 2018 +0200 git:33ced72
> > > (XEN) Processor: 410fd034: "ARM Limited", variant: 0x0, part 0xd03, rev
> > 0x4
> > > (XEN) 64-bit Execution:
> > > (XEN)   Processor Features:  
> > > (XEN) Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
> > > (XEN) Extensions: FloatingPoint AdvancedSIMD
> > > (XEN)   Debug Features: 10305106 
> > > (XEN)   Auxiliary Features:  
> > > (XEN)   Memory Model Features: 1122 
> > > (XEN)   ISA Features:  00011120 
> > > (XEN) 32-bit Execution:
> > > (XEN)   Processor Features: 0131:00011011
> > > (XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
> > > (XEN) Extensions: GenericTimer Security
> > > (XEN)   Debug Features: 03010066
> > > (XEN)   Auxiliary Features: 
> > > (XEN)   Memory Model Features: 10201105 4000 0126 02102211
> > > (XEN)  ISA Features: 02101110 13112111 21232042 01112131 00011142
> > 00011121
> > > (XEN) Using SMC Calling Convention v1.1
> > > (XEN) Using PSCI v1.1
> > > (XEN) SMP: Allowing 8 CPUs
> > > (XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 1920 KHz
> > > (XEN) GICv2 initialization:
> > > (XEN) gic_dist_addr=e82b1000
> > > (XEN) gic_cpu_addr=e82b2000
> > > (XEN) gic_hyp_addr=e82b4000
> > > (XEN) gic_vcpu_addr=e82b6000
> > > (XEN) gic_maintenance_irq=25
> > > (XEN) GICv2: 384 lines, 8 cpus, secure (IID 0200143b).
> > > (XEN) Using scheduler: SMP Credit Scheduler (credit)
> > > (XEN) Allocated console ring of 64 KiB.
> > > (XEN) Bringing up CPU1
> > > (XEN) Failed to bring up CPU1
> > > (XEN) Failed to bring up CPU 1 (error -9)
> > ..
> >
> 
> -- 
> 
> 
> 
> 
> 
> 
> This
> message contains confidential information and is intended only 
> for the
> individual(s) named. If you are not the intended
> recipient, you are 
> notified that disclosing, copying, distributing or taking any
> action in 
> reliance on the contents of this mail and attached file/s is strictly
> 
> prohibited. Please notify the
> sender immediately and delete this e-mail 
> from your system. E-mail transmission
> cannot be guaranteed to be secured or 
> error-free as information could be
> intercepted, corrupted, lost, destroyed, 
> arrive late or incomplete, or contain
> viruses. The sender therefore does 
> not accept liability for any errors or
> omissions in the contents of this 
> message, which arise as a result of e-mail
> transmission.

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

Re: [Xen-devel] Armv8-A: Not able to enable secondary CPUs in Hikey960 board

2018-08-11 Thread Konrad Rzeszutek Wilk
On Sat, Aug 11, 2018 at 08:44:42PM +0530, Omkar Bolla wrote:
> Hi,
> 
> I am using Hikey960 board and i started trying to port xen on hykey960.
> 
> I followed all procedure has given in
> https://wiki.xenproject.org/wiki/HiKey960 link.
> And using *Xen version 4.11.1-pre *and linux as mentioned in above link.
> 
> But, After flashing, I ended up with secondary CPUs errors and linux Dom0
> errors.
> Please give some suggestions to start xen with all CPUs.

Oh that is weird. What happens if you use an older Xen release?

> 
> Please check below log:
> 
>  Using modules provided by bootloader in FDT
> Xen 4.11.1-pre (c/s Mon Jul 30 11:30:09 2018 +0200 git:33ced72) EFI loader
>  Xen 4.11.1-pre
> (XEN) Xen version 4.11.1-pre (omkar.bolla@) (aarch64-linux-gnu-gcc (Linaro
> GCC 7.1-2017.05) 7.1.1 20170510) debug=n  Sat Aug 11 20:35:10 IST 201
> 8
> (XEN) Latest ChangeSet: Mon Jul 30 11:30:09 2018 +0200 git:33ced72
> (XEN) Processor: 410fd034: "ARM Limited", variant: 0x0, part 0xd03, rev 0x4
> (XEN) 64-bit Execution:
> (XEN)   Processor Features:  
> (XEN) Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
> (XEN) Extensions: FloatingPoint AdvancedSIMD
> (XEN)   Debug Features: 10305106 
> (XEN)   Auxiliary Features:  
> (XEN)   Memory Model Features: 1122 
> (XEN)   ISA Features:  00011120 
> (XEN) 32-bit Execution:
> (XEN)   Processor Features: 0131:00011011
> (XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
> (XEN) Extensions: GenericTimer Security
> (XEN)   Debug Features: 03010066
> (XEN)   Auxiliary Features: 
> (XEN)   Memory Model Features: 10201105 4000 0126 02102211
> (XEN)  ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
> (XEN) Using SMC Calling Convention v1.1
> (XEN) Using PSCI v1.1
> (XEN) SMP: Allowing 8 CPUs
> (XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 1920 KHz
> (XEN) GICv2 initialization:
> (XEN) gic_dist_addr=e82b1000
> (XEN) gic_cpu_addr=e82b2000
> (XEN) gic_hyp_addr=e82b4000
> (XEN) gic_vcpu_addr=e82b6000
> (XEN) gic_maintenance_irq=25
> (XEN) GICv2: 384 lines, 8 cpus, secure (IID 0200143b).
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Allocated console ring of 64 KiB.
> (XEN) Bringing up CPU1
> (XEN) Failed to bring up CPU1
> (XEN) Failed to bring up CPU 1 (error -9)
..

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

[Xen-devel] Armv8-A: Not able to enable secondary CPUs in Hikey960 board

2018-08-11 Thread Omkar Bolla
Hi,

I am using Hikey960 board and i started trying to port xen on hykey960.

I followed all procedure has given in
https://wiki.xenproject.org/wiki/HiKey960 link.
And using *Xen version 4.11.1-pre *and linux as mentioned in above link.

But, After flashing, I ended up with secondary CPUs errors and linux Dom0
errors.
Please give some suggestions to start xen with all CPUs.

Please check below log:

 Using modules provided by bootloader in FDT
Xen 4.11.1-pre (c/s Mon Jul 30 11:30:09 2018 +0200 git:33ced72) EFI loader
 Xen 4.11.1-pre
(XEN) Xen version 4.11.1-pre (omkar.bolla@) (aarch64-linux-gnu-gcc (Linaro
GCC 7.1-2017.05) 7.1.1 20170510) debug=n  Sat Aug 11 20:35:10 IST 201
8
(XEN) Latest ChangeSet: Mon Jul 30 11:30:09 2018 +0200 git:33ced72
(XEN) Processor: 410fd034: "ARM Limited", variant: 0x0, part 0xd03, rev 0x4
(XEN) 64-bit Execution:
(XEN)   Processor Features:  
(XEN) Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
(XEN) Extensions: FloatingPoint AdvancedSIMD
(XEN)   Debug Features: 10305106 
(XEN)   Auxiliary Features:  
(XEN)   Memory Model Features: 1122 
(XEN)   ISA Features:  00011120 
(XEN) 32-bit Execution:
(XEN)   Processor Features: 0131:00011011
(XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
(XEN) Extensions: GenericTimer Security
(XEN)   Debug Features: 03010066
(XEN)   Auxiliary Features: 
(XEN)   Memory Model Features: 10201105 4000 0126 02102211
(XEN)  ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
(XEN) Using SMC Calling Convention v1.1
(XEN) Using PSCI v1.1
(XEN) SMP: Allowing 8 CPUs
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 1920 KHz
(XEN) GICv2 initialization:
(XEN) gic_dist_addr=e82b1000
(XEN) gic_cpu_addr=e82b2000
(XEN) gic_hyp_addr=e82b4000
(XEN) gic_vcpu_addr=e82b6000
(XEN) gic_maintenance_irq=25
(XEN) GICv2: 384 lines, 8 cpus, secure (IID 0200143b).
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Allocated console ring of 64 KiB.
(XEN) Bringing up CPU1
(XEN) Failed to bring up CPU1
(XEN) Failed to bring up CPU 1 (error -9)
(XEN) Bringing up CPU2
(XEN) Failed to bring up CPU2
(XEN) Failed to bring up CPU 2 (error -9)
(XEN) Bringing up CPU3
(XEN) Failed to bring up CPU3
(XEN) Failed to bring up CPU 3 (error -9)
(XEN) Bringing up CPU4
(XEN) Failed to bring up CPU4
(XEN) Failed to bring up CPU 4 (error -9)
(XEN) Bringing up CPU5
(XEN) Failed to bring up CPU5
(XEN) Failed to bring up CPU 5 (error -9)
(XEN) Bringing up CPU6
(XEN) Failed to bring up CPU6
(XEN) Failed to bring up CPU 6 (error -9)
(XEN) Bringing up CPU7
(XEN) Failed to bring up CPU7
(XEN) Failed to bring up CPU 7 (error -9)
(XEN) Brought up 1 CPUs
(XEN) P2M: 40-bit IPA with 40-bit PA and 8-bit VMID
(XEN) P2M: 3 levels with order-1 root, VTCR 0x80023558
(XEN) I/O virtualisation disabled
(XEN) build-id: fa5f17a58e5d75750920185c7944c71cbea9de1d
(XEN) alternatives: Patching with alt table 400acfc8 ->
400ad544
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading kernel from boot module @ b8887000
(XEN) Allocating 1:1 mappings totalling 512MB for dom0:
(XEN) BANK[0] 0x00c000-0x00e000 (512MB)
(XEN) Grant table range: 0x021fe0-0x021fe4
(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading zImage from b8887000 to
c008-c1187200
(XEN) Loading dom0 DTB to 0xc800-0xc800a4db
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Scrubbing Free RAM on 1 nodes using 1 CPUs
(XEN)
done.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) ***
(XEN) PLEASE SPECIFY dom0_mem PARAMETER - USING 512M FOR NOW
(XEN) ***
(XEN) 3... 2... 1...
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input
to Xen)
(XEN) Freed 292kB init memory.
(XEN) d0v0: vGICD: unhandled word write 0x to ICACTIVER4
(XEN) d0v0: vGICD: unhandled word write 0x to ICACTIVER8
(XEN) d0v0: vGICD: unhandled word write 0x to ICACTIVER12
(XEN) d0v0: vGICD: unhandled word write 0x to ICACTIVER16
(XEN) d0v0: vGICD: unhandled word write 0x to ICACTIVER20
(XEN) d0v0: vGICD: unhandled word write 0x to ICACTIVER24
(XEN) d0v0: vGICD: unhandled word write 0x to ICACTIVER28
(XEN) d0v0: vGICD: unhandled word write 0x to ICACTIVER32
(XEN) d0v0: vGICD: unhandled word write 0x to ICACTIVER36
(XEN) d0v0: vGICD: unhandled word write 0x to ICACTIVER40
[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version