MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17503.15830.52960.611596@domain.hid> Date: Mon, 8 May 2006 14:47:18 +0200 Subject: Re: [Xenomai-core] [RFC][patch] per-process data. In-Reply-To: References: <17502.13773.674199.219762@domain.hid> <445E637A.5080706@domain.hid> <17502.32006.418774.459215@domain.hid> From: Gilles Chanteperdrix List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Dmitry Adamushko Cc: Jan Kiszka , xenomai@xenomai.org Dmitry Adamushko wrote: > On 08/05/06, Gilles Chanteperdrix wrote: > > Jan Kiszka wrote: > > > Likely I did not yet get the full picture: What prevents using another > > > adeos per-task key for this? > > > > We would need a per-task key for every skin that needs a per-process > > data, but more importantly, we would need to track the clone syscalls > > (that would be another adeos event) in order to propagate the per-task > > data to each thread of the process. Or maybe ptds are inherited upon > > clone ? > > All of them are cleared in kernel/fork.c :: copy_process(). At least, > the one pointed by "nkgkptd" (keeps shadow's xnthread_t *) must be > cleared. Another logic could be applied for the rest, I guess. It make sense, if they were not cleared, they would not be per-thread data. -- Gilles Chanteperdrix.