From: Jan Kiszka <jan.kiszka@domain.hid>
To: xenomai-core <xenomai@xenomai.org>
Cc: adeos-main <adeos-main@gna.org>
Subject: Re: [Xenomai-core] FYI: CONFIG_PERF_EVENTS conflicts with Xenomai shadows
Date: Wed, 31 Mar 2010 18:53:30 +0200 [thread overview]
Message-ID: <4BB37E0A.1020507@domain.hid> (raw)
In-Reply-To: <4BB3532D.2070305@domain.hid>
Jan Kiszka wrote:
> Hi,
>
> just ran into an ugly warning of I-pipe as I happened to have
> CONFIG_PERF_EVENTS enabled in 2.6.32 kernel. That pulls some plain Linux
> spinlock into the finish_task_switch path.
>
> We should either disable this feature at I-pipe level or patch it
> properly. Haven't checked yet if the latter is feasible with moderate
> effort, though.
>
At least this one is now explainable: There is no problem related to
CONFIG_PERF_EVENTS. finish_task_switch is not part of the critical
shadow task switch, and the oops I saw finally turned out to be caused
by my buggy virtual hardware (IOW: an unrelated hypervisor bug). Nothing
to worry about for Xenomai or I-pipe.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2010-03-31 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 13:50 [Xenomai-core] FYI: CONFIG_PERF_EVENTS conflicts with Xenomai shadows Jan Kiszka
2010-03-31 16:53 ` Jan Kiszka [this message]
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=4BB37E0A.1020507@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=adeos-main@gna.org \
--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.