summaryrefslogtreecommitdiff
path: root/net/x25
diff options
context:
space:
mode:
authorMartin Schwidefsky <schwidefsky@de.ibm.com>2016-08-18 13:59:46 +0300
committerMartin Schwidefsky <schwidefsky@de.ibm.com>2016-08-29 12:05:09 +0300
commit69c0e360f990c2dc737681f40a361195066cef02 (patch)
treee5e5ff1ff6f09e21b28752b948283589803d81eb /net/x25
parentd863d5945f2be0abfcd9d36b1a7c605f3eaef517 (diff)
downloadlinux-69c0e360f990c2dc737681f40a361195066cef02.tar.xz
s390/crypto: cpacf function detection
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>
Diffstat (limited to 'net/x25')
0 files changed, 0 insertions, 0 deletions