summaryrefslogtreecommitdiffstats
path: root/lib/iommu-helper.c
diff options
context:
space:
mode:
authorMartin Schwidefsky <schwidefsky@de.ibm.com>2017-10-12 13:24:48 +0200
committerMartin Schwidefsky <schwidefsky@de.ibm.com>2017-10-19 17:07:40 +0200
commit3037a52f9846b9d6e233274453f2d4117a14f31b (patch)
tree030694099f002e9c3dd222b8f905a1a871e96341 /lib/iommu-helper.c
parent6c81511ca1f52a0bbe921b2b98e34319a4ca59ed (diff)
downloadop-kernel-dev-3037a52f9846b9d6e233274453f2d4117a14f31b.zip
op-kernel-dev-3037a52f9846b9d6e233274453f2d4117a14f31b.tar.gz
s390/nmi: do register validation as early as possible
The validation of the CPU registers in the machine check handler is currently split into two parts. The first part is done at the start of the low level mcck_int_handler function, this includes the CPU timer register and the general purpose registers. The second part is done a bit later in s390_do_machine_check for all the other registers, including the control registers, floating pointer control, vector or floating pointer registers, the access registers, the guarded storage registers, the TOD programmable registers and the clock comparator. This is working fine to far but in theory a future extensions could cause the C code to use registers that are not validated yet. A better approach is to validate all CPU registers in "safe" assembler code before any C function is called. Reviewed-by: Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'lib/iommu-helper.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud