aboutsummaryrefslogtreecommitdiff
path: root/include/mem-map.h
diff options
context:
space:
mode:
authorVasant Hegde <hegdevasant@linux.vnet.ibm.com>2019-05-28 11:17:27 +0530
committerStewart Smith <stewart@linux.ibm.com>2019-06-03 10:28:57 +1000
commit9cae036fafea468219892406a846639f2715854d (patch)
tree3340ac9059b0561b6b311941fdf558dc020c4d07 /include/mem-map.h
parenteb86b1484f5442cc2fc78b7c60ff504647318ca2 (diff)
downloadskiboot-9cae036fafea468219892406a846639f2715854d.zip
skiboot-9cae036fafea468219892406a846639f2715854d.tar.gz
skiboot-9cae036fafea468219892406a846639f2715854d.tar.bz2
opal-prd: Fix prd message size issue
If prd messages size is insufficient then read_prd_msg() call fails with below error. And caller is not reallocating sufficient buffer. Also its hard to guess the size. sample log: ----------- Mar 28 03:31:43 zz24p1 opal-prd: FW: error reading from firmware: alloc 32 rc -1: Invalid argument Mar 28 03:31:43 zz24p1 opal-prd: FW: error reading from firmware: alloc 32 rc -1: Invalid argument Mar 28 03:31:43 zz24p1 opal-prd: FW: error reading from firmware: alloc 32 rc -1: Invalid argument .... Lets use `opal-msg-size` device tree property to allocate memory for prd message. Cc: Skiboot Stable <skiboot-stable@lists.ozlabs.org> Signed-off-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com> Signed-off-by: Stewart Smith <stewart@linux.ibm.com>
Diffstat (limited to 'include/mem-map.h')
0 files changed, 0 insertions, 0 deletions