From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Jorge Ramirez Ortiz, HCL Europe" <Jorge.Ramirez-Ortiz@hcl.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] BUG: Unhandled exception over domain Xenomai - switching to ROOT
Date: Fri, 13 Jul 2012 14:31:46 +0200 [thread overview]
Message-ID: <50001532.60406@xenomai.org> (raw)
In-Reply-To: <4F534D1A615F544D95E57BFD8460658302FEBD85@GEO-HCLT-UKEVS1.GEO.CORP.HCL.IN>
On 07/13/2012 01:24 PM, Jorge Ramirez Ortiz, HCL Europe wrote:
> Yes it does: the caller ignores upfront whether the call will be
> handled in realtime or non-realtime context by the driver. The client
> (of course!) can/should (it doesn't really matter for the sake of the
> argument) take the adequate measures to make sure it will get into
> the adequate path. But the _interface_ does not guarantee which path
> it will take. This is a fact that you can't disagree with.
>
> But please allow me to re-frame the discussion: I am not discussing
> here about realtime design practises or about how to use the
> framework properly. I am merely commenting on the _interfaces_ to
> the realtime framework and their consistency.
Philippe and Jan have answered already, so I am going to make it really
short.
The Linux kernel API has hundreds of services, much of which can not be
re-entered from an RT context, that is a consequence of the "dual
kernel" model. It would simply be silly to assume that we have put LARTs
in these hundreds of services. Knowing that you can not call linux
services when in RT context in driver code is simply part of the things
you should know when developing an RTDM driver.
You forgot that, you got bitten, now get over it.
--
Gilles.
next prev parent reply other threads:[~2012-07-13 12:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 18:10 [Xenomai] BUG: Unhandled exception over domain Xenomai - switching to ROOT Jorge Ramirez Ortiz, HCL Europe
2012-07-12 0:21 ` Gilles Chanteperdrix
2012-07-12 8:16 ` Jorge Ramirez Ortiz, HCL Europe
2012-07-12 8:31 ` Gilles Chanteperdrix
2012-07-12 21:29 ` Jorge Ramirez Ortiz, HCL Europe
2012-07-13 7:27 ` Gilles Chanteperdrix
2012-07-13 9:34 ` Philippe Gerum
2012-07-13 10:41 ` Jorge Ramirez Ortiz, HCL Europe
2012-07-13 11:08 ` Philippe Gerum
2012-07-13 11:24 ` Jorge Ramirez Ortiz, HCL Europe
2012-07-13 11:58 ` Jan Kiszka
2012-07-13 16:27 ` Jorge Ramirez Ortiz, HCL Europe
2012-07-13 17:47 ` Gilles Chanteperdrix
2012-07-16 9:10 ` Jorge Ramirez Ortiz, HCL Europe
2012-07-13 12:31 ` Gilles Chanteperdrix [this message]
2012-07-13 16:39 ` Jorge Ramirez Ortiz, HCL Europe
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=50001532.60406@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Jorge.Ramirez-Ortiz@hcl.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.