From: Ninja <Ninja15@gmx.de>
To: linux-media <linux-media@vger.kernel.org>
Cc: Marko Ristola <marko.ristola@kolumbus.fi>
Subject: Re: Mantis CAM not SMP safe / Activating CAM on Technisat Skystar HD2 (DVB-S2)
Date: Tue, 13 Dec 2011 22:30:33 +0100 [thread overview]
Message-ID: <4EE7C3F9.1080703@gmx.de> (raw)
In-Reply-To: <4EE5E0BE.4060300@kolumbus.fi>
Am 12.12.2011 12:08, schrieb Marko Ristola:
> On 12/10/2011 01:57 AM, Ninja wrote:
>> Hi,
>>
>> has anyone an idea how the SMP problems could be fixed?
>
> You could turn on Mantis Kernel module's debug messages.
> It could tell you the emitted interrupts.
>
> One risky thing with the Interrupt handler code is that
> MANTIS_GPIF_STATUS is cleared, even though IRQ0 isn't active yet.
> This could lead to a rare starvation of the wait queue you described.
> I supplied a patch below. Does it help?
>
>> I did some further investigation. When comparing the number of
>> interrupts with all cores enabled and the interrupts with only one
>> core enabled it seems like only the IRQ0 changed, the other IRQs and
>> the total number stays quite the same:
>>
>> 4 Cores:
>> All IRQ/sec: 493
>> Masked IRQ/sec: 400
>> Unknown IRQ/sec: 0
>> DMA/sec: 400
>> IRQ-0/sec: 143
>> IRQ-1/sec: 0
>> OCERR/sec: 0
>> PABRT/sec: 0
>> RIPRR/sec: 0
>> PPERR/sec: 0
>> FTRGT/sec: 0
>> RISCI/sec: 258
>> RACK/sec: 0
>>
>> 1 Core:
>> All IRQ/sec: 518
>> Masked IRQ/sec: 504
>> Unknown IRQ/sec: 0
>> DMA/sec: 504
>> IRQ-0/sec: 246
>> IRQ-1/sec: 0
>> OCERR/sec: 0
>> PABRT/sec: 0
>> RIPRR/sec: 0
>> PPERR/sec: 0
>> FTRGT/sec: 0
>> RISCI/sec: 258
>> RACK/sec: 0
>>
>> So, where might be the problem?
> Turning on Mantis debug messages, might tell the difference between
> these interrupts.
>
> ....
>> I hope somebody can help, because I think we are very close to a
>> fully functional CAM here.
>> I ran out of things to test to get closer to the solution :(
>> Btw: Is there any documentation available for the mantis PCI bridge?
> Not that I know.
>
>>
>> Manuel
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-media" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
>
> Regards,
> Marko Ristola
>
Hi Marko,
thanks for the patch. I did some quick testing today. The IRQ0 problem
stays, but it seems like the small hangs (3-5 seconds every 20 minutes
or something) are fixed :)
Manuel
next prev parent reply other threads:[~2011-12-13 21:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 23:29 Mantis CAM not SMP safe / Activating CAM on Technisat Skystar HD2 (DVB-S2) Ninja
2011-12-09 23:57 ` Ninja
2011-12-12 11:08 ` Marko Ristola
2011-12-13 21:30 ` Ninja [this message]
2011-12-16 8:10 ` Ninja
-- strict thread matches above, loose matches on Subject: below --
2011-11-13 23:17 Ninja
2011-11-13 19:30 Ninja
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=4EE7C3F9.1080703@gmx.de \
--to=ninja15@gmx.de \
--cc=linux-media@vger.kernel.org \
--cc=marko.ristola@kolumbus.fi \
/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.