From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 4/9] powerpc/powernv: OPAL console standardise OPAL_BUSY loops
Date: Mon, 09 Apr 2018 15:53:33 +1000 [thread overview]
Message-ID: <1523253213.11062.7.camel@kernel.crashing.org> (raw)
In-Reply-To: <20180409052431.26405-5-npiggin@gmail.com>
On Mon, 2018-04-09 at 15:24 +1000, Nicholas Piggin wrote:
> Convert to using the standard delay poll/delay form.
>
> The console code:
>
> - Did not previously delay or sleep in its busy loop.
>
> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Does it help with anything ? We don't technically *have* to delay or
wait, I thought it would be good to try to hit the console as fast as
possible in that case...
Ben.
> ---
> arch/powerpc/platforms/powernv/opal.c | 38 ++++++++++++++++-----------
> 1 file changed, 23 insertions(+), 15 deletions(-)
>
> diff --git a/arch/powerpc/platforms/powernv/opal.c b/arch/powerpc/platforms/powernv/opal.c
> index 87d4c0aa7f64..473c8ce14a34 100644
> --- a/arch/powerpc/platforms/powernv/opal.c
> +++ b/arch/powerpc/platforms/powernv/opal.c
> @@ -378,33 +378,41 @@ int opal_put_chars(uint32_t vtermno, const char *data, int total_len)
> /* We still try to handle partial completions, though they
> * should no longer happen.
> */
> - rc = OPAL_BUSY;
> - while(total_len > 0 && (rc == OPAL_BUSY ||
> - rc == OPAL_BUSY_EVENT || rc == OPAL_SUCCESS)) {
> +
> + while (total_len > 0) {
> olen = cpu_to_be64(total_len);
> - rc = opal_console_write(vtermno, &olen, data);
> +
> + rc = OPAL_BUSY;
> + while (rc == OPAL_BUSY || rc == OPAL_BUSY_EVENT) {
> + rc = opal_console_write(vtermno, &olen, data);
> + if (rc == OPAL_BUSY_EVENT) {
> + mdelay(OPAL_BUSY_DELAY_MS);
> + opal_poll_events(NULL);
> + } else if (rc == OPAL_BUSY) {
> + mdelay(OPAL_BUSY_DELAY_MS);
> + }
> + }
> +
> len = be64_to_cpu(olen);
>
> /* Closed or other error drop */
> - if (rc != OPAL_SUCCESS && rc != OPAL_BUSY &&
> - rc != OPAL_BUSY_EVENT) {
> - written += total_len;
> + if (rc != OPAL_SUCCESS) {
> + written += total_len; /* drop remaining chars */
> break;
> }
> - if (rc == OPAL_SUCCESS) {
> - total_len -= len;
> - data += len;
> - written += len;
> - }
> +
> + total_len -= len;
> + data += len;
> + written += len;
> +
> /* This is a bit nasty but we need that for the console to
> * flush when there aren't any interrupts. We will clean
> * things a bit later to limit that to synchronous path
> * such as the kernel console and xmon/udbg
> */
> - do
> + do {
> opal_poll_events(&evt);
> - while(rc == OPAL_SUCCESS &&
> - (be64_to_cpu(evt) & OPAL_EVENT_CONSOLE_OUTPUT));
> + } while (be64_to_cpu(evt) & OPAL_EVENT_CONSOLE_OUTPUT);
> }
> spin_unlock_irqrestore(&opal_write_lock, flags);
> return written;
next prev parent reply other threads:[~2018-04-09 5:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 5:24 [PATCH v2 0/9] first step of standardising OPAL_BUSY handling Nicholas Piggin
2018-04-09 5:24 ` [PATCH v2 1/9] powerpc/powernv: define a standard delay for OPAL_BUSY type retry loops Nicholas Piggin
2018-04-09 5:24 ` [PATCH v2 2/9] powerpc/powernv: OPAL RTC driver standardise OPAL_BUSY loops Nicholas Piggin
2018-04-09 5:24 ` [PATCH v2 3/9] powerpc/powernv: opal_put_chars partial write fix Nicholas Piggin
2018-04-09 5:50 ` Benjamin Herrenschmidt
2018-04-09 5:24 ` [PATCH v2 4/9] powerpc/powernv: OPAL console standardise OPAL_BUSY loops Nicholas Piggin
2018-04-09 5:53 ` Benjamin Herrenschmidt [this message]
2018-04-09 6:13 ` Nicholas Piggin
2018-04-09 8:22 ` Benjamin Herrenschmidt
2018-04-09 5:24 ` [PATCH v2 5/9] powerpc/powernv: OPAL platform " Nicholas Piggin
2018-04-09 5:24 ` [PATCH v2 6/9] powerpc/powernv: OPAL NVRAM driver standardise OPAL_BUSY delays Nicholas Piggin
2018-04-09 5:24 ` [PATCH v2 7/9] powerpc/powernv: OPAL dump support " Nicholas Piggin
2018-04-09 5:24 ` [PATCH v2 8/9] powerpc/xive: " Nicholas Piggin
2018-04-09 5:24 ` [PATCH v2 9/9] powerpc/powernv: opal-kmsg standardise OPAL_BUSY handling Nicholas Piggin
2018-04-10 5:01 ` 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=1523253213.11062.7.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
/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).