Re: [PATCH] powerpc: opal-msglog: Report size of memcons log

2017-01-25 Thread Joel Stanley
On Wed, Jan 25, 2017 at 1:33 PM, Michael Ellerman wrote: > Michael Ellerman writes: > >> Joel Stanley writes: >> >>> The OPAL memory console is reported to be size zero, as we do not >>> initialise the struct attr with any size information due to the size >>> being variable. This leads users to

Re: [PATCH] powerpc: opal-msglog: Report size of memcons log

2017-01-24 Thread Michael Ellerman
Michael Ellerman writes: > Joel Stanley writes: > >> The OPAL memory console is reported to be size zero, as we do not >> initialise the struct attr with any size information due to the size >> being variable. This leads users to think that the console is empty. > > Hmm OK. That is a general pro

Re: [PATCH] powerpc: opal-msglog: Report size of memcons log

2017-01-23 Thread Michael Ellerman
Joel Stanley writes: > The OPAL memory console is reported to be size zero, as we do not > initialise the struct attr with any size information due to the size > being variable. This leads users to think that the console is empty. Hmm OK. That is a general property of /proc and /sys files that a

[PATCH] powerpc: opal-msglog: Report size of memcons log

2017-01-12 Thread Joel Stanley
The OPAL memory console is reported to be size zero, as we do not initialise the struct attr with any size information due to the size being variable. This leads users to think that the console is empty. Instead report the maximum size. Signed-off-by: Joel Stanley --- arch/powerpc/platforms/pow