All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Philippe Gerum <rpm@xenomai.org>
Cc: "Mauerer, Wolfgang" <wolfgang.mauerer@siemens.com>,
	Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] [PATCH] Revert "ipipe: ipipe_request_irq(), ipipe_free_irq() are root-only services"
Date: Thu, 20 Sep 2012 13:15:24 +0200	[thread overview]
Message-ID: <505AFACC.1050802@siemens.com> (raw)
In-Reply-To: <505AF687.9010002@siemens.com>

On 2012-09-20 12:57, Jan Kiszka wrote:
> On 2012-09-20 12:56, Jan Kiszka wrote:
>> On 2012-09-20 12:49, Philippe Gerum wrote:
>>> On 09/20/2012 12:37 PM, Jan Kiszka wrote:
>>>> This reverts commit 073ff1e8045d0311b8cf390687c0ba3619681672.
>>>>
>>>> Both service are NOT just root-only services. E.g., rtdm_irq_request
>>>> requires by specification support also over non-Linux contexts.
>>>
>>> Nack. We can't run the enable code for MSIs over non-root, and
>>> that code typically follows the irq request. Besides, we want to mask
>>> the source upon irq free to handle the SMP case properly, which we could
>>> not do from non-root with MSIs.
>>>
>>> So either we have both request+enable and free usable over non-root, or
>>> there is no point.
>>
>> OK, I get the point with legacy MSI. Then we have two other bugs to solve:
>>  - in I-pipe as it holds a hardened spin lock across enable/disable (of
>>    MSIs)

I think this bug may only manifest over ARM as that arch does
enable/disable_irq() inside __ipipe_enable/disable_irqdesc - unless
something prevents that enabling will ever happen for interrupts that
need Linux locks to work. Is that assured?

>>  - in Xenomai 2.6 (at least, didn't check forge) as it calls with a
>>    hardened spin lock held into ipipe_virtualize_irq

This problem is something I vaguely recall we discussed before already
in the past. I think there was no good solution for the Xenomai 2
architecture.

In this light, let's remove those checks nevertheless.
Enabling/disabling the IRQ are separate calls, and those should be
instrumented as those cause the restriction.

> 
> Sorry, three bugs:
>  - in the RTDM spec as it always allowed rtdm_irq_request over RT task
>    contexts

Changing the spec and adding a runtime check will likely be no issue. No
sane driver should have made use of that option. I will file a patch.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux


  parent reply	other threads:[~2012-09-20 11:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 10:37 [Xenomai] [PATCH] Revert "ipipe: ipipe_request_irq(), ipipe_free_irq() are root-only services" Jan Kiszka
2012-09-20 10:49 ` Philippe Gerum
2012-09-20 10:56   ` Jan Kiszka
2012-09-20 10:57     ` Jan Kiszka
2012-09-20 11:06       ` Philippe Gerum
2012-09-20 11:15       ` Jan Kiszka [this message]
2012-09-20 11:27         ` Jan Kiszka
2012-09-20 13:01         ` Gilles Chanteperdrix
2012-09-20 13:15           ` Jan Kiszka
2012-09-20 14:12             ` Gilles Chanteperdrix
2012-09-20 15:00               ` Jan Kiszka
2012-09-20 15:13                 ` Gilles Chanteperdrix
2012-09-20 13:10         ` Philippe Gerum
2012-09-20 13:54           ` Jan Kiszka
2012-09-20 14:05             ` Philippe Gerum
2012-09-20 15:07               ` Jan Kiszka
2012-09-20 15:16                 ` Philippe Gerum
2012-09-20 15:45                   ` Jan Kiszka

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=505AFACC.1050802@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=rpm@xenomai.org \
    --cc=wolfgang.mauerer@siemens.com \
    --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.