Re: [Xen-devel] [PATCH] xen/arm: Propagate clock-frequency to DOMU if present in the DT timer node

["Chris (Christopher) Brand" <chris.brand@xxxxxxxxxxxx>]

Hi Julien,

>> A simple "export CONFIG_DTB_FILE=...".
>
>Are you using an absolute path?

Absolute path, yes.

>> So your patch isn't designed to help in this case (CNTFRQ set on core 0 
>> only, no clock-frequency property in timer node of DT).
>
>Well, my patch is designed to propagate the "clock-frequency" property in DOMU 
>via the toolstack. The propagation for Dom0 is already present in Xen since 
>last year [1].

Understood. In my case, the DomU kernel dies during boot if it happens to be 
scheduled on a core other than core 0 (it comes up fine if it happens to run on 
core 0). Core 0 has CNTFRQ set, but the other cores don't. We will fix this for 
real by writing to CNTFRQ on the other cores in the PSCI code in the SMC.

>Does your bootloader create Xen nodes (multiboot, chosen, ...) or the device 
>tree provided by the bootloader contain such nodes? If not, then you are using 
>an appended DT (via CONFIG_DTB_FILE) to Xen.

It doesn't do that, no. In that case the mystery is why Xen apparently doesn't 
see the clock-frequency property. I'll keep investigating.

>If you didn't yet do it, I would try to clean Xen repository and try to 
>rebuild Xen to see if the build system was using a stall DTB by mistake.

I have, but I'll do it again.

Chris


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