From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <5152CB6D.40208@siemens.com>
Date: Wed, 27 Mar 2013 11:35:25 +0100
From: Jan Kiszka <jan.kiszka@siemens.com>
MIME-Version: 1.0
References: <5151F44F.3050306@siemens.com> <5151F730.4090507@siemens.com>
	<5152C8FC.10705@xenomai.org> <5152C990.9050101@siemens.com>
	<5152CAC6.1020304@xenomai.org>
In-Reply-To: <5152CAC6.1020304@xenomai.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Xenomai] New domain migration process with ipipe-core and forge
List-Id: Discussions about the Xenomai project <xenomai.xenomai.org>
List-Unsubscribe: <http://www.xenomai.org/mailman/options/xenomai>,
	<mailto:xenomai-request@xenomai.org?subject=unsubscribe>
List-Archive: <http://www.xenomai.org/pipermail/xenomai>
List-Post: <mailto:xenomai@xenomai.org>
List-Help: <mailto:xenomai-request@xenomai.org?subject=help>
List-Subscribe: <http://www.xenomai.org/mailman/listinfo/xenomai>,
	<mailto:xenomai-request@xenomai.org?subject=subscribe>
To: Philippe Gerum <rpm@xenomai.org>
Cc: Xenomai <xenomai@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