All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] I-pipe on ARM platform.
Date: Sun, 07 Apr 2013 17:13:50 +0200	[thread overview]
Message-ID: <51618D2E.6080702@xenomai.org> (raw)
In-Reply-To: <51618C48.7040505@xenomai.org>

On 04/07/2013 05:10 PM, Gilles Chanteperdrix wrote:

> On 04/06/2013 08:32 PM, Jan Kiszka wrote:
> 
>> On 2013-04-06 20:27, Gilles Chanteperdrix wrote:
>>>> And it has to map directly to might_fault
>>>> in case CONFIG_IPIPE_DEBUG_CONTEXT is disabled (thus zero overhead).
>>>
>>> That would defeat the purpose of the patch. might_fault can not be
>>> called over non root domains.
>>
>> True. But we should avoid leaving the costly irq-disable/enable and
>> domain checks in production code behind when might_fault actually
>> resolves to a nop. That should be the case for
>> !CONFIG_DEBUG_ATOMIC_SLEEP && !CONFIG_PROVE_LOCKING.
> 
> 
> I am almost sure I did not have either of these two options enabled when
> I observed the bug.
> 

migh_fault also resolves to _cond_resched() when
CONFIG_PREEMPT_VOLUNTARY is enabled.

-- 
                                                                Gilles.


  reply	other threads:[~2013-04-07 15:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 20:58 [Xenomai] I-pipe on ARM platform Gilles Chanteperdrix
2013-04-06  9:48 ` Jan Kiszka
2013-04-06 13:24   ` Philippe Gerum
2013-04-06 18:27   ` Gilles Chanteperdrix
2013-04-06 18:32     ` Jan Kiszka
2013-04-07 15:10       ` Gilles Chanteperdrix
2013-04-07 15:13         ` Gilles Chanteperdrix [this message]
2013-04-07 15:14         ` Jan Kiszka
2013-04-07 15:26           ` Gilles Chanteperdrix
2013-04-07 16:55   ` Gilles Chanteperdrix
2013-04-07 18:47     ` Gilles Chanteperdrix
2013-04-07 19:01       ` Jan Kiszka
2013-04-07 19:16         ` Gilles Chanteperdrix
2013-04-08 21:02           ` 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=51618D2E.6080702@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=jan.kiszka@web.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.