All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>,
	Philippe Gerum <rpm@xenomai.org>
Cc: xenomai-help <xenomai@xenomai.org>, adeos-main <adeos-main@gna.org>
Subject: [Xenomai-help] __ipipe_syscall_root logic (was: BUG fs/buffer.c with Linux 2.6.26, 27)
Date: Wed, 18 Feb 2009 14:33:39 +0100	[thread overview]
Message-ID: <499C0E33.3070606@domain.hid> (raw)
In-Reply-To: <499BF9BB.3090700@domain.hid>

Jan Kiszka wrote:
> ...
> However, let's assumed we entered __ipipe_syscall_root with root domain
> stalled. If we then return from __ipipe_dispatch_event with 0 (=>
> forward this syscall to Linux), we would not call __fixup_if again so
> that the stalled state is kept. Is this a valid scenario for the given
> task, or would this be broken already? At least it looks like the path
> taken here

Could someone explain __ipipe_syscall_root to me? The comment before the
second __fixup_if() does not help me understanding why we only have to
call it when we do not forward the syscall to Linux. In other words,
this version would make more sense to me (32-bit variant, but 64-bit
looks as fishy as its little brother):

--- a/arch/x86/kernel/ipipe.c
+++ b/arch/x86/kernel/ipipe.c
@@ -540,6 +540,7 @@ asmlinkage void __ipipe_unstall_iret_roo
 asmlinkage int __ipipe_syscall_root(struct pt_regs regs)
 {
 	unsigned long flags;
+	int pass;
 
 	__fixup_if(&regs);
 
@@ -551,8 +552,9 @@ asmlinkage int __ipipe_syscall_root(stru
 	   tail work has to be performed (for handling signals etc). */
 
 	if (__ipipe_syscall_watched_p(current, regs.orig_ax) &&
-	    __ipipe_event_monitored_p(IPIPE_EVENT_SYSCALL) &&
-	    __ipipe_dispatch_event(IPIPE_EVENT_SYSCALL,&regs) > 0) {
+	    __ipipe_event_monitored_p(IPIPE_EVENT_SYSCALL)) {
+		pass = !__ipipe_dispatch_event(IPIPE_EVENT_SYSCALL,&regs);
+
 		/* We might enter here over a non-root domain and exit
 		 * over the root one as a result of the syscall
 		 * (i.e. by recycling the register set of the current
@@ -562,6 +564,9 @@ asmlinkage int __ipipe_syscall_root(stru
 		 * stall bit on exit. */
 		__fixup_if(&regs);
 
+		if (pass)
+			return 0;
+
 		if (ipipe_root_domain_p && !in_atomic()) {
 			/* Sync pending VIRQs before _TIF_NEED_RESCHED is tested. */
 			local_irq_save_hw(flags);

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux


  reply	other threads:[~2009-02-18 13:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 22:14 [Xenomai-help] BUG fs/buffer.c with Linux 2.6.26,27 Roman Pisl
2009-02-17 22:38 ` Philippe Gerum
2009-02-17 22:50 ` Jan Kiszka
2009-02-18  0:07   ` Gilles Chanteperdrix
2009-02-18  0:26     ` Gilles Chanteperdrix
2009-02-18  7:58       ` Jan Kiszka
2009-02-18 10:28         ` Gilles Chanteperdrix
2009-02-18 12:06           ` Jan Kiszka
2009-02-18 13:33             ` Jan Kiszka [this message]
2009-02-18 13:52               ` [Xenomai-help] __ipipe_syscall_root logic Gilles Chanteperdrix
2009-02-18 13:56                 ` Jan Kiszka
2009-02-19 15:49               ` [Xenomai-help] [Adeos-main] " Philippe Gerum
2009-02-19 16:14                 ` Jan Kiszka
2009-02-19 16:22                   ` Philippe Gerum
2009-02-18 19:15 ` [Xenomai-help] BUG fs/buffer.c with Linux 2.6.26,27 Philippe Gerum
2009-02-19 17:38   ` Roman Pisl
2009-02-19 18:08     ` Jan Kiszka
2009-02-19 18:23       ` Steven Seeger
2009-02-19 18:32         ` Philippe Gerum
2009-02-20 11:37     ` Philippe Gerum
2009-02-20 12:05       ` Jan Kiszka
2009-02-20 12:10       ` Roman Pisl

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=499C0E33.3070606@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=adeos-main@gna.org \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.