Re: [Xen-devel] ARMv8: New board bring up hangs in kernel start?

[Julien Grall <julien.grall@xxxxxxx>]

On 04/04/2016 16:44, Dirk Behme wrote:
> Hi Julien,
Hello Dirk,

> On 01.04.2016 18:34, Julien Grall wrote:
> > On 31/03/16 18:41, Dirk Behme wrote:
> > > > Also have you tried a newer version of Xen?
> > >
> > > I've switched to the recent master
> > >
> > > a6f2cdb63 x86/hvm/viridian: keep APIC assist page mapped
> > >
> > > now. No difference.
> > >
> > > I'll have a deeper look into the interrupt configuration.
> > >
> > > Is there anywhere some basic description which interrupts are supposed
> > > to be handled by XEN and which by the Linux kernel? I.e. how the ARM
> > > GIC
> > > should be configured regarding the distributor/CPU/virtual parts?
> > All the interrupts are taken by Xen. The function do_IRQ in Xen will
> > dispatch the IRQ either to a guest or call a Xen specific handler.
> >
> > Xen handles only a limited number of interrupt:
> >      * timers
> >      * UART
> >      * SMMU
> >
> > The rest is either routed to guests or blacklisted by Xen.
>
> Ok, thanks, that helps :) Once I have it working, maybe I post a patch
> to add this info to the documentation.
That would be good. Thank you!

> Just an other question:
>
> On ARMv8 64-bit Xen is supposed to be started at EL2 *nonsecure*, correct?
That's right.

> It looks to me that the GICv2 on my board is already partly configured
> by the firmware at secure EL3. That does mean, whatever
> gicv2_dist_init() and gicv2_cpu_init() are supposed to do, they can't do
> it (completely) because they don't have access to the secure part of the
> GIC (?)
Which is normal, the secure part of the GIC should have already been 
initialized by the firmware running at secure EL3.
Do you know if Linux was able to initialize KVM on baremetal?

Regards,

--
Julien Grall

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