Hi,
Philippe Gerum schrieb:
>
> I agree with the conclusion, not with the fix.
Thanks for reviewing the patch and sorry for the late answer.
> - the kernel side should rather test RTHAL_CPU_FREQ for consistency in
> the generic hal init code, and bail out with an error if 0 is detected,
> since
In some conditions, while testing Xenomai in VirtualBox, I had the error that
xnarch_init_timeconv() is called from init_32.h with a frequency of 0. That
leads to a division by zero, followed by a system oops.
Of course that is a bug in the virtualisation and Linux reports a CPU frequency
of 0 in
