powerpc/secvar: Handle max object size in the consumer
authorRussell Currey <ruscur@russell.cc>
Fri, 10 Feb 2023 08:03:43 +0000 (19:03 +1100)
committerMichael Ellerman <mpe@ellerman.id.au>
Sun, 12 Feb 2023 11:12:37 +0000 (22:12 +1100)
commite02407944052554c1685e11e56175147d1ac56b6
tree6f3e3174d40b446a197687c1eb92792bfa01a43d
parentec2f40bd004b4b9142469282d4a6ce9afa22f9c0
powerpc/secvar: Handle max object size in the consumer

Currently the max object size is handled in the core secvar code with an
entirely OPAL-specific implementation, so create a new max_size() op and
move the existing implementation into the powernv platform.  Should be
no functional change.

Signed-off-by: Russell Currey <ruscur@russell.cc>
Signed-off-by: Andrew Donnellan <ajd@linux.ibm.com>
Reviewed-by: Stefan Berger <stefanb@linux.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20230210080401.345462-9-ajd@linux.ibm.com
arch/powerpc/include/asm/secvar.h
arch/powerpc/kernel/secvar-sysfs.c
arch/powerpc/platforms/powernv/opal-secvar.c