From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Andreas Galauner <andreas@galauner.de>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Xenomai on Linux 3.18 on Zynq
Date: Fri, 10 Apr 2015 18:11:12 +0200 [thread overview]
Message-ID: <20150410161112.GR20752@hermes.click-hack.org> (raw)
In-Reply-To: <5527DF9B.9020304@galauner.de>
On Fri, Apr 10, 2015 at 04:35:07PM +0200, Andreas Galauner wrote:
> On a sidenote: That patch
> https://git.xenomai.org/ipipe-gch.git/commit/?h=for-ipipe-3.18&id=f98b6d95359ea0429307d98759357d54dcfba7e8
> makes the board stop directly after the bootloader jumps into the
> kernel.
Please try branch for-ipipe-3.18 in ipipe-gch.git, it contains a
totally untested, not even compiled patch for fixing this particular
issue.
In short, I believe kmalloc may be using percpu, so ends-up using
ipipe_processor_id() which ends up dereferencing the NULL
__cpu_reverse_map, so I temporarily set __cpu_reverse_map to
__cpu_logical_map before calling kmalloc.
This is correct, because at this point in the code we can rely on
__cpu_logical_map to contain what is necessary to be used as a
reverse map.
If the kernel still crashes, then the problem does not come from
kmalloc using per-cpu data.
--
Gilles.
next prev parent reply other threads:[~2015-04-10 16:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 14:35 [Xenomai] Xenomai on Linux 3.18 on Zynq Andreas Galauner
2015-04-10 15:09 ` Stefan Roese
2015-04-10 15:15 ` Andreas Galauner
2015-04-10 15:26 ` Stefan Roese
2015-04-10 15:24 ` Gilles Chanteperdrix
2015-04-10 15:29 ` Gilles Chanteperdrix
2015-04-10 16:06 ` Andreas Galauner
2015-04-10 16:14 ` Gilles Chanteperdrix
2015-04-10 16:11 ` Gilles Chanteperdrix [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-05 8:31 Philippe.Corbel
2015-11-05 11:00 ` Stefan Roese
2015-11-05 12:13 ` Philippe.Corbel
2015-11-05 20:46 ` Gilles Chanteperdrix
2015-11-06 10:49 ` Philippe.Corbel
2015-11-06 10:57 ` Gilles Chanteperdrix
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=20150410161112.GR20752@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=andreas@galauner.de \
--cc=xenomai@xenomai.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.