From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: adeos-main <adeos-main@gna.org>, xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] Re: [Adeos-main] [RFC][PATCH 2/2] detect domain violations
Date: Fri, 29 Sep 2006 17:26:20 +0200 [thread overview]
Message-ID: <1159543580.4973.3.camel@domain.hid> (raw)
In-Reply-To: <451D38BA.1070105@domain.hid>
On Fri, 2006-09-29 at 17:16 +0200, Jan Kiszka wrote:
> Jan Kiszka wrote:
> > ...
> > This patch is an RFC as the following issues need to be resolved:
> >
> > o The might be parts of I-pipe remaining that make use of
> > preemp_disable even over non-root contexts. Philippe indicated the
> > PPC PIC code would be one example.
>
> Mmpf, first test, then post. Looks like there are more subtle scenarios
> hidden:
>
[...]
> Namely, __switch_to->__unlazy_fpu->save_init_fpu->preempt_disable.
> Philippe, looks like killing the ipipe_preempt_guard is not trivial...
>
> Anyway, attached version 2 of this patch enables both stack dump and
> ipipe-backtrace.
>
No, it's not. This is the reason why we should make this disabling an
obscure I-pipe config option (like in the kernel hacking section,
default off), so that each and every platform could be validated
separately, before actually removing the whole damn thing from
linux/preempt.h.
--
Philippe.
prev parent reply other threads:[~2006-09-29 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 14:54 [Xenomai-core] [RFC][PATCH 2/2] detect domain violations Jan Kiszka
2006-09-29 15:16 ` [Xenomai-core] Re: [Adeos-main] " Jan Kiszka
2006-09-29 15:26 ` Philippe Gerum [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=1159543580.4973.3.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=adeos-main@gna.org \
--cc=jan.kiszka@domain.hid \
--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.