From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: Dom0 kernel panic when porting xen to new arm soc Date: Sat, 20 Jun 2015 11:19:12 +0100 Message-ID: <55853E20.6030700@gmail.com> References: <5582D109.2000409@gmail.com> <1434639280.28264.42.camel@citrix.com> <55841799.6000406@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <55841799.6000406@gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Peng Fan , Ian Campbell Cc: julien.grall@citrix.com, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org 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