Thanks!! for review.
Sending out v2 with suggested changes.
On Thursday 23 February 2017 09:22 AM, Stewart Smith wrote:
Michael Ellerman writes:
Stewart Smith writes:
Vipin K Parashar writes:
On Monday 13 February 2017 06:13 AM, Michael Ellerman wrote:
Vipin K Parashar writes:
OPA
Michael Ellerman writes:
> Stewart Smith writes:
>
>> Vipin K Parashar writes:
>>> On Monday 13 February 2017 06:13 AM, Michael Ellerman wrote:
Vipin K Parashar writes:
> OPAL returns OPAL_WRONG_STATE for XSCOM operations
>
> done to read any core FIR which is sleeping, o
Stewart Smith writes:
> Vipin K Parashar writes:
>> On Monday 13 February 2017 06:13 AM, Michael Ellerman wrote:
>>> Vipin K Parashar writes:
>>>
OPAL returns OPAL_WRONG_STATE for XSCOM operations
done to read any core FIR which is sleeping, offline.
>>> OK.
>>>
>>> Do we know wh
Vipin K Parashar writes:
> On Monday 13 February 2017 06:13 AM, Michael Ellerman wrote:
>> Vipin K Parashar writes:
>>
>>> OPAL returns OPAL_WRONG_STATE for XSCOM operations
>>>
>>> done to read any core FIR which is sleeping, offline.
>> OK.
>>
>> Do we know why Linux is causing that to happen?
Hi Michael,
Thanks!! for review.
Answers to your questions as below:
On Monday 13 February 2017 06:13 AM, Michael Ellerman wrote:
Vipin K Parashar writes:
OPAL returns OPAL_WRONG_STATE for XSCOM operations
done to read any core FIR which is sleeping, offline.
OK.
Do we know why Linux is
Michael Ellerman writes:
> Vipin K Parashar writes:
>
>> OPAL returns OPAL_WRONG_STATE for XSCOM operations
>>
>> done to read any core FIR which is sleeping, offline.
>
> OK.
>
> Do we know why Linux is causing that to happen?
>
> It's also returned from many of the XIVE routines if we're in the
Vipin K Parashar writes:
> OPAL returns OPAL_WRONG_STATE for XSCOM operations
>
> done to read any core FIR which is sleeping, offline.
OK.
Do we know why Linux is causing that to happen?
It's also returned from many of the XIVE routines if we're in the wrong
xive mode, all of which would indi
OPAL returns OPAL_WRONG_STATE for XSCOM operations
done to read any core FIR which is sleeping, offline.
On Friday 27 January 2017 05:47 AM, Michael Ellerman wrote:
Vipin K Parashar writes:
Added check for OPAL_WRONG_STATE error code returned from OPAL.
Currently Linux flashes "unexpected e
Vipin K Parashar writes:
> Added check for OPAL_WRONG_STATE error code returned from OPAL.
> Currently Linux flashes "unexpected error" over console for this
> error. This will avoid throwing such message and return I/O error
> for such OPAL failures.
Why do we expect to get OPAL_WRONG_STATE ?
On Tuesday 20 December 2016 07:46 PM, Vipin K Parashar wrote:
Added check for OPAL_WRONG_STATE error code returned from OPAL.
Currently Linux flashes "unexpected error" over console for this
error. This will avoid throwing such message and return I/O error
for such OPAL failures.
Signed-off-by
Added check for OPAL_WRONG_STATE error code returned from OPAL.
Currently Linux flashes "unexpected error" over console for this
error. This will avoid throwing such message and return I/O error
for such OPAL failures.
Signed-off-by: Vipin K Parashar
---
arch/powerpc/platforms/powernv/opal.c | 7
11 matches
Mail list logo
