All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: "Mauerer, Wolfgang" <wolfgang.mauerer@domain.hid>,
	xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Domain switch during page fault handling
Date: Fri, 22 Jan 2010 18:48:43 +0100	[thread overview]
Message-ID: <4B59E4FB.5070003@domain.hid> (raw)
In-Reply-To: <4B59E3B9.6060303@domain.hid>

Jan Kiszka wrote:
> Philippe Gerum wrote:
>> On Fri, 2010-01-22 at 17:58 +0100, Jan Kiszka wrote: 
>>> Hi guys,
>>>
>>> we are currently trying to catch an ugly Linux pipeline state corruption
>>> on x86-64.
>>>
>>> Conceptual question: If a Xenomai task causes a fault, we enter
>>> ipipe_trap_notify over the primary domain and leave it over the root
>>> domain, right? Now, if the root domain happened to be stalled when the
>>> exception happened, where should it normally be unstalled again,
>>> *for_that_task*? Our problem is that we generate a code path where this
>>> does not happen.
>> xnhadow_relax -> ipipe_reenter_root -> finish_task_switch ->
>> finish_lock_switch -> unstall
>>
>> Since xnshadow_relax is called on behalf the event dispatcher, we should
>> expect it to return with the root domain unstalled after a domain
>> downgrade, from primary to root.
> 
> That all happens as expected. But then __ipipe_handle_exception - as it
> last duty - ruins our day by replaying an unrelated root state.
> 

To illustrate what goes wrong (maybe it already fixes the issue, but it
may have side effects and is surely not clean):

diff --git a/arch/x86/kernel/ipipe.c b/arch/x86/kernel/ipipe.c
index 4442d96..b6a3720 100644
--- a/arch/x86/kernel/ipipe.c
+++ b/arch/x86/kernel/ipipe.c
@@ -702,11 +702,14 @@ static int __ipipe_xlate_signo[] = {
 
 int __ipipe_handle_exception(struct pt_regs *regs, long error_code, int vector)
 {
-	unsigned long flags;
+	struct ipipe_domain *entry_domain = ipipe_current_domain;
+	unsigned long flags, entry_dom_flags;
 
 	/* Pick up the root domain state of the interrupted context. */
 	local_save_flags(flags);
 
+	entry_dom_flags = ipipe_test_pipeline() ? 0 : X86_EFLAGS_IF;
+
 	if (ipipe_root_domain_p) {
 		/*
 		 * Replicate hw interrupt state into the virtual mask before
@@ -729,6 +732,9 @@ int __ipipe_handle_exception(struct pt_regs *regs, long error_code, int vector)
 		return 1;
 	}
 
+	if (entry_domain != ipipe_current_domain)
+		flags = entry_dom_flags;
+
 	/*
 	 * 32-bit: In case we migrated to root domain inside the event
 	 * handler, restore the original IF from exception entry as the


Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux


  reply	other threads:[~2010-01-22 17:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-22 16:58 [Xenomai-core] Domain switch during page fault handling Jan Kiszka
2010-01-22 17:10 ` Jan Kiszka
2010-01-22 17:37 ` Philippe Gerum
2010-01-22 17:39   ` Gilles Chanteperdrix
2010-01-22 17:41     ` Jan Kiszka
2010-01-22 17:52       ` Philippe Gerum
2010-01-22 18:03         ` Jan Kiszka
2010-01-22 18:08           ` Philippe Gerum
2010-01-23  9:59             ` Philippe Gerum
2010-01-23 10:09               ` Jan Kiszka
2010-01-23 10:12                 ` Philippe Gerum
2010-01-23 10:20                   ` Gilles Chanteperdrix
2010-01-23 10:36                     ` Jan Kiszka
2010-01-23 11:17                       ` Jan Kiszka
2010-01-23 10:33                   ` Jan Kiszka
2010-01-24 10:25                     ` Philippe Gerum
2010-01-24 10:45                       ` Jan Kiszka
2010-01-24 11:35                         ` Philippe Gerum
2010-01-22 17:43   ` Jan Kiszka
2010-01-22 17:48     ` Jan Kiszka [this message]
2010-01-22 17:38 ` Gilles Chanteperdrix

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=4B59E4FB.5070003@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=rpm@xenomai.org \
    --cc=wolfgang.mauerer@domain.hid \
    --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.