All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Philippe Gerum <rpm@xenomai.org>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] New domain migration process with ipipe-core and forge
Date: Wed, 27 Mar 2013 11:35:25 +0100	[thread overview]
Message-ID: <5152CB6D.40208@siemens.com> (raw)
In-Reply-To: <5152CAC6.1020304@xenomai.org>

On 2013-03-27 11:32, Philippe Gerum wrote:
> On 03/27/2013 11:27 AM, Jan Kiszka wrote:
> 
>>> Nitpicking: in theory, the code should expect the migration hook to have
>>> actually done the work, and not delayed it like Xenomai currently does
>>> in practice.
>>
>> Where does Xenomai do that? I was looking for it but didn't find a log
>> flush.
>>
> 
> You mean delaying? Check per-arch xnarch_escalate(). Flushing occurs as 
> soon as the xnpod_schedule() caller unstalls the head domain, which has 
> to happen quickly after the delay was enforced.

Hmm, I still do not see where we should flush in Xenomai forge before
the return to complete_domain_migration and its clearance of the stall flag.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux


  reply	other threads:[~2013-03-27 10:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 19:17 [Xenomai] New domain migration process with ipipe-core and forge Jan Kiszka
2013-03-26 19:29 ` Jan Kiszka
2013-03-27 10:25   ` Philippe Gerum
2013-03-27 10:27     ` Jan Kiszka
2013-03-27 10:32       ` Philippe Gerum
2013-03-27 10:35         ` Jan Kiszka [this message]
2013-03-27 11:16           ` Philippe Gerum
2013-03-27 10:21 ` 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=5152CB6D.40208@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=rpm@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.