Re: [Xen-devel] [XenARM] XEN tools for ARM with Virtualization Extensions

[Julien Grall <julien.grall@xxxxxxxxxx>]

On 06/27/2013 08:01 PM, Eric Trudeau wrote:

>> -----Original Message-----
>> From: Ian Campbell [mailto:Ian.Campbell@xxxxxxxxxx]
>> Sent: Thursday, June 27, 2013 12:34 PM
>> To: Eric Trudeau
>> Cc: xen-devel
>> Subject: Re: [XenARM] XEN tools for ARM with Virtualization Extensions
>>
>> On Thu, 2013-06-27 at 16:21 +0000, Eric Trudeau wrote:
>>>> -----Original Message-----
>>>> From: Ian Campbell [mailto:Ian.Campbell@xxxxxxxxxx]
>>>> Sent: Wednesday, June 26, 2013 12:45 PM
>>>> To: Eric Trudeau
>>>> Cc: xen-devel
>>>> Subject: Re: [XenARM] XEN tools for ARM with Virtualization Extensions
>>>>
>>
> 
>>> I rebased to the XSA-55 commit and now I can create the guest.  I am
>>> able to debug a kernel init panic.
>>
> 
> My panic seems related to memory regions in device tree.  I am appended
> my DTB to the kernel zImage.
> How does the memory assigned by XEN for the guest domain get inserted
> into the device tree?
> Does Hypervisor or the toolchain manipulate the appended DTB and modify
> the hypervisor node's reg and irq properties? What about the memory node?


For the moment, the toolstack isn't not able to parse/modify the guest
DTB. Memory and IRQ properties are hardcoded in the hypervisor and the
toolstack. The different values need to match the following constraints:
  - The memory region start from 0x80000000. The size needs to be the
same in the configuration file and the DTS, otherwise the domain will
crash. I believe the default size is 128MB.
  - IRQ properties are:
      * event channel: 31, except if you have modified the IRQ number in
Xen for dom0;
      * timer: same IRQs number as the dom0 DTS;
  - GIC range: same range as the dom0 DTS.

Cheers,

-- 
Julien

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel