All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: adeos-main <adeos-main@gna.org>
Subject: Re: [Adeos-main] x86-32: Unpreemptible return from __ipipe_handle_irq
Date: Mon, 13 Sep 2010 09:51:50 +0200	[thread overview]
Message-ID: <1284364310.24088.786.camel@domain.hid> (raw)
In-Reply-To: <4C87BFA3.5040207@domain.hid>

On Wed, 2010-09-08 at 18:53 +0200, Jan Kiszka wrote:
> Hi Philippe,
> 
> __ipipe_handle_irq:
> 
> #if defined(CONFIG_X86_32) && defined(CONFIG_SMP)
> 	/*
> 	 * Prevent a spurious rescheduling from being triggered on
> 	 * preemptible kernels along the way out through
> 	 * ret_from_intr.
> 	 */
> 	if ((long)regs->orig_ax < 0)
> 		__set_bit(IPIPE_STALL_FLAG, &ipipe_root_cpudom_var(status));
> #endif	/* CONFIG_SMP */
> 
> But this defeats any preemption of kernel contexts on CONFIG_PREEMPT,
> doesn't it? __ipipe_test_preemption should now always fail.
> 
> What kind of spurious rescheduling has to be prevented?

This hack was introduced in 2.6.9; disabling preemption on the IRQ
return path was working around a SMP issue causing a crash. I would not
be surprised if such code was only papering over a migration issue in
fact, which probably disappeared later in the pipeline implementation.
x86_64 never required this, and it is likely time to re-assess the need
for this hack, and fix the issue properly if ever it still makes sense.

> 
> Jan
> 

-- 
Philippe.




      reply	other threads:[~2010-09-13  7:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 16:53 [Adeos-main] x86-32: Unpreemptible return from __ipipe_handle_irq Jan Kiszka
2010-09-13  7:51 ` Philippe Gerum [this message]

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=1284364310.24088.786.camel@domain.hid \
    --to=rpm@xenomai.org \
    --cc=adeos-main@gna.org \
    --cc=jan.kiszka@domain.hid \
    /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.