From: Ian Campbell <Ian.Campbell@citrix.com>
To: Chen Baozi <baozich@gmail.com>
Cc: Grall Julien <julien.grall@linaro.org>,
List Xen Developer <xen-devel@lists.xen.org>
Subject: Re: Problems when using latest git tree to boot xen on OMAP5
Date: Mon, 7 Oct 2013 09:39:55 +0100 [thread overview]
Message-ID: <1381135195.21562.56.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <91879A6F-B459-4D10-A691-4A04915D82AA@gmail.com>
On Sun, 2013-10-06 at 22:21 +0800, Chen Baozi wrote:
> On Oct 4, 2013, at 10:11 PM, Chen Baozi <baozich@gmail.com> wrote:
>
> > Hi Julien,
> >
> > Since Ian has merged most my OMAP5 patches, I decide to try to update my working tree to it today. However, it seems it doesn't work as expected. There mainly two kind of problems that I met:
> >
> > 1. It seems that xen no longer maps some of io memory regions described in dts. For example, the memory regions in "ocp" node of omap5.dtsi.
>
> I looked into the codes today. It is because of checking
> dt_device_is_available() before map_device(). Some node, for
> example /ocp/mmc@480d1000, is disabled in omap5-uevm.dts separately
> from omap5.dtsi where it is original defined. In this case, xen won't
> map its memory region for dom0. However, it seems dom0 kernel still
> accesses those regions.
> I guess there would be a bug dealing with this situations?
It is certainly a bug in the kernel if it is accessing something which
is disabled. It may also independently be a bug in the dts that this
devices is disabled.
However in v3.12-rc4 I don't see mmc@480d1000 being disabled in
omap5-uevm.dts and I can't see anything in the history of that file
either. Where did your copy come from?
Hopefully we won't need a converse to the device blacklist, i.e. a
whitelist of disabled devices to pass through regardless of the DTS
enabled state.
Ian.
next prev parent reply other threads:[~2013-10-07 8:39 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 [this message]
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
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=1381135195.21562.56.camel@kazak.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=baozich@gmail.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.