From: Anton Blanchard <anton@samba.org>
To: John Rose <johnrose@austin.ibm.com>
Cc: Paul Mackerras <paulus@samba.org>, Nathan Lynch <ntl@pobox.com>,
External List <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] reorg RTAS delay code
Date: Sat, 10 Jun 2006 12:04:54 +1000 [thread overview]
Message-ID: <20060610020453.GF23891@krispykreme> (raw)
In-Reply-To: <1149543108.17307.6.camel@sinatra.austin.ibm.com>
Hi John,
> This patch attempts to handle RTAS "busy" return codes in a more simple
> and consistent manner. Typical callers of RTAS shouldn't have to
> manage wait times and delay calls.
>
> This patch also changes the kernel to use msleep() rather than udelay()
> when a runtime delay is necessary. This will avoid CPU soft lockups
> for extended delay conditions.
Looks like you missed one:
WARNING: ".rtas_extended_busy_delay_time" [arch/powerpc/platforms/pseries/scanlog.ko] undefined!
Anton
next prev parent reply other threads:[~2006-06-10 2:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 19:32 [PATCH] use msleep() for RTAS delays John Rose
2006-06-01 5:31 ` Benjamin Herrenschmidt
2006-06-01 5:39 ` Paul Mackerras
2006-06-01 18:09 ` Arnd Bergmann
2006-06-01 15:55 ` John Rose
2006-06-01 22:25 ` John Rose
2006-06-02 20:30 ` [PATCH] reorg RTAS delay code John Rose
2006-06-02 21:33 ` Nathan Lynch
2006-06-05 21:31 ` John Rose
2006-06-05 21:54 ` Nathan Lynch
2006-06-10 2:04 ` Anton Blanchard [this message]
2006-06-10 2:08 ` Anton Blanchard
2006-06-12 16:18 ` John Rose
[not found] ` <17553.4390.79327.634945@cargo.ozlabs.ibm.com>
2006-06-15 22:32 ` [PATCH] powerpc: RTAS delay, fix module build breaks John Rose
2006-07-13 18:20 ` [PATCH] reorg RTAS delay code Nathan Lynch
2006-07-25 4:39 ` Haren Myneni
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=20060610020453.GF23891@krispykreme \
--to=anton@samba.org \
--cc=johnrose@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.com \
--cc=paulus@samba.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).