All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] [RFC][patch] per-process data.
Date: Sun, 07 May 2006 23:15:38 +0200	[thread overview]
Message-ID: <445E637A.5080706@domain.hid> (raw)
In-Reply-To: <17502.13773.674199.219762@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]

Gilles Chanteperdrix wrote:
> Hi,
> 
> for review, here are patches that provide Xenomai skins with a
> per-process per-skin data structures. It will allow skins to do
> per-process cleanup for example, or the posix skin to maintain a
> per-process signal mask.

That sounds promising!

> 
> In order to use it, the skins must pass an eventcb function to the
> xnshadow_register_interface service. This eventcb function gets called
> when:
> - a process bind the interfaces, the eventcb has to allocate the
>   per-process structure and must return a pointer to an xnppd_holder_t
>   member of this structure; 
> - the process exits, the eventcb function is then passed the
>   xnppd_holder_t pointer and may free the container structure.
> 
> The patch also add a service called xnppd_get, which must be passed the
> skin magic, and returns the xnppd_holder_t pointer attached to the
> current process.
> 
> This support relies on a new adeos event called "PEXIT" for
> process-exit, that get triggered in the mmput function when a process
> mm_struct get deallocated.

Likely I did not yet get the full picture: What prevents using another
adeos per-task key for this? And why is it required to establish a new
termination hook? Are there scenarios where the existing
task-termination hook is not suited for the planned cleanup work?

> 
> These patches are not ready for inclusion, they are not tested
> yet.
> 

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2006-05-07 21:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-07 18:00 [Xenomai-core] [RFC][patch] per-process data Gilles Chanteperdrix
2006-05-07 21:15 ` Jan Kiszka [this message]
2006-05-07 23:04   ` Gilles Chanteperdrix
2006-05-08 10:18     ` Dmitry Adamushko
2006-05-08 12:47       ` Gilles Chanteperdrix
2006-05-08 13:05     ` Jan Kiszka
2006-05-08 12:51 ` Gilles Chanteperdrix
2006-05-08 13:14   ` Gilles Chanteperdrix
2006-05-08 13:51   ` Philippe Gerum
2006-05-09 17:49     ` Gilles Chanteperdrix
2006-05-09 22:09       ` Philippe Gerum
2006-05-10 13:03         ` Gilles Chanteperdrix
2006-05-11 12:53           ` Philippe Gerum
2006-05-11 14:03             ` Gilles Chanteperdrix
2006-05-11 14:12               ` Philippe Gerum

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=445E637A.5080706@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.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.