From: Julien Grall <julien.grall.oss@gmail.com>
To: Peng Fan <van.freenix@gmail.com>, Ian Campbell <ian.campbell@citrix.com>
Cc: julien.grall@citrix.com, xen-devel@lists.xen.org
Subject: Re: Dom0 kernel panic when porting xen to new arm soc
Date: Sat, 20 Jun 2015 11:19:12 +0100 [thread overview]
Message-ID: <55853E20.6030700@gmail.com> (raw)
In-Reply-To: <55841799.6000406@gmail.com>
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
next prev parent reply other threads:[~2015-06-20 10:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 14:09 Dom0 kernel panic when porting xen to new arm soc Peng Fan
2015-06-18 14:24 ` Julien Grall
2015-06-18 14:54 ` Ian Campbell
2015-06-19 13:22 ` Peng Fan
2015-06-20 10:19 ` Julien Grall [this message]
2015-06-20 14:08 ` Peng Fan
2015-06-20 14:47 ` Peng Fan
2015-06-22 10:20 ` Julien Grall
2015-06-22 11:17 ` Peng Fan
2015-06-22 14:02 ` Julien Grall
2015-06-23 13:03 ` Peng Fan
2015-06-23 13:36 ` Julien Grall
2015-06-23 13:56 ` Peng Fan
2015-06-25 14:09 ` Peng Fan
2015-06-26 16:27 ` Julien Grall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55853E20.6030700@gmail.com \
--to=julien.grall.oss@gmail.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@citrix.com \
--cc=van.freenix@gmail.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.