All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Baozi <baozich@gmail.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	List Xen Developer <xen-devel@lists.xen.org>
Subject: Re: Problems when using latest git tree to boot xen on OMAP5
Date: Tue, 15 Oct 2013 16:41:45 +0800	[thread overview]
Message-ID: <AF3F5E2C-6C4F-4C80-A3E6-D9C806C40183@gmail.com> (raw)
In-Reply-To: <52553AE2.6070806@linaro.org>


On Oct 9, 2013, at 7:15 PM, Julien Grall <julien.grall@linaro.org> wrote:

> On 10/09/2013 09:11 AM, Ian Campbell wrote:
>> Rather than whitelisting and mapping disabled devices through perhaps we
>> should implement them as read 0xf (or 0x0) and write ignore?
> 
> We can't assume that these values (0x0 or 0xf) won't affect dom0 behaviour.
> 
> What about a new quirk to map all disabled device in dom0
> (PLATFORM_QUIRK_DOM0_MAP_DISABLED_DEVICE)?

I've implemented the PLATFORM_QUIRK_DOM0_MAP_DISABLED_DEVICE quirk in my
own working tree. It seems to work very well on fixing this issue. +1 
to this idea.

Then I finished new smp initialization callbacks for omap5.

However, the new xen version still has some issues to boot dom0 on OMAP5.

Right now, Dumping cpu0 guest state shows that PC stays at __loop_delay,
while cpu1 stays at cpu_relax() line of ipi_cpu_stop(), using addr2line
to translate PC to the C code location.

Any ideas?

Cheers,

Baozi

  parent reply	other threads:[~2013-10-15  8:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04 14:11 Problems when using latest git tree to boot xen on OMAP5 Chen Baozi
2013-10-06 14:21 ` Chen Baozi
2013-10-07  8:39   ` Ian Campbell
2013-10-07  9:58     ` Chen Baozi
2013-10-07 10:01       ` Ian Campbell
2013-10-07 10:59       ` Julien Grall
2013-10-07 15:28         ` Chen Baozi
2013-10-07 15:44           ` Julien Grall
2013-10-08 13:54             ` Chen Baozi
2013-10-09  7:46         ` Chen Baozi
2013-10-09  8:11           ` Ian Campbell
2013-10-09  9:09             ` Chen Baozi
2013-10-09 11:15             ` Julien Grall
2013-10-09 11:19               ` Ian Campbell
2013-10-09 11:29                 ` Stefano Stabellini
2013-10-09 12:01                   ` Ian Campbell
2013-10-09 12:11                     ` Stefano Stabellini
2013-10-09 11:29                 ` Julien Grall
2013-10-09 12:05                   ` Ian Campbell
2013-10-15  8:41               ` Chen Baozi [this message]
2013-10-10  8:05             ` Chen Baozi
2013-10-10 11:07               ` Julien Grall
2013-10-10 11:36                 ` Chen Baozi
2013-10-10 12:04                   ` Vaibhav Bedia
2013-10-07 10:19 ` 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=AF3F5E2C-6C4F-4C80-A3E6-D9C806C40183@gmail.com \
    --to=baozich@gmail.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=julien.grall@linaro.org \
    --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.