Re: [PATCH 04/15] powerpc/powernv: opal-kmsg use flush fallback from console code

On Mon, 07 May 2018 20:36:39 +1000 Michael Ellerman wrote: > Nicholas Piggin writes: > > On Fri, 04 May 2018 15:16:37 +1000 > > Michael Ellerman wrote: > >> Nicholas Piggin writes: > >> > Use the more refined and tested event polling loop from opal_put_chars > >> > as the fallback console

Re: [PATCH 04/15] powerpc/powernv: opal-kmsg use flush fallback from console code

Nicholas Piggin writes: > On Fri, 04 May 2018 15:16:37 +1000 > Michael Ellerman wrote: >> Nicholas Piggin writes: >> > Use the more refined and tested event polling loop from opal_put_chars >> > as the fallback console flush in the opal-kmsg path. This loop is used >> > by the console driver tod

Re: [PATCH 04/15] powerpc/powernv: opal-kmsg use flush fallback from console code

On Fri, 04 May 2018 15:16:37 +1000 Michael Ellerman wrote: > Nicholas Piggin writes: > > > Use the more refined and tested event polling loop from opal_put_chars > > as the fallback console flush in the opal-kmsg path. This loop is used > > by the console driver today, whereas the opal-kmsg fal

Re: [PATCH 04/15] powerpc/powernv: opal-kmsg use flush fallback from console code

Nicholas Piggin writes: > Use the more refined and tested event polling loop from opal_put_chars > as the fallback console flush in the opal-kmsg path. This loop is used > by the console driver today, whereas the opal-kmsg fallback is not > likely to have been used for years. > > Use WARN_ONCE ra

[PATCH 04/15] powerpc/powernv: opal-kmsg use flush fallback from console code

Use the more refined and tested event polling loop from opal_put_chars as the fallback console flush in the opal-kmsg path. This loop is used by the console driver today, whereas the opal-kmsg fallback is not likely to have been used for years. Use WARN_ONCE rather than a printk when the fallback