Hi all,
I'm reading Mini-OS's codes and to estimate the amount of work porting it to
ARM (Ian's GSoC idea this year).
While Xen is booting Mini-OS on x86 platform, it passes the start_info_t to
the guest through ESI register. And Mini-OS would use this structure as the
argument of start_kernel. However, I didn't see codes handle the
start_info_t on ARM side. Instead, I see a more standard protocal when
booting ARM's dom0, which follows linux kernel bootstrap rules:
r0 = 0, r1 = machine nr, r2 = atags or dtb pointer
Does it mean that Xen for ARM does not use the start_info_t to pass
information when booting PV guest? Or did I miss something important?
Any comments?
Thanks,
- Chen Baozi
_______________________________________________
Xen-arm mailing list
Xen-arm@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm
I'm reading Mini-OS's codes and to estimate the amount of work porting it to
ARM (Ian's GSoC idea this year).
While Xen is booting Mini-OS on x86 platform, it passes the start_info_t to
the guest through ESI register. And Mini-OS would use this structure as the
argument of start_kernel. However, I didn't see codes handle the
start_info_t on ARM side. Instead, I see a more standard protocal when
booting ARM's dom0, which follows linux kernel bootstrap rules:
r0 = 0, r1 = machine nr, r2 = atags or dtb pointer
Does it mean that Xen for ARM does not use the start_info_t to pass
information when booting PV guest? Or did I miss something important?
Any comments?
Thanks,
- Chen Baozi
_______________________________________________
Xen-arm mailing list
Xen-arm@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-arm