All of lore.kernel.org
 help / color / mirror / Atom feed
From: jamie@shareable.org (Jamie Lokier)
To: linux-arm-kernel@lists.infradead.org
Subject: [arm-gnu] Problems with pthread on ARM/PXA270
Date: Fri, 18 Sep 2009 13:48:48 +0100	[thread overview]
Message-ID: <20090918124848.GA1631@shareable.org> (raw)
In-Reply-To: <20090918075355.GA13044@pengutronix.de>

Uwe Kleine-K?nig wrote:
> On Thu, Sep 17, 2009 at 08:54:44AM +1000, James wrote:
> > Are you running with superuser privileges?  My manpage tells me that
> > SCHED_RR is only available if run with superuser privileges.
> Note that pthread_attr_setschedpolicy has a return value that tells you
> if the function was successful.

And that SCHED_RR has a time quantum returned by sched_rr_get_interval
which is not guaranteed to be small.  However, if it is a small time
and it's not switching that's a bug in either libc or the kernel.

Note that printf() does locking which may complicate things.  Try
opening separate outputs for each thread, or using write().

-- Jamie

  reply	other threads:[~2009-09-18 12:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16  7:26 Problems with pthread on ARM/PXA270 Juergen Schindele
2009-09-16 14:14 ` Eric Miao
2009-09-16 15:01   ` Juergen Schindele
2009-09-16 15:06     ` Eric Miao
2009-09-17  7:35       ` Juergen Schindele
2009-09-17 12:47         ` Beckwith, Stephen (Stephen)
2009-09-17 13:06           ` Juergen Schindele
2009-09-21 21:19           ` Beckwith, Stephen (Stephen)
2009-09-16 14:40 ` Daniel Jacobowitz
2009-09-18 10:06   ` Juergen Schindele
2009-09-18 14:10     ` Daniel Jacobowitz
2009-09-16 22:01 ` Jamie Lokier
2009-09-16 22:54 ` [arm-gnu] " James
2009-09-18  7:53   ` Uwe Kleine-König
2009-09-18 12:48     ` Jamie Lokier [this message]
2009-09-24  8:34 ` Juergen Schindele

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=20090918124848.GA1631@shareable.org \
    --to=jamie@shareable.org \
    --cc=linux-arm-kernel@lists.infradead.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.