forked from luck/tmp_suning_uos_patched
69c0e360f9
The CPACF code makes some assumptions about the availablity of hardware support. E.g. if the machine supports KM(AES-256) without chaining it is assumed that KMC(AES-256) with chaining is available as well. For the existing CPUs this is true but the architecturally correct way is to check each CPACF functions on its own. This is what the query function of each instructions is all about. Reviewed-by: Harald Freudenberger <freude@linux.vnet.ibm.com> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com> |
||
|---|---|---|
| .. | ||
| diag.c | ||
| gaccess.c | ||
| gaccess.h | ||
| guestdbg.c | ||
| intercept.c | ||
| interrupt.c | ||
| irq.h | ||
| Kconfig | ||
| kvm-s390.c | ||
| kvm-s390.h | ||
| Makefile | ||
| priv.c | ||
| sigp.c | ||
| sthyi.c | ||
| trace-s390.h | ||
| trace.h | ||
| vsie.c | ||