[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] ARM64:Porting xen to new hardware


What I meant by using '>' for quoting is all my reply should be prefixed with '>'. You write your reply normally.

You can do that in gmail by switching the e-mail from HTML to plain text.

On 26/02/18 07:31, bharat gohil wrote:
On Thu, Feb 22, 2018 at 4:57 PM, Julien Grall <julien.grall@xxxxxxx <mailto:julien.grall@xxxxxxx>> wrote:
    This looks quite wrong to me. By modifying the interrupt parent
    property, you also modify which interrupt controller will be used
    for routing the interrupt. This is probably the reason of the hang
    you mention below.

    What are the interrupts controller you have on your platform?

>It has interrupt controller which change the polarity of SPI IRQ before redirect to GIC-400.
 >In DTB debug, I got following trace,
>(XEN) irq 0 not connected to primary controller. Connected to /intpol-controller@10220a80. >I think Xen skip interrupt controller(if other than GIC) while domain creation.

Xen will not try to map interrupt that are routed to a different interrupt controller. This is because we don't know how to translate the property 'regs' for those interrupts.

 >Do you have suggestion to solve this?
>Do I need to support custom IRQ controller in Xen or hard code the custom controller register in Xen and modified DTB with GIC as primary controller?

If any interrupts used by Xen (e.g UART) are behind that custom IRQ controller, then you would need to add the driver in Xen.

There was an attempt to provide a framework for hooking custom IRQ controller in Xen (see [1]).

You could probably look for doing something similar for your board.


[1] https://lists.xenproject.org/archives/html/xen-devel/2017-04/msg00991.html

Julien Grall

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.