From: Julien Grall <julien.grall@linaro.org>
To: Andrii Anisov <andrii.anisov@globallogic.com>,
Oleksandr Tyshchenko <oleksandr.tyshchenko@globallogic.com>
Cc: Julien Grall <julien.grall@citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Bringing up sequence for non-boot CPU fails
Date: Sat, 01 Mar 2014 23:58:48 +0800 [thread overview]
Message-ID: <531203B8.7070604@linaro.org> (raw)
In-Reply-To: <CAGQvs6hwsWkknOCprz67i6rPCycBuBf7hW+C9_jS2fvB1n5HiA@mail.gmail.com>
Hello Andrii and Oleksandr,
Sorry for the late answer.
On 19/02/14 20:35, Andrii Anisov wrote:
> The latest update is: Oleksandr tried solution suggested by Julien and
> the issue seems to be not reproducible.
Thanks for the update. I talked with Ian about this issue, the problem
may come from setup_pagetables (arch/arm/mm.c).
The function is zeros boot_pgtable, boot_first and boot_second, then
just clean the cache for theses ranges.
But ... when the secondary CPU sets up theses variables, the cache is
disabled. When the cache is enabled (just before we enable paging),
cache may contain data that was not reached the memory, therefore it
will shadow the real data.
Can you try these 2 small tests (separately):
- Flush all the cache before boot_pgtable is zeroed (arch/arm/mm.c:486)
- Flush all the cache after clean_xen_dcache(boot_second)
(arch/arm/mm.c:493)
If the former test is failing and not the latter, then we have found the
issue :).
I think the 3 clean_xen_dcache should be replaced by a clean and
invalidate dcache.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-03-01 15:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 11:44 Bringing up sequence for non-boot CPU fails Oleksandr Tyshchenko
2014-02-18 12:14 ` Ian Campbell
2014-02-18 12:36 ` Andrii Anisov
2014-02-18 12:53 ` Ian Campbell
2014-02-18 13:23 ` Andrii Anisov
2014-02-18 13:34 ` Ian Campbell
2014-02-18 13:37 ` Andrii Anisov
2014-02-18 15:33 ` Ian Campbell
2014-02-18 18:17 ` Oleksandr Tyshchenko
2014-02-18 18:33 ` Julien Grall
2014-02-18 18:40 ` Oleksandr Tyshchenko
2014-02-19 9:15 ` Ian Campbell
2014-02-19 12:35 ` Andrii Anisov
2014-03-01 15:58 ` Julien Grall [this message]
2014-03-04 16:50 ` Oleksandr Tyshchenko
2014-03-05 1:45 ` Ian Campbell
2014-02-19 9:04 ` Ian Campbell
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=531203B8.7070604@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=andrii.anisov@globallogic.com \
--cc=julien.grall@citrix.com \
--cc=oleksandr.tyshchenko@globallogic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).