From: Jan Kiszka <jan.kiszka@siemens.com>
To: Antoine Durand <wanipof@gmail.com>,
Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] I-Pipe Tracer and linux ftrace
Date: Tue, 23 Jun 2015 19:00:03 +0200 [thread overview]
Message-ID: <55899093.4050006@siemens.com> (raw)
In-Reply-To: <CAOL1OyOdg9S=G412PAsiJCkaSii9Pgu17a_0=gOHaOyr=fHaDQ@mail.gmail.com>
On 2015-06-23 18:18, Antoine Durand wrote:
> booting with 'maxcpus=2' in my case has the same behavior than
> CONFIG_NR_CPUS=2
> the clocksource switche to refined-jiffies and system time is wrong (very
> very slow)
Ugh, reproduced something with a 4-core VM and maxcpus=2. I get a kernel
crash in __ipipe_ack_hrtimer_irq. Probably an online vs. possible cpus
issue. Will look into this.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2015-06-23 17:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 16:06 [Xenomai] I-Pipe Tracer and linux ftrace Antoine Durand
2015-06-22 17:20 ` Jan Kiszka
2015-06-22 20:47 ` Antoine Durand
2015-06-23 6:19 ` Jan Kiszka
2015-06-23 10:09 ` Antoine Durand
2015-06-23 14:11 ` Lennart Sorensen
2015-06-23 14:15 ` Jan Kiszka
2015-06-23 14:27 ` Gilles Chanteperdrix
2015-06-23 14:41 ` Antoine Durand
2015-06-23 14:43 ` Jan Kiszka
2015-06-23 14:46 ` Gilles Chanteperdrix
2015-06-23 14:47 ` Antoine Durand
2015-06-23 14:49 ` Gilles Chanteperdrix
2015-06-23 14:59 ` Jan Kiszka
2015-06-23 15:01 ` Antoine Durand
2015-06-23 16:07 ` Lennart Sorensen
2015-06-23 16:18 ` Antoine Durand
2015-06-23 17:00 ` Jan Kiszka [this message]
2015-06-23 17:23 ` Jan Kiszka
2015-06-24 7:30 ` Antoine Durand
[not found] ` <CAOL1OyNELX_6g8fOSS8wuJ+6-TzrBXjoxn3wH-Gb8u-HKHFqSw@mail.gmail.com>
2015-06-23 14:42 ` Jan Kiszka
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=55899093.4050006@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=wanipof@gmail.com \
--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.