linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Armin Steinhoff <armin@steinhoff.de>
To: rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: Operation not permitted / pthread_setschedparam
Date: Tue, 30 Sep 2014 19:22:07 +0200	[thread overview]
Message-ID: <542AE6BF.6090500@steinhoff.de> (raw)
In-Reply-To: <542AA2E5.1050507@steinhoff.de>


Hi,

pthread_setschedparam seems to be broken in my PREEMPT_RT version !!
The pthread_attr_ interface is working ...

Any comments ??

cheers

--Armin

Armin Steinhoff schrieb:
> Harry,
>
> I'm running as root. The same code works w/o problem with the normal
> (non RT) kernel.
> "chrt -m" shows  1/99 for SCHED_FIFO. I did also add @root - rtprio 99
> to limits.conf ... no success, as expected. 
>
> --Armin
>
> Harry van Haaren schrieb:
>> On Tue, Sep 30, 2014 at 11:40 AM, Armin Steinhoff <armin@steinhoff.de> wrote:
>>> a "pthread_setschedparam" call of the code below terminates with an
>>> errno == 1  ... means "Operation not permitted"
>> At risk of asking the obvious: are you running as root, or does the
>> user running this code have RT priorities?
>>
>> User priorities controlled by /etc/security/limits.conf : you can set
>> a groups max-rtprio like so:
>> @audio          -       rtprio          65
>>
>>> KERNEL_EVENT_THREAD_PRIORITY is 55!
>>> How to solve that problem ?
>> Anything above 50 requrires changing limits.conf  or root IIRC.
>>
>> HTH, -Harry
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


  reply	other threads:[~2014-09-30 17:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 10:40 Operation not permitted / pthread_setschedparam Armin Steinhoff
2014-09-30 11:44 ` Harry van Haaren
2014-09-30 12:32   ` Armin Steinhoff
2014-09-30 17:22     ` Armin Steinhoff [this message]
2014-09-30 23:09 ` Thomas Gleixner
2014-10-01  7:27   ` Armin Steinhoff
2014-10-01  7:49     ` Patrik Lundquist
2014-10-02  8:02       ` Armin Steinhoff
2014-10-04 10:49         ` Carsten Emde
2014-10-04 12:36           ` Armin Steinhoff
2014-10-04 12:50             ` Armin Steinhoff
2014-10-04 23:56             ` Thomas Gleixner
2014-10-05 11:07               ` Armin Steinhoff
2014-10-05 11:47               ` Armin Steinhoff
2014-10-05 14:34               ` Armin Steinhoff
     [not found]               ` <54312C88.8060609@steinhoff.de>
2014-10-05 20:54                 ` Thomas Gleixner
2014-10-06  8:03                   ` Armin Steinhoff
2014-10-06 13:34                   ` Armin Steinhoff
2014-10-07  1:33                     ` Thomas Gleixner
2014-10-07  7:57                       ` Armin Steinhoff
2014-10-09  8:35                       ` Operation not permitted / pthread_setschedparam / EOD Armin Steinhoff
2014-10-09  9:41                         ` Pavel Vasilyev
2014-10-09 12:22                           ` Crowd Funding ? Armin Steinhoff
2014-10-09 21:59                             ` Richard Weinberger
2014-10-10 12:14                               ` Armin Steinhoff
2014-10-11 10:04                                 ` Armin Steinhoff
2014-10-05 10:13             ` Operation not permitted / pthread_setschedparam Armin Steinhoff

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=542AE6BF.6090500@steinhoff.de \
    --to=armin@steinhoff.de \
    --cc=linux-rt-users@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).