Re: [Xen-devel] Dom0 kernel panic when porting xen to new arm soc

[Julien Grall <julien.grall.oss@xxxxxxxxx>]

Hi,

On 19/06/2015 14:22, Peng Fan wrote:
> diff --git a/kernel/timer.c b/kernel/timer.c
> index 38f0d40..4a025cc 100644
> --- a/kernel/timer.c
> +++ b/kernel/timer.c
> @@ -1175,6 +1175,10 @@ static inline void __run_timers(struct tvec_base
> *base)
>
>                          base->running_timer = timer;
>                          detach_expired_timer(timer, base);
> +                       if (!fn) {
> +                               printk("fn is null why????\n"); ---->
> This log only shows once. Not sure why fn is null and only once.
> +                               continue;
> +                       }
>
>                          if (irqsafe) {
>                                  spin_unlock(&base->lock);
By any chance, does your board has a another timer (i.e other than the 
generic timer)?
I would also track down to see who is adding this timer.

> But after apply the above kernel patch, Dom0 Linux can handle shell input.
> Just have another question, How can Dom0 handle DMA for arm.
When Xen is allocating the RAM bank for DOM0 we use a direct mapping 
(i.e the Physical Address = Intermediate Address for the RAM). So DOM0 
can perform DMA as on baremetal.
Regards,

--
Julien Grall

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