From: Philippe Gerum <rpm@xenomai.org>
To: Anders Blomdell <anders.blomdell@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] [BUG] Interrupt problem on powerpc
Date: Mon, 30 Jan 2006 19:03:08 +0100 [thread overview]
Message-ID: <43DE54DC.4080802@domain.hid> (raw)
In-Reply-To: <43DE44AD.7000208@domain.hid>
Anders Blomdell wrote:
> Philippe Gerum wrote:
>
>> Anders Blomdell wrote:
>>
>>> On a PrPMC800 (PPC 7410 processor) withe Xenomai-2.1-rc2, I get the
>>> following if the interrupt handler takes too long (i.e. next
>>> interrupt gets generated before the previous one has finished)
>>>
>>> [ 42.543765] [c00c2008] spin_bug+0xa8/0xc4
>>> [ 42.597617] [c00c22d4] _raw_spin_lock+0x180/0x184
>>
>>
>>
>> Someone (in arch/ppc64/kernel/*.c?) is spinlocking+irqsave desc->lock
>
> more likely arch/ppc/kernel/*.c :-)
>
Gah... looks like I'm still confused by ia64 issues I'm chasing right now. (Why on
earth do we need so many bits on our CPUs that only serve the purpose of raising
so many problems?)
>> for any given IRQ without using the Adeos *_hw() spinlock variant that
>> masks the interrupt at hw level. So we seem to have:
>>
>> spin_lock_irqsave(&desc->lock)
>> <hw IRQ>
>> __ipipe_grab_irq
>> __ipipe_handle_irq
>> __ipipe_ack_irq
>> spin_lock...(&desc->lock)
>> deadlock.
>>
>> The point is about having spinlock_irqsave only _virtually_ masking
>> the interrupts by preventing their associated Linux handler from being
>> called, but despite this, Adeos still actually acquires and
>> acknowledges the incoming hw events before logging them, even if their
>> associated action happen to be postponed until spinlock_irq_restore()
>> is called.
>>
>> To solve this, all spinlocks potentially touched by the ipipe's
>> primary IRQ handler and/or the code it calls indirectly, _must_ be
>> operated using the _hw() call variant all over the kernel, so that no
>> hw IRQ can be taken while those spinlocks are held by Linux. Usually,
>> only the spinlock(s) protecting the interrupt descriptors or the PIC
>> hardware are concerned.
>
> So you will expect an addition to the ipipe patch then?
>
Yep. We first need to find out who's grabbing the shared spinlock using the
vanilla Linux primitives.
> /Anders
>
--
Philippe.
prev parent reply other threads:[~2006-01-30 18:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 14:07 [Xenomai-core] [BUG] Interrupt problem on powerpc Anders Blomdell
2006-01-30 14:39 ` Jan Kiszka
2006-01-30 16:10 ` Anders Blomdell
2006-01-30 16:31 ` Jan Kiszka
2006-01-30 16:50 ` Anders Blomdell
2006-02-01 9:12 ` [Xenomai-core] [BUG] version mismatch Anders Blomdell
2006-02-01 18:17 ` Philippe Gerum
2006-01-30 16:31 ` [Xenomai-core] [BUG] Interrupt problem on powerpc Philippe Gerum
2006-01-30 16:54 ` Anders Blomdell
2006-01-30 18:03 ` 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=43DE54DC.4080802@domain.hid \
--to=rpm@xenomai.org \
--cc=anders.blomdell@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.