[Xen-devel] Hikey: Enable Xen + Mainline Linux Kernel

[Leo Yan <leo.yan@xxxxxxxxxx>]

Hi all,

Sorry I bring up this question at here if it's duplicate due I googled
and found on the mailing list there have several related discussion for
enabling Xen on Hikey (I use Hikey but not Hikey960); but what I saw it
seems a new issue.

Below is the configuration at my side:

- Linux kernel: mainline kernel with 5.0-rc2;

  make defconfig
  make -j16 Image dtbs

- Xen: latest code base

  git clone git://xenbits.xen.org/xen.git
  cd xen
  make dist-xen XEN_TARGET_ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu-

- Prepare my boot image:

  $ mount -o loop,rw,sync boot-linux.uefi.img boot-fat
  $ cp Image hi6220-hikey.dtb boot-fat/

  # prepare xen.cfg and startup.nsh

  For xen.cfg, it have below content:
  options=dom0_mem=512M dom0_max_vcpus=8 conswitch=x console=dtuart
  dtuart=/smb/uart@f7113000
  kernel=Image console=hvc root=/dev/mmcblk0p9 rootwait rw 3 mem=256M
  dtb=hi6220-hikey.dtb

  For startup.nsh, it have below content:
  FS0:
  Image console=ttyAMA3,115200 root=/dev/mmcblk0p9 rootwait rw efi=noruntime 
earlycon=pl011,0xf7113000

  $ umount boot-fat

- Flash the boot image into 'boot' partition and UEFI will find it by
  default:

  $ fastboot flash boot boot-linux.uefi.img

- After run into UEFI shell, after execute 'xen' command I can see
  below kernel panic; it's related with mmc driver initialization and
  it tries to use xen_swiotlb_alloc_coherent() for DMA memory
  allocation but failed.

  I tried to reduce the memory size in xen.cfg (options=dom0_mem=512M)
  for Xen and Linux kernel (mem=256M) but it doesn't work.

  Also enclosed the complete booting log.

  Very appreciate if you could give some suggestions for this.

Thanks,
Leo Yan

[    1.807591] Modules linked in:
[    1.810717] CPU: 4 PID: 1 Comm: swapper/0 Not tainted 
5.0.0-rc2-00001-g5b47dea3757c #3
[    1.818691] Hardware name: HiKey Development Board (DT)
[    1.823983] pstate: 40000005 (nZcv daif -PAN -UAO)
[    1.828848] pc : xen_swiotlb_alloc_coherent+0x64/0x1e8
[    1.834044] lr : dma_alloc_attrs+0xf4/0x110
[    1.838289] sp : ffff000010073a50
[    1.841671] x29: ffff000010073a50 x28: 0000000000000007 
[    1.847047] x27: ffff000011150068 x26: ffff80001b6ddd60 
[    1.852429] x25: ffff000010caaa70 x24: 0000000000000000 
[    1.857800] x23: 0000000000001000 x22: 0000000000001000 
[    1.863177] x21: 0000000000000000 x20: ffff80001c2edc10 
[    1.868553] x19: ffff0000111fd000 x18: ffffffffffffffff 
[    1.873930] x17: 0000000000000000 x16: 0000000000000000 
[    1.879306] x15: ffff0000111fd6c8 x14: ffff0000900737b7 
[    1.884683] x13: ffff0000100737c5 x12: ffff000011215000 
[    1.890060] x11: 0000000005f5e0ff x10: ffff0000111fd940 
[    1.895436] x9 : 0000000000000000 x8 : ffff80001bb0e700 
[    1.900813] x7 : 0000000000000000 x6 : 0000000000000000 
[    1.906189] x5 : ffff0000105bdbb8 x4 : 0000000000000000 
[    1.911566] x3 : 00000000006000c0 x2 : ffff80001b6ddd60 
[    1.916943] x1 : 0000000000001000 x0 : 0000000000000000 
[    1.922326] Process swapper/0 (pid: 1, stack limit = 0x(____ptrval____))
[    1.929084] Call trace:
[    1.931602]  xen_swiotlb_alloc_coherent+0x64/0x1e8
[    1.936456]  dma_alloc_attrs+0xf4/0x110
[    1.940359]  dmam_alloc_attrs+0x64/0xb8
[    1.944264]  dw_mci_probe+0x5f8/0xb00
[    1.947990]  dw_mci_pltfm_register+0xa0/0xd0
[    1.952327]  dw_mci_k3_probe+0x2c/0x38
[    1.956145]  platform_drv_probe+0x50/0xa0
[    1.960218]  really_probe+0x1f0/0x298
[    1.963947]  driver_probe_device+0x58/0x100
[    1.968196]  __driver_attach+0xd4/0xd8
[    1.972017]  bus_for_each_dev+0x74/0xc8
[    1.975914]  driver_attach+0x20/0x28
[    1.979556]  bus_add_driver+0x1ac/0x218
[    1.983458]  driver_register+0x60/0x110
[    1.987361]  __platform_driver_register+0x40/0x48
[    1.992138]  dw_mci_k3_pltfm_driver_init+0x18/0x20
[    1.996988]  do_one_initcall+0x5c/0x178
[    2.000891]  kernel_init_freeable+0x198/0x240
[    2.005314]  kernel_init+0x10/0x108
[    2.008867]  ret_from_fork+0x10/0x18
[    2.012516] Code: f9414280 aa1503e4 aa1a03e2 aa1703e1 (f9400005) 
[    2.018680] ---[ end trace baf3ac16eabafa1f ]---
[    2.023394] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0000000b
[    2.031068] SMP: stopping secondary CPUs
[    2.035101] Kernel Offset: disabled
[    2.038611] CPU features: 0x002,24002004
[    2.042604] Memory Limit: 256 MB
[    2.045898] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0000000b ]---

Attachment: hikey_xen.log
Description: Text document

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