From: Andrew Morton <akpm@linux-foundation.org>
To: Alexandre Bounine <alexandre.bounine@idt.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] rapidio: fix blocking wait for discovery ready
Date: Wed, 3 Oct 2012 15:20:01 -0700 [thread overview]
Message-ID: <20121003152001.665c9373.akpm@linux-foundation.org> (raw)
In-Reply-To: <1349291923-22860-2-git-send-email-alexandre.bounine@idt.com>
On Wed, 3 Oct 2012 15:18:39 -0400
Alexandre Bounine <alexandre.bounine@idt.com> wrote:
> Fix blocking wait loop in the RapidIO discovery routine to avoid warning
> dumps about stalled CPU on x86 platforms.
>
> ...
>
> + to_end = jiffies + CONFIG_RAPIDIO_DISC_TIMEOUT * HZ;
> + while (time_before(jiffies, to_end)) {
> + if (rio_enum_complete(mport))
> + goto enum_done;
> + schedule_timeout_uninterruptible(msecs_to_jiffies(10));
I think a simple msleep(10) would suffice here?
next prev parent reply other threads:[~2012-10-03 22:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 19:18 [PATCH 0/5] rapidio: patches to support multiple master ports Alexandre Bounine
2012-10-03 19:18 ` [PATCH 1/5] rapidio: fix blocking wait for discovery ready Alexandre Bounine
2012-10-03 22:20 ` Andrew Morton [this message]
2012-10-04 17:20 ` Bounine, Alexandre
2012-10-03 19:18 ` [PATCH 2/5] rapidio: use device lists handling on per-net basis Alexandre Bounine
2012-10-03 19:18 ` [PATCH 3/5] rapidio: run discovery as an asynchronous process Alexandre Bounine
2012-10-03 22:29 ` Andrew Morton
2012-10-04 19:08 ` Bounine, Alexandre
2012-10-03 19:18 ` [PATCH 4/5] rapidio/rionet: rework to support multiple RIO master ports Alexandre Bounine
2012-10-03 19:18 ` [PATCH 5/5] rapidio: add destination ID allocation mechanism Alexandre Bounine
2012-10-03 22:36 ` Andrew Morton
2012-10-04 20:39 ` Bounine, Alexandre
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=20121003152001.665c9373.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alexandre.bounine@idt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).