From: Russell Currey <ruscur@russell.cc>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] pseries/eeh: Handle RTAS delay requests in configure_bridge
Date: Wed, 23 Mar 2016 11:28:26 +1100 [thread overview]
Message-ID: <1458692906.5945.2.camel@russell.cc> (raw)
In-Reply-To: <1458606895-24620-1-git-send-email-ruscur@russell.cc>
On Tue, 2016-03-22 at 11:34 +1100, Russell Currey wrote:
> In the configure_pe and configure_bridge RTAS calls, the spec states
> that values of 9900-9905 can be returned, indicating that software
> should delay for 10^x (where x is the last digit, i.e. 990x)
> milliseconds and attempt the call again. Currently, the kernel doesn't
> know about this, and respecting it fixes some PCI failures when the
> hypervisor is busy.
>
> The delay is capped at 0.2 seconds.
>
> Signed-off-by: Russell Currey <ruscur@russell.cc>
Forgot to mention this patch should go to stable, 3.10+
next prev parent reply other threads:[~2016-03-23 0:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 0:34 [PATCH] pseries/eeh: Handle RTAS delay requests in configure_bridge Russell Currey
2016-03-23 0:28 ` Russell Currey [this message]
2016-03-23 0:38 ` Michael Ellerman
2016-03-23 2:52 ` Russell Currey
2016-03-23 10:39 ` Michael Ellerman
2016-03-23 23:56 ` Russell Currey
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=1458692906.5945.2.camel@russell.cc \
--to=ruscur@russell.cc \
--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).