From: Philippe Gerum <rpm@xenomai.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] [RFC, PATCH] per-thread exec-time stats
Date: Fri, 07 Jul 2006 16:25:32 +0200 [thread overview]
Message-ID: <1152282333.5035.46.camel@domain.hid> (raw)
In-Reply-To: <17582.26845.522459.204811@domain.hid>
On Fri, 2006-07-07 at 15:59 +0200, Gilles Chanteperdrix wrote:
> Philippe Gerum wrote:
> > > xnpod_acc_exec_time() is called from within xnpod_schedule() that is
> > > called from within xnpod_migrate_thread() at a time where
> > > threadout->sched is the wrong pointer.
> >
> > Gasp. Unfortunately, we are trapped by an exception case, and I don't
> > see any better approach.
>
> We could reimplement an xnpod_migrate_thread() which suspend the calling
> thread and wake up a server thread on the destination CPU, this server
> thread migrating the suspended thread by changing its sched pointer
> outside of xnpod_schedule().
>
No, really. A small hack to get per-thread accounting should not trigger
a storm of fundamental changes like this.
> Or we can get rid of xnpod_migrate_thread(), it is currently not used by
> any skin.
>
It's a fundamental feature for placing SMP jobs, and kernel-based
Xenomai threads could not rely on sched_setscheduler() to do it. Let's
keep this service, and simply pass the sched pointer to the accumulation
routine; I was wrong initially suggesting the opposite. IOW, let's avoid
smashing a squadron of flies with nukes...
--
Philippe.
next prev parent reply other threads:[~2006-07-07 14:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 11:37 [Xenomai-core] [RFC, PATCH] per-thread exec-time stats Jan Kiszka
2006-07-06 11:41 ` Jan Kiszka
2006-07-06 14:32 ` Philippe Gerum
2006-07-06 15:09 ` Jan Kiszka
2006-07-06 15:37 ` Philippe Gerum
2006-07-06 15:46 ` Jan Kiszka
2006-07-06 16:36 ` Jan Kiszka
2006-07-06 17:17 ` Jan Kiszka
2006-07-07 8:20 ` Jan Kiszka
2006-07-07 8:04 ` Philippe Gerum
2006-07-07 8:09 ` Jan Kiszka
2006-07-07 8:49 ` Philippe Gerum
2006-07-07 9:03 ` Jan Kiszka
2006-07-07 11:28 ` Philippe Gerum
2006-07-06 16:37 ` Philippe Gerum
2006-07-06 23:47 ` Gilles Chanteperdrix
2006-07-07 7:54 ` Philippe Gerum
2006-07-07 10:22 ` Gilles Chanteperdrix
2006-07-07 10:30 ` Jan Kiszka
2006-07-07 13:23 ` Philippe Gerum
2006-07-07 13:59 ` Gilles Chanteperdrix
2006-07-07 14:25 ` Philippe Gerum [this message]
2006-07-06 15:04 ` Philippe Gerum
2006-07-06 15:06 ` 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=1152282333.5035.46.camel@domain.hid \
--to=rpm@xenomai.org \
--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.