2017-11-15 01:38:01 +08:00
|
|
|
// SPDX-License-Identifier: GPL-2.0+
|
2006-09-20 21:58:25 +08:00
|
|
|
/*
|
2012-08-28 22:41:50 +08:00
|
|
|
* Copyright IBM Corp. 2006, 2012
|
2006-09-20 21:58:25 +08:00
|
|
|
* Author(s): Cornelia Huck <cornelia.huck@de.ibm.com>
|
|
|
|
* Martin Schwidefsky <schwidefsky@de.ibm.com>
|
|
|
|
* Ralph Wuerthner <rwuerthn@de.ibm.com>
|
2008-12-25 20:38:41 +08:00
|
|
|
* Felix Beck <felix.beck@de.ibm.com>
|
2011-07-24 16:48:25 +08:00
|
|
|
* Holger Dengler <hd@linux.vnet.ibm.com>
|
2006-09-20 21:58:25 +08:00
|
|
|
*
|
|
|
|
* Adjunct processor bus.
|
|
|
|
*/
|
|
|
|
|
2008-12-25 20:39:46 +08:00
|
|
|
#define KMSG_COMPONENT "ap"
|
|
|
|
#define pr_fmt(fmt) KMSG_COMPONENT ": " fmt
|
|
|
|
|
2011-01-05 19:47:38 +08:00
|
|
|
#include <linux/kernel_stat.h>
|
2017-02-09 22:48:10 +08:00
|
|
|
#include <linux/moduleparam.h>
|
2006-09-20 21:58:25 +08:00
|
|
|
#include <linux/init.h>
|
|
|
|
#include <linux/delay.h>
|
|
|
|
#include <linux/err.h>
|
|
|
|
#include <linux/interrupt.h>
|
|
|
|
#include <linux/workqueue.h>
|
include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
percpu.h is included by sched.h and module.h and thus ends up being
included when building most .c files. percpu.h includes slab.h which
in turn includes gfp.h making everything defined by the two files
universally available and complicating inclusion dependencies.
percpu.h -> slab.h dependency is about to be removed. Prepare for
this change by updating users of gfp and slab facilities include those
headers directly instead of assuming availability. As this conversion
needs to touch large number of source files, the following script is
used as the basis of conversion.
http://userweb.kernel.org/~tj/misc/slabh-sweep.py
The script does the followings.
* Scan files for gfp and slab usages and update includes such that
only the necessary includes are there. ie. if only gfp is used,
gfp.h, if slab is used, slab.h.
* When the script inserts a new include, it looks at the include
blocks and try to put the new include such that its order conforms
to its surrounding. It's put in the include block which contains
core kernel includes, in the same order that the rest are ordered -
alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
doesn't seem to be any matching order.
* If the script can't find a place to put a new include (mostly
because the file doesn't have fitting include block), it prints out
an error message indicating which .h file needs to be added to the
file.
The conversion was done in the following steps.
1. The initial automatic conversion of all .c files updated slightly
over 4000 files, deleting around 700 includes and adding ~480 gfp.h
and ~3000 slab.h inclusions. The script emitted errors for ~400
files.
2. Each error was manually checked. Some didn't need the inclusion,
some needed manual addition while adding it to implementation .h or
embedding .c file was more appropriate for others. This step added
inclusions to around 150 files.
3. The script was run again and the output was compared to the edits
from #2 to make sure no file was left behind.
4. Several build tests were done and a couple of problems were fixed.
e.g. lib/decompress_*.c used malloc/free() wrappers around slab
APIs requiring slab.h to be added manually.
5. The script was run on all .h files but without automatically
editing them as sprinkling gfp.h and slab.h inclusions around .h
files could easily lead to inclusion dependency hell. Most gfp.h
inclusion directives were ignored as stuff from gfp.h was usually
wildly available and often used in preprocessor macros. Each
slab.h inclusion directive was examined and added manually as
necessary.
6. percpu.h was updated not to include slab.h.
7. Build test were done on the following configurations and failures
were fixed. CONFIG_GCOV_KERNEL was turned off for all tests (as my
distributed build env didn't work with gcov compiles) and a few
more options had to be turned off depending on archs to make things
build (like ipr on powerpc/64 which failed due to missing writeq).
* x86 and x86_64 UP and SMP allmodconfig and a custom test config.
* powerpc and powerpc64 SMP allmodconfig
* sparc and sparc64 SMP allmodconfig
* ia64 SMP allmodconfig
* s390 SMP allmodconfig
* alpha SMP allmodconfig
* um on x86_64 SMP allmodconfig
8. percpu.h modifications were reverted so that it could be applied as
a separate patch and serve as bisection point.
Given the fact that I had only a couple of failures from tests on step
6, I'm fairly confident about the coverage of this conversion patch.
If there is a breakage, it's likely to be something in one of the arch
headers which should be easily discoverable easily on most builds of
the specific arch.
Signed-off-by: Tejun Heo <tj@kernel.org>
Guess-its-ok-by: Christoph Lameter <cl@linux-foundation.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
2010-03-24 16:04:11 +08:00
|
|
|
#include <linux/slab.h>
|
2006-09-20 21:58:25 +08:00
|
|
|
#include <linux/notifier.h>
|
|
|
|
#include <linux/kthread.h>
|
|
|
|
#include <linux/mutex.h>
|
2015-07-17 19:43:18 +08:00
|
|
|
#include <linux/suspend.h>
|
2008-12-25 20:38:41 +08:00
|
|
|
#include <asm/airq.h>
|
2011-07-27 07:09:06 +08:00
|
|
|
#include <linux/atomic.h>
|
2008-12-25 20:38:41 +08:00
|
|
|
#include <asm/isc.h>
|
2008-07-14 15:59:08 +08:00
|
|
|
#include <linux/hrtimer.h>
|
|
|
|
#include <linux/ktime.h>
|
2012-03-29 01:30:02 +08:00
|
|
|
#include <asm/facility.h>
|
2014-11-21 09:05:53 +08:00
|
|
|
#include <linux/crypto.h>
|
2016-08-25 17:16:03 +08:00
|
|
|
#include <linux/mod_devicetable.h>
|
2016-11-24 13:45:21 +08:00
|
|
|
#include <linux/debugfs.h>
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
#include <linux/ctype.h>
|
2006-09-20 21:58:25 +08:00
|
|
|
|
|
|
|
#include "ap_bus.h"
|
2016-11-24 13:45:21 +08:00
|
|
|
#include "ap_debug.h"
|
2006-09-20 21:58:25 +08:00
|
|
|
|
2008-04-17 13:46:28 +08:00
|
|
|
/*
|
2017-02-09 22:48:10 +08:00
|
|
|
* Module parameters; note though this file itself isn't modular.
|
2006-09-20 21:58:25 +08:00
|
|
|
*/
|
|
|
|
int ap_domain_index = -1; /* Adjunct Processor Domain Index */
|
2016-08-25 17:11:30 +08:00
|
|
|
static DEFINE_SPINLOCK(ap_domain_lock);
|
2018-08-17 18:36:01 +08:00
|
|
|
module_param_named(domain, ap_domain_index, int, 0440);
|
2006-09-20 21:58:25 +08:00
|
|
|
MODULE_PARM_DESC(domain, "domain index for ap devices");
|
|
|
|
EXPORT_SYMBOL(ap_domain_index);
|
|
|
|
|
2018-08-17 18:36:01 +08:00
|
|
|
static int ap_thread_flag;
|
|
|
|
module_param_named(poll_thread, ap_thread_flag, int, 0440);
|
2008-02-10 01:24:30 +08:00
|
|
|
MODULE_PARM_DESC(poll_thread, "Turn on/off poll thread, default is 0 (off).");
|
2006-09-20 21:58:25 +08:00
|
|
|
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
static char *apm_str;
|
|
|
|
module_param_named(apmask, apm_str, charp, 0440);
|
|
|
|
MODULE_PARM_DESC(apmask, "AP bus adapter mask.");
|
|
|
|
|
|
|
|
static char *aqm_str;
|
|
|
|
module_param_named(aqmask, aqm_str, charp, 0440);
|
|
|
|
MODULE_PARM_DESC(aqmask, "AP bus domain mask.");
|
|
|
|
|
2016-08-25 17:16:03 +08:00
|
|
|
static struct device *ap_root_device;
|
|
|
|
|
|
|
|
DEFINE_SPINLOCK(ap_list_lock);
|
|
|
|
LIST_HEAD(ap_card_list);
|
|
|
|
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
/* Default permissions (card and domain masking) */
|
|
|
|
static struct ap_perms {
|
|
|
|
DECLARE_BITMAP(apm, AP_DEVICES);
|
|
|
|
DECLARE_BITMAP(aqm, AP_DOMAINS);
|
|
|
|
} ap_perms;
|
|
|
|
static DEFINE_MUTEX(ap_perms_mutex);
|
|
|
|
|
2012-08-28 22:41:50 +08:00
|
|
|
static struct ap_config_info *ap_configuration;
|
s390/zcrypt: Fix kernel crash on systems without AP bus support
On systems without AP bus (e.g. KVM) the kernel crashes during init
calls when zcrypt is built-in:
kernel BUG at drivers/base/driver.c:153!
illegal operation: 0001 ilc:1 [#1] SMP
Modules linked in:
CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.2.0+ #221
task: 0000000010a40000 ti: 0000000010a48000 task.ti:0000000010a48000
Krnl PSW : 0704c00180000000 0000000000592bd6(driver_register+0x106/0x140)
R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 EA:3
0000000000000012 0000000000000000 0000000000c45328 0000000000c44e30
00000000009ef63c 000000000067f598 0000000000cf3c58 0000000000000000
000000000000007b 0000000000cb1030 0000000000000002 0000000000000000
0000000000ca8580 0000000010306700 00000000001001d8 0000000010a4bd88
Krnl Code: 0000000000592bc6: f0b00004ebcf srp 4(12,%r0),3023(%r14),0
0000000000592bcc: f0a0000407f4 srp 4(11,%r0),2036,0
#0000000000592bd2: a7f40001 brc 15,592bd4
>0000000000592bd6: e330d0000004 lg %r3,0(%r13)
0000000000592bdc: c0200021edfd larl %r2,9d07d6
0000000000592be2: c0e500126d8f brasl %r14,7e0700
0000000000592be8: e330d0080004 lg %r3,8(%r13)
0000000000592bee: a7f4ffab brc 15,592b44
Call Trace:
([<00000000001001c8>] do_one_initcall+0x90/0x1d0)
[<0000000000c6dd34>] kernel_init_freeable+0x1e4/0x2a0
[<00000000007db53a>] kernel_init+0x2a/0x120
[<00000000007e8ece>] kernel_thread_starter+0x6/0xc
[<00000000007e8ec8>] kernel_thread_starter+0x0/0xc
Last Breaking-Event-Address:
[<0000000000592bd2>] driver_register+0x102/0x140
When zcrypt is built as a module, the module loader ensures that the
driver modules cannot be loaded if the AP bus module returns an error
during initialisation. But if zcrypt and the driver are built-in, the
driver is getting initialised even if the AP bus initialisation
failed. The driver invokes ap_driver_register() during initialisation,
which then causes operations on uninitialised data structures to be
performed.
Explicitly protect ap_driver_register() by introducing an
"initialised" flag that gets set iff the AP bus initialisation was
successful. When the AP bus initialisation failed,
ap_driver_register() will error out with -ENODEV, causing the driver
initialisation to fail as well.
Test results:
1. Inside KVM (no AP bus), zcrypt built-in
Boots. /sys/bus/ap not present (expected).
2. Inside KVM (no AP bus), zcrypt as module
Boots. Loading zcrypt_cex4 fails because loading ap_bus fails
(expected).
3. On LPAR with CEX5, zcrypt built-in
Boots. /sys/bus/ap/devices/card* present but .../card*/type missing
(i.e. zcrypt_device_register() fails, unrelated issue).
4. On LPAR with CEX5, zcrypt as module
Boots. Loading zcrypt_cex4 successful,
/sys/bus/ap/devices/card*/type present. No further testing
(user-space functionality) was done.
Signed-off-by: Sascha Silbe <silbe@linux.vnet.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2015-10-28 01:29:52 +08:00
|
|
|
static bool initialised;
|
2006-09-20 21:58:25 +08:00
|
|
|
|
2016-11-24 13:45:21 +08:00
|
|
|
/*
|
|
|
|
* AP bus related debug feature things.
|
|
|
|
*/
|
|
|
|
debug_info_t *ap_dbf_info;
|
|
|
|
|
2008-04-17 13:46:28 +08:00
|
|
|
/*
|
2015-07-27 18:47:40 +08:00
|
|
|
* Workqueue timer for bus rescan.
|
2006-09-20 21:58:25 +08:00
|
|
|
*/
|
|
|
|
static struct timer_list ap_config_timer;
|
|
|
|
static int ap_config_time = AP_CONFIG_TIME;
|
2015-09-14 23:01:23 +08:00
|
|
|
static void ap_scan_bus(struct work_struct *);
|
2015-07-27 18:47:40 +08:00
|
|
|
static DECLARE_WORK(ap_scan_work, ap_scan_bus);
|
2006-09-20 21:58:25 +08:00
|
|
|
|
2008-04-17 13:46:28 +08:00
|
|
|
/*
|
2008-12-25 20:38:41 +08:00
|
|
|
* Tasklet & timer for AP request polling and interrupts
|
2006-09-20 21:58:25 +08:00
|
|
|
*/
|
2015-09-14 23:01:23 +08:00
|
|
|
static void ap_tasklet_fn(unsigned long);
|
|
|
|
static DECLARE_TASKLET(ap_tasklet, ap_tasklet_fn, 0);
|
2006-09-20 21:58:25 +08:00
|
|
|
static DECLARE_WAIT_QUEUE_HEAD(ap_poll_wait);
|
2018-08-17 18:36:01 +08:00
|
|
|
static struct task_struct *ap_poll_kthread;
|
2006-09-20 21:58:25 +08:00
|
|
|
static DEFINE_MUTEX(ap_poll_thread_mutex);
|
2009-12-07 19:52:00 +08:00
|
|
|
static DEFINE_SPINLOCK(ap_poll_timer_lock);
|
2008-07-14 15:59:08 +08:00
|
|
|
static struct hrtimer ap_poll_timer;
|
2018-08-17 18:36:01 +08:00
|
|
|
/*
|
|
|
|
* In LPAR poll with 4kHz frequency. Poll every 250000 nanoseconds.
|
|
|
|
* If z/VM change to 1500000 nanoseconds to adjust to z/VM polling.
|
|
|
|
*/
|
2008-07-14 15:59:08 +08:00
|
|
|
static unsigned long long poll_timeout = 250000;
|
2006-09-20 21:58:25 +08:00
|
|
|
|
2009-06-22 18:08:16 +08:00
|
|
|
/* Suspend flag */
|
|
|
|
static int ap_suspend_flag;
|
2015-06-26 22:55:35 +08:00
|
|
|
/* Maximum domain id */
|
|
|
|
static int ap_max_domain_id;
|
2018-08-17 18:36:01 +08:00
|
|
|
/*
|
|
|
|
* Flag to check if domain was set through module parameter domain=. This is
|
2009-09-23 04:58:51 +08:00
|
|
|
* important when supsend and resume is done in a z/VM environment where the
|
2018-08-17 18:36:01 +08:00
|
|
|
* domain might change.
|
|
|
|
*/
|
|
|
|
static int user_set_domain;
|
2009-06-22 18:08:16 +08:00
|
|
|
static struct bus_type ap_bus_type;
|
|
|
|
|
2013-06-24 16:30:41 +08:00
|
|
|
/* Adapter interrupt definitions */
|
2015-09-14 23:01:23 +08:00
|
|
|
static void ap_interrupt_handler(struct airq_struct *airq);
|
|
|
|
|
2013-06-24 16:30:41 +08:00
|
|
|
static int ap_airq_flag;
|
|
|
|
|
|
|
|
static struct airq_struct ap_airq = {
|
|
|
|
.handler = ap_interrupt_handler,
|
|
|
|
.isc = AP_ISC,
|
|
|
|
};
|
|
|
|
|
2008-12-25 20:38:41 +08:00
|
|
|
/**
|
|
|
|
* ap_using_interrupts() - Returns non-zero if interrupt support is
|
|
|
|
* available.
|
|
|
|
*/
|
|
|
|
static inline int ap_using_interrupts(void)
|
|
|
|
{
|
2013-06-24 16:30:41 +08:00
|
|
|
return ap_airq_flag;
|
2008-12-25 20:38:41 +08:00
|
|
|
}
|
|
|
|
|
2016-08-25 17:16:03 +08:00
|
|
|
/**
|
|
|
|
* ap_airq_ptr() - Get the address of the adapter interrupt indicator
|
|
|
|
*
|
|
|
|
* Returns the address of the local-summary-indicator of the adapter
|
|
|
|
* interrupt handler for AP, or NULL if adapter interrupts are not
|
|
|
|
* available.
|
|
|
|
*/
|
|
|
|
void *ap_airq_ptr(void)
|
|
|
|
{
|
|
|
|
if (ap_using_interrupts())
|
|
|
|
return ap_airq.lsi_ptr;
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
2008-12-25 20:38:41 +08:00
|
|
|
/**
|
|
|
|
* ap_interrupts_available(): Test if AP interrupts are available.
|
|
|
|
*
|
|
|
|
* Returns 1 if AP interrupts are available.
|
|
|
|
*/
|
|
|
|
static int ap_interrupts_available(void)
|
|
|
|
{
|
2015-02-14 18:23:21 +08:00
|
|
|
return test_facility(65);
|
2008-12-25 20:38:41 +08:00
|
|
|
}
|
|
|
|
|
2012-08-28 22:41:50 +08:00
|
|
|
/**
|
|
|
|
* ap_configuration_available(): Test if AP configuration
|
|
|
|
* information is available.
|
|
|
|
*
|
|
|
|
* Returns 1 if AP configuration information is available.
|
|
|
|
*/
|
|
|
|
static int ap_configuration_available(void)
|
|
|
|
{
|
2015-02-14 18:23:21 +08:00
|
|
|
return test_facility(12);
|
2012-08-28 22:41:50 +08:00
|
|
|
}
|
|
|
|
|
2016-11-08 14:09:13 +08:00
|
|
|
/**
|
|
|
|
* ap_apft_available(): Test if AP facilities test (APFT)
|
|
|
|
* facility is available.
|
|
|
|
*
|
|
|
|
* Returns 1 if APFT is is available.
|
|
|
|
*/
|
|
|
|
static int ap_apft_available(void)
|
|
|
|
{
|
|
|
|
return test_facility(15);
|
|
|
|
}
|
|
|
|
|
2017-10-16 18:28:35 +08:00
|
|
|
/*
|
|
|
|
* ap_qact_available(): Test if the PQAP(QACT) subfunction is available.
|
|
|
|
*
|
|
|
|
* Returns 1 if the QACT subfunction is available.
|
|
|
|
*/
|
|
|
|
static inline int ap_qact_available(void)
|
|
|
|
{
|
|
|
|
if (ap_configuration)
|
|
|
|
return ap_configuration->qact;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2016-11-08 18:54:28 +08:00
|
|
|
/*
|
|
|
|
* ap_query_configuration(): Fetch cryptographic config info
|
|
|
|
*
|
|
|
|
* Returns the ap configuration info fetched via PQAP(QCI).
|
|
|
|
* On success 0 is returned, on failure a negative errno
|
|
|
|
* is returned, e.g. if the PQAP(QCI) instruction is not
|
|
|
|
* available, the return value will be -EOPNOTSUPP.
|
|
|
|
*/
|
2018-06-12 21:42:36 +08:00
|
|
|
static inline int ap_query_configuration(struct ap_config_info *info)
|
2016-06-20 20:00:27 +08:00
|
|
|
{
|
2016-11-08 18:54:28 +08:00
|
|
|
if (!ap_configuration_available())
|
2016-06-20 20:00:27 +08:00
|
|
|
return -EOPNOTSUPP;
|
2016-11-08 18:54:28 +08:00
|
|
|
if (!info)
|
|
|
|
return -EINVAL;
|
|
|
|
return ap_qci(info);
|
2016-06-20 20:00:27 +08:00
|
|
|
}
|
2016-11-08 18:54:28 +08:00
|
|
|
EXPORT_SYMBOL(ap_query_configuration);
|
2016-06-20 20:00:27 +08:00
|
|
|
|
2015-06-26 22:55:35 +08:00
|
|
|
/**
|
|
|
|
* ap_init_configuration(): Allocate and query configuration array.
|
|
|
|
*/
|
|
|
|
static void ap_init_configuration(void)
|
|
|
|
{
|
|
|
|
if (!ap_configuration_available())
|
|
|
|
return;
|
|
|
|
|
|
|
|
ap_configuration = kzalloc(sizeof(*ap_configuration), GFP_KERNEL);
|
|
|
|
if (!ap_configuration)
|
|
|
|
return;
|
2016-11-08 18:54:28 +08:00
|
|
|
if (ap_query_configuration(ap_configuration) != 0) {
|
2015-06-26 22:55:35 +08:00
|
|
|
kfree(ap_configuration);
|
|
|
|
ap_configuration = NULL;
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* ap_test_config(): helper function to extract the nrth bit
|
|
|
|
* within the unsigned int array field.
|
|
|
|
*/
|
|
|
|
static inline int ap_test_config(unsigned int *field, unsigned int nr)
|
|
|
|
{
|
|
|
|
return ap_test_bit((field + (nr >> 5)), (nr & 0x1f));
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* ap_test_config_card_id(): Test, whether an AP card ID is configured.
|
|
|
|
* @id AP card ID
|
|
|
|
*
|
|
|
|
* Returns 0 if the card is not configured
|
|
|
|
* 1 if the card is configured or
|
|
|
|
* if the configuration information is not available
|
|
|
|
*/
|
|
|
|
static inline int ap_test_config_card_id(unsigned int id)
|
|
|
|
{
|
|
|
|
if (!ap_configuration) /* QCI not supported */
|
|
|
|
return 1;
|
|
|
|
return ap_test_config(ap_configuration->apm, id);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* ap_test_config_domain(): Test, whether an AP usage domain is configured.
|
|
|
|
* @domain AP usage domain ID
|
|
|
|
*
|
|
|
|
* Returns 0 if the usage domain is not configured
|
|
|
|
* 1 if the usage domain is configured or
|
|
|
|
* if the configuration information is not available
|
|
|
|
*/
|
|
|
|
static inline int ap_test_config_domain(unsigned int domain)
|
|
|
|
{
|
|
|
|
if (!ap_configuration) /* QCI not supported */
|
|
|
|
return domain < 16;
|
|
|
|
return ap_test_config(ap_configuration->aqm, domain);
|
|
|
|
}
|
|
|
|
|
2006-09-20 21:58:25 +08:00
|
|
|
/**
|
2008-04-17 13:46:28 +08:00
|
|
|
* ap_query_queue(): Check if an AP queue is available.
|
|
|
|
* @qid: The AP queue number
|
|
|
|
* @queue_depth: Pointer to queue depth value
|
|
|
|
* @device_type: Pointer to device type value
|
2015-06-26 21:40:41 +08:00
|
|
|
* @facilities: Pointer to facility indicator
|
2006-09-20 21:58:25 +08:00
|
|
|
*/
|
2015-06-26 21:40:41 +08:00
|
|
|
static int ap_query_queue(ap_qid_t qid, int *queue_depth, int *device_type,
|
|
|
|
unsigned int *facilities)
|
2006-09-20 21:58:25 +08:00
|
|
|
{
|
|
|
|
struct ap_queue_status status;
|
2015-06-26 21:40:41 +08:00
|
|
|
unsigned long info;
|
2015-06-26 22:55:35 +08:00
|
|
|
int nd;
|
|
|
|
|
2016-08-25 17:16:03 +08:00
|
|
|
if (!ap_test_config_card_id(AP_QID_CARD(qid)))
|
2015-06-26 22:55:35 +08:00
|
|
|
return -ENODEV;
|
2006-09-20 21:58:25 +08:00
|
|
|
|
2016-11-08 14:09:13 +08:00
|
|
|
status = ap_test_queue(qid, ap_apft_available(), &info);
|
2015-06-17 22:19:15 +08:00
|
|
|
switch (status.response_code) {
|
|
|
|
case AP_RESPONSE_NORMAL:
|
2015-06-26 21:40:41 +08:00
|
|
|
*queue_depth = (int)(info & 0xff);
|
|
|
|
*device_type = (int)((info >> 24) & 0xff);
|
|
|
|
*facilities = (unsigned int)(info >> 32);
|
2015-06-26 22:55:35 +08:00
|
|
|
/* Update maximum domain id */
|
|
|
|
nd = (info >> 16) & 0xff;
|
2016-11-02 17:23:24 +08:00
|
|
|
/* if N bit is available, z13 and newer */
|
2015-06-26 22:55:35 +08:00
|
|
|
if ((info & (1UL << 57)) && nd > 0)
|
|
|
|
ap_max_domain_id = nd;
|
2016-11-02 17:23:24 +08:00
|
|
|
else /* older machine types */
|
|
|
|
ap_max_domain_id = 15;
|
2016-10-27 14:57:39 +08:00
|
|
|
switch (*device_type) {
|
|
|
|
/* For CEX2 and CEX3 the available functions
|
|
|
|
* are not refrected by the facilities bits.
|
|
|
|
* Instead it is coded into the type. So here
|
|
|
|
* modify the function bits based on the type.
|
|
|
|
*/
|
|
|
|
case AP_DEVICE_TYPE_CEX2A:
|
|
|
|
case AP_DEVICE_TYPE_CEX3A:
|
|
|
|
*facilities |= 0x08000000;
|
|
|
|
break;
|
|
|
|
case AP_DEVICE_TYPE_CEX2C:
|
|
|
|
case AP_DEVICE_TYPE_CEX3C:
|
|
|
|
*facilities |= 0x10000000;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
break;
|
|
|
|
}
|
2015-06-17 22:19:15 +08:00
|
|
|
return 0;
|
|
|
|
case AP_RESPONSE_Q_NOT_AVAIL:
|
|
|
|
case AP_RESPONSE_DECONFIGURED:
|
|
|
|
case AP_RESPONSE_CHECKSTOPPED:
|
|
|
|
case AP_RESPONSE_INVALID_ADDRESS:
|
|
|
|
return -ENODEV;
|
|
|
|
case AP_RESPONSE_RESET_IN_PROGRESS:
|
|
|
|
case AP_RESPONSE_OTHERWISE_CHANGED:
|
|
|
|
case AP_RESPONSE_BUSY:
|
|
|
|
return -EBUSY;
|
|
|
|
default:
|
|
|
|
BUG();
|
2006-09-20 21:58:25 +08:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2016-08-25 17:16:03 +08:00
|
|
|
void ap_wait(enum ap_wait wait)
|
2015-09-14 23:01:23 +08:00
|
|
|
{
|
|
|
|
ktime_t hr_time;
|
|
|
|
|
|
|
|
switch (wait) {
|
|
|
|
case AP_WAIT_AGAIN:
|
|
|
|
case AP_WAIT_INTERRUPT:
|
|
|
|
if (ap_using_interrupts())
|
|
|
|
break;
|
|
|
|
if (ap_poll_kthread) {
|
|
|
|
wake_up(&ap_poll_wait);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
/* Fall through */
|
|
|
|
case AP_WAIT_TIMEOUT:
|
|
|
|
spin_lock_bh(&ap_poll_timer_lock);
|
|
|
|
if (!hrtimer_is_queued(&ap_poll_timer)) {
|
2016-12-25 19:30:41 +08:00
|
|
|
hr_time = poll_timeout;
|
2015-09-14 23:01:23 +08:00
|
|
|
hrtimer_forward_now(&ap_poll_timer, hr_time);
|
|
|
|
hrtimer_restart(&ap_poll_timer);
|
|
|
|
}
|
|
|
|
spin_unlock_bh(&ap_poll_timer_lock);
|
|
|
|
break;
|
|
|
|
case AP_WAIT_NONE:
|
|
|
|
default:
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ap_request_timeout(): Handling of request timeouts
|
2017-10-25 18:27:37 +08:00
|
|
|
* @t: timer making this callback
|
2015-09-14 23:01:23 +08:00
|
|
|
*
|
|
|
|
* Handles request timeouts.
|
|
|
|
*/
|
2017-10-25 18:27:37 +08:00
|
|
|
void ap_request_timeout(struct timer_list *t)
|
2015-09-14 23:01:23 +08:00
|
|
|
{
|
2017-10-25 18:27:37 +08:00
|
|
|
struct ap_queue *aq = from_timer(aq, t, timeout);
|
2015-09-14 23:01:23 +08:00
|
|
|
|
|
|
|
if (ap_suspend_flag)
|
|
|
|
return;
|
2016-08-25 17:16:03 +08:00
|
|
|
spin_lock_bh(&aq->lock);
|
|
|
|
ap_wait(ap_sm_event(aq, AP_EVENT_TIMEOUT));
|
|
|
|
spin_unlock_bh(&aq->lock);
|
2015-09-14 23:01:23 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ap_poll_timeout(): AP receive polling for finished AP requests.
|
|
|
|
* @unused: Unused pointer.
|
|
|
|
*
|
|
|
|
* Schedules the AP tasklet using a high resolution timer.
|
|
|
|
*/
|
|
|
|
static enum hrtimer_restart ap_poll_timeout(struct hrtimer *unused)
|
|
|
|
{
|
|
|
|
if (!ap_suspend_flag)
|
|
|
|
tasklet_schedule(&ap_tasklet);
|
|
|
|
return HRTIMER_NORESTART;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ap_interrupt_handler() - Schedule ap_tasklet on interrupt
|
|
|
|
* @airq: pointer to adapter interrupt descriptor
|
|
|
|
*/
|
|
|
|
static void ap_interrupt_handler(struct airq_struct *airq)
|
|
|
|
{
|
|
|
|
inc_irq_stat(IRQIO_APB);
|
|
|
|
if (!ap_suspend_flag)
|
|
|
|
tasklet_schedule(&ap_tasklet);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ap_tasklet_fn(): Tasklet to poll all AP devices.
|
|
|
|
* @dummy: Unused variable
|
|
|
|
*
|
|
|
|
* Poll all AP devices on the bus.
|
|
|
|
*/
|
|
|
|
static void ap_tasklet_fn(unsigned long dummy)
|
|
|
|
{
|
2016-08-25 17:16:03 +08:00
|
|
|
struct ap_card *ac;
|
|
|
|
struct ap_queue *aq;
|
2015-09-14 23:01:23 +08:00
|
|
|
enum ap_wait wait = AP_WAIT_NONE;
|
|
|
|
|
|
|
|
/* Reset the indicator if interrupts are used. Thus new interrupts can
|
|
|
|
* be received. Doing it in the beginning of the tasklet is therefor
|
|
|
|
* important that no requests on any AP get lost.
|
|
|
|
*/
|
|
|
|
if (ap_using_interrupts())
|
|
|
|
xchg(ap_airq.lsi_ptr, 0);
|
|
|
|
|
2016-08-25 17:16:03 +08:00
|
|
|
spin_lock_bh(&ap_list_lock);
|
|
|
|
for_each_ap_card(ac) {
|
|
|
|
for_each_ap_queue(aq, ac) {
|
|
|
|
spin_lock_bh(&aq->lock);
|
|
|
|
wait = min(wait, ap_sm_event_loop(aq, AP_EVENT_POLL));
|
|
|
|
spin_unlock_bh(&aq->lock);
|
|
|
|
}
|
2015-09-14 23:01:23 +08:00
|
|
|
}
|
2016-08-25 17:16:03 +08:00
|
|
|
spin_unlock_bh(&ap_list_lock);
|
|
|
|
|
|
|
|
ap_wait(wait);
|
2007-07-10 17:24:19 +08:00
|
|
|
}
|
|
|
|
|
2016-09-21 20:12:53 +08:00
|
|
|
static int ap_pending_requests(void)
|
|
|
|
{
|
2016-08-25 17:16:03 +08:00
|
|
|
struct ap_card *ac;
|
|
|
|
struct ap_queue *aq;
|
|
|
|
|
|
|
|
spin_lock_bh(&ap_list_lock);
|
|
|
|
for_each_ap_card(ac) {
|
|
|
|
for_each_ap_queue(aq, ac) {
|
|
|
|
if (aq->queue_count == 0)
|
|
|
|
continue;
|
|
|
|
spin_unlock_bh(&ap_list_lock);
|
|
|
|
return 1;
|
2016-09-21 20:12:53 +08:00
|
|
|
}
|
|
|
|
}
|
2016-08-25 17:16:03 +08:00
|
|
|
spin_unlock_bh(&ap_list_lock);
|
|
|
|
return 0;
|
2016-09-21 20:12:53 +08:00
|
|
|
}
|
|
|
|
|
2015-07-17 19:43:18 +08:00
|
|
|
/**
|
|
|
|
* ap_poll_thread(): Thread that polls for finished requests.
|
|
|
|
* @data: Unused pointer
|
|
|
|
*
|
|
|
|
* AP bus poll thread. The purpose of this thread is to poll for
|
|
|
|
* finished requests in a loop if there is a "free" cpu - that is
|
|
|
|
* a cpu that doesn't have anything better to do. The polling stops
|
|
|
|
* as soon as there is another task or if all messages have been
|
|
|
|
* delivered.
|
|
|
|
*/
|
|
|
|
static int ap_poll_thread(void *data)
|
|
|
|
{
|
|
|
|
DECLARE_WAITQUEUE(wait, current);
|
|
|
|
|
|
|
|
set_user_nice(current, MAX_NICE);
|
|
|
|
set_freezable();
|
|
|
|
while (!kthread_should_stop()) {
|
|
|
|
add_wait_queue(&ap_poll_wait, &wait);
|
|
|
|
set_current_state(TASK_INTERRUPTIBLE);
|
2016-09-21 20:12:53 +08:00
|
|
|
if (ap_suspend_flag || !ap_pending_requests()) {
|
2015-07-17 19:43:18 +08:00
|
|
|
schedule();
|
|
|
|
try_to_freeze();
|
|
|
|
}
|
|
|
|
set_current_state(TASK_RUNNING);
|
|
|
|
remove_wait_queue(&ap_poll_wait, &wait);
|
|
|
|
if (need_resched()) {
|
|
|
|
schedule();
|
|
|
|
try_to_freeze();
|
|
|
|
continue;
|
|
|
|
}
|
2015-09-14 23:01:23 +08:00
|
|
|
ap_tasklet_fn(0);
|
2016-09-21 20:12:53 +08:00
|
|
|
}
|
|
|
|
|
2015-07-17 19:43:18 +08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int ap_poll_thread_start(void)
|
|
|
|
{
|
|
|
|
int rc;
|
|
|
|
|
|
|
|
if (ap_using_interrupts() || ap_poll_kthread)
|
|
|
|
return 0;
|
|
|
|
mutex_lock(&ap_poll_thread_mutex);
|
|
|
|
ap_poll_kthread = kthread_run(ap_poll_thread, NULL, "appoll");
|
2018-07-19 12:42:05 +08:00
|
|
|
rc = PTR_ERR_OR_ZERO(ap_poll_kthread);
|
2015-07-17 19:43:18 +08:00
|
|
|
if (rc)
|
|
|
|
ap_poll_kthread = NULL;
|
|
|
|
mutex_unlock(&ap_poll_thread_mutex);
|
|
|
|
return rc;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void ap_poll_thread_stop(void)
|
|
|
|
{
|
|
|
|
if (!ap_poll_kthread)
|
|
|
|
return;
|
|
|
|
mutex_lock(&ap_poll_thread_mutex);
|
|
|
|
kthread_stop(ap_poll_kthread);
|
|
|
|
ap_poll_kthread = NULL;
|
|
|
|
mutex_unlock(&ap_poll_thread_mutex);
|
|
|
|
}
|
|
|
|
|
2016-08-25 17:16:03 +08:00
|
|
|
#define is_card_dev(x) ((x)->parent == ap_root_device)
|
|
|
|
#define is_queue_dev(x) ((x)->parent != ap_root_device)
|
2006-09-20 21:58:25 +08:00
|
|
|
|
|
|
|
/**
|
2008-04-17 13:46:28 +08:00
|
|
|
* ap_bus_match()
|
|
|
|
* @dev: Pointer to device
|
|
|
|
* @drv: Pointer to device_driver
|
|
|
|
*
|
2006-09-20 21:58:25 +08:00
|
|
|
* AP bus driver registration/unregistration.
|
|
|
|
*/
|
|
|
|
static int ap_bus_match(struct device *dev, struct device_driver *drv)
|
|
|
|
{
|
|
|
|
struct ap_driver *ap_drv = to_ap_drv(drv);
|
|
|
|
struct ap_device_id *id;
|
|
|
|
|
2008-04-17 13:46:28 +08:00
|
|
|
/*
|
2006-09-20 21:58:25 +08:00
|
|
|
* Compare device type of the device with the list of
|
|
|
|
* supported types of the device_driver.
|
|
|
|
*/
|
|
|
|
for (id = ap_drv->ids; id->match_flags; id++) {
|
2016-08-25 17:16:03 +08:00
|
|
|
if (is_card_dev(dev) &&
|
|
|
|
id->match_flags & AP_DEVICE_ID_MATCH_CARD_TYPE &&
|
|
|
|
id->dev_type == to_ap_dev(dev)->device_type)
|
|
|
|
return 1;
|
|
|
|
if (is_queue_dev(dev) &&
|
|
|
|
id->match_flags & AP_DEVICE_ID_MATCH_QUEUE_TYPE &&
|
|
|
|
id->dev_type == to_ap_dev(dev)->device_type)
|
|
|
|
return 1;
|
2006-09-20 21:58:25 +08:00
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2008-04-17 13:46:28 +08:00
|
|
|
* ap_uevent(): Uevent function for AP devices.
|
|
|
|
* @dev: Pointer to device
|
|
|
|
* @env: Pointer to kobj_uevent_env
|
|
|
|
*
|
|
|
|
* It sets up a single environment variable DEV_TYPE which contains the
|
|
|
|
* hardware device type.
|
2006-09-20 21:58:25 +08:00
|
|
|
*/
|
2018-08-17 18:36:01 +08:00
|
|
|
static int ap_uevent(struct device *dev, struct kobj_uevent_env *env)
|
2006-09-20 21:58:25 +08:00
|
|
|
{
|
|
|
|
struct ap_device *ap_dev = to_ap_dev(dev);
|
2007-08-14 21:15:12 +08:00
|
|
|
int retval = 0;
|
2006-09-20 21:58:25 +08:00
|
|
|
|
|
|
|
if (!ap_dev)
|
|
|
|
return -ENODEV;
|
|
|
|
|
|
|
|
/* Set up DEV_TYPE environment variable. */
|
2007-08-14 21:15:12 +08:00
|
|
|
retval = add_uevent_var(env, "DEV_TYPE=%04X", ap_dev->device_type);
|
2007-03-31 13:23:12 +08:00
|
|
|
if (retval)
|
|
|
|
return retval;
|
|
|
|
|
2006-12-04 22:40:10 +08:00
|
|
|
/* Add MODALIAS= */
|
2007-08-14 21:15:12 +08:00
|
|
|
retval = add_uevent_var(env, "MODALIAS=ap:t%02X", ap_dev->device_type);
|
2007-03-31 13:23:12 +08:00
|
|
|
|
|
|
|
return retval;
|
2006-09-20 21:58:25 +08:00
|
|
|
}
|
|
|
|
|
2016-11-23 05:06:00 +08:00
|
|
|
static int ap_dev_suspend(struct device *dev)
|
2009-06-22 18:08:16 +08:00
|
|
|
{
|
|
|
|
struct ap_device *ap_dev = to_ap_dev(dev);
|
|
|
|
|
2016-08-25 17:16:03 +08:00
|
|
|
if (ap_dev->drv && ap_dev->drv->suspend)
|
|
|
|
ap_dev->drv->suspend(ap_dev);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int ap_dev_resume(struct device *dev)
|
|
|
|
{
|
|
|
|
struct ap_device *ap_dev = to_ap_dev(dev);
|
|
|
|
|
|
|
|
if (ap_dev->drv && ap_dev->drv->resume)
|
|
|
|
ap_dev->drv->resume(ap_dev);
|
2015-07-17 19:43:18 +08:00
|
|
|
return 0;
|
|
|
|
}
|
2009-09-23 04:58:51 +08:00
|
|
|
|
2015-07-17 19:43:18 +08:00
|
|
|
static void ap_bus_suspend(void)
|
|
|
|
{
|
2018-08-17 18:36:01 +08:00
|
|
|
AP_DBF(DBF_DEBUG, "%s running\n", __func__);
|
2016-11-24 13:45:21 +08:00
|
|
|
|
2015-07-17 19:43:18 +08:00
|
|
|
ap_suspend_flag = 1;
|
|
|
|
/*
|
|
|
|
* Disable scanning for devices, thus we do not want to scan
|
|
|
|
* for them after removing.
|
|
|
|
*/
|
2015-07-27 18:47:40 +08:00
|
|
|
flush_work(&ap_scan_work);
|
2015-07-17 19:43:18 +08:00
|
|
|
tasklet_disable(&ap_tasklet);
|
|
|
|
}
|
|
|
|
|
2016-08-25 17:16:03 +08:00
|
|
|
static int __ap_card_devices_unregister(struct device *dev, void *dummy)
|
|
|
|
{
|
|
|
|
if (is_card_dev(dev))
|
|
|
|
device_unregister(dev);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int __ap_queue_devices_unregister(struct device *dev, void *dummy)
|
|
|
|
{
|
|
|
|
if (is_queue_dev(dev))
|
|
|
|
device_unregister(dev);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int __ap_queue_devices_with_id_unregister(struct device *dev, void *data)
|
2015-07-17 19:43:18 +08:00
|
|
|
{
|
2016-08-25 17:16:03 +08:00
|
|
|
if (is_queue_dev(dev) &&
|
|
|
|
AP_QID_CARD(to_ap_queue(dev)->qid) == (int)(long) data)
|
|
|
|
device_unregister(dev);
|
2015-07-17 19:43:18 +08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void ap_bus_resume(void)
|
2009-06-22 18:08:16 +08:00
|
|
|
{
|
2013-06-24 16:30:41 +08:00
|
|
|
int rc;
|
2009-06-22 18:08:16 +08:00
|
|
|
|
2018-08-17 18:36:01 +08:00
|
|
|
AP_DBF(DBF_DEBUG, "%s running\n", __func__);
|
2016-11-24 13:45:21 +08:00
|
|
|
|
2016-08-25 17:16:03 +08:00
|
|
|
/* remove all queue devices */
|
|
|
|
bus_for_each_dev(&ap_bus_type, NULL, NULL,
|
|
|
|
__ap_queue_devices_unregister);
|
|
|
|
/* remove all card devices */
|
|
|
|
bus_for_each_dev(&ap_bus_type, NULL, NULL,
|
|
|
|
__ap_card_devices_unregister);
|
|
|
|
|
2015-07-17 19:43:18 +08:00
|
|
|
/* Reset thin interrupt setting */
|
|
|
|
if (ap_interrupts_available() && !ap_using_interrupts()) {
|
|
|
|
rc = register_adapter_interrupt(&ap_airq);
|
|
|
|
ap_airq_flag = (rc == 0);
|
2009-09-23 04:58:51 +08:00
|
|
|
}
|
2015-07-17 19:43:18 +08:00
|
|
|
if (!ap_interrupts_available() && ap_using_interrupts()) {
|
|
|
|
unregister_adapter_interrupt(&ap_airq);
|
|
|
|
ap_airq_flag = 0;
|
|
|
|
}
|
|
|
|
/* Reset domain */
|
|
|
|
if (!user_set_domain)
|
|
|
|
ap_domain_index = -1;
|
|
|
|
/* Get things going again */
|
|
|
|
ap_suspend_flag = 0;
|
|
|
|
if (ap_airq_flag)
|
|
|
|
xchg(ap_airq.lsi_ptr, 0);
|
|
|
|
tasklet_enable(&ap_tasklet);
|
2015-07-27 18:47:40 +08:00
|
|
|
queue_work(system_long_wq, &ap_scan_work);
|
2015-07-17 19:43:18 +08:00
|
|
|
}
|
2009-06-22 18:08:16 +08:00
|
|
|
|
2015-07-17 19:43:18 +08:00
|
|
|
static int ap_power_event(struct notifier_block *this, unsigned long event,
|
|
|
|
void *ptr)
|
|
|
|
{
|
|
|
|
switch (event) {
|
|
|
|
case PM_HIBERNATION_PREPARE:
|
|
|
|
case PM_SUSPEND_PREPARE:
|
|
|
|
ap_bus_suspend();
|
|
|
|
break;
|
|
|
|
case PM_POST_HIBERNATION:
|
|
|
|
case PM_POST_SUSPEND:
|
|
|
|
ap_bus_resume();
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
return NOTIFY_DONE;
|
2009-06-22 18:08:16 +08:00
|
|
|
}
|
2015-07-17 19:43:18 +08:00
|
|
|
static struct notifier_block ap_power_notifier = {
|
|
|
|
.notifier_call = ap_power_event,
|
|
|
|
};
|
2009-06-22 18:08:16 +08:00
|
|
|
|
2016-08-25 17:16:03 +08:00
|
|
|
static SIMPLE_DEV_PM_OPS(ap_bus_pm_ops, ap_dev_suspend, ap_dev_resume);
|
2016-11-23 05:06:00 +08:00
|
|
|
|
2006-09-20 21:58:25 +08:00
|
|
|
static struct bus_type ap_bus_type = {
|
|
|
|
.name = "ap",
|
|
|
|
.match = &ap_bus_match,
|
|
|
|
.uevent = &ap_uevent,
|
2016-11-23 05:06:00 +08:00
|
|
|
.pm = &ap_bus_pm_ops,
|
2006-09-20 21:58:25 +08:00
|
|
|
};
|
|
|
|
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
static int __ap_revise_reserved(struct device *dev, void *dummy)
|
|
|
|
{
|
|
|
|
int rc, card, queue, devres, drvres;
|
|
|
|
|
|
|
|
if (is_queue_dev(dev)) {
|
|
|
|
card = AP_QID_CARD(to_ap_queue(dev)->qid);
|
|
|
|
queue = AP_QID_QUEUE(to_ap_queue(dev)->qid);
|
|
|
|
mutex_lock(&ap_perms_mutex);
|
|
|
|
devres = test_bit_inv(card, ap_perms.apm)
|
|
|
|
&& test_bit_inv(queue, ap_perms.aqm);
|
|
|
|
mutex_unlock(&ap_perms_mutex);
|
|
|
|
drvres = to_ap_drv(dev->driver)->flags
|
|
|
|
& AP_DRIVER_FLAG_DEFAULT;
|
|
|
|
if (!!devres != !!drvres) {
|
|
|
|
AP_DBF(DBF_DEBUG, "reprobing queue=%02x.%04x\n",
|
|
|
|
card, queue);
|
|
|
|
rc = device_reprobe(dev);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void ap_bus_revise_bindings(void)
|
|
|
|
{
|
|
|
|
bus_for_each_dev(&ap_bus_type, NULL, NULL, __ap_revise_reserved);
|
|
|
|
}
|
|
|
|
|
|
|
|
int ap_owned_by_def_drv(int card, int queue)
|
|
|
|
{
|
|
|
|
int rc = 0;
|
|
|
|
|
|
|
|
if (card < 0 || card >= AP_DEVICES || queue < 0 || queue >= AP_DOMAINS)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
mutex_lock(&ap_perms_mutex);
|
|
|
|
|
|
|
|
if (test_bit_inv(card, ap_perms.apm)
|
|
|
|
&& test_bit_inv(queue, ap_perms.aqm))
|
|
|
|
rc = 1;
|
|
|
|
|
|
|
|
mutex_unlock(&ap_perms_mutex);
|
|
|
|
|
|
|
|
return rc;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(ap_owned_by_def_drv);
|
|
|
|
|
|
|
|
int ap_apqn_in_matrix_owned_by_def_drv(unsigned long *apm,
|
|
|
|
unsigned long *aqm)
|
|
|
|
{
|
|
|
|
int card, queue, rc = 0;
|
|
|
|
|
|
|
|
mutex_lock(&ap_perms_mutex);
|
|
|
|
|
|
|
|
for (card = 0; !rc && card < AP_DEVICES; card++)
|
|
|
|
if (test_bit_inv(card, apm) &&
|
|
|
|
test_bit_inv(card, ap_perms.apm))
|
|
|
|
for (queue = 0; !rc && queue < AP_DOMAINS; queue++)
|
|
|
|
if (test_bit_inv(queue, aqm) &&
|
|
|
|
test_bit_inv(queue, ap_perms.aqm))
|
|
|
|
rc = 1;
|
|
|
|
|
|
|
|
mutex_unlock(&ap_perms_mutex);
|
|
|
|
|
|
|
|
return rc;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(ap_apqn_in_matrix_owned_by_def_drv);
|
|
|
|
|
2006-09-20 21:58:25 +08:00
|
|
|
static int ap_device_probe(struct device *dev)
|
|
|
|
{
|
|
|
|
struct ap_device *ap_dev = to_ap_dev(dev);
|
2015-09-14 23:01:23 +08:00
|
|
|
struct ap_driver *ap_drv = to_ap_drv(dev->driver);
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
int card, queue, devres, drvres, rc;
|
|
|
|
|
|
|
|
if (is_queue_dev(dev)) {
|
|
|
|
/*
|
|
|
|
* If the apqn is marked as reserved/used by ap bus and
|
|
|
|
* default drivers, only probe with drivers with the default
|
|
|
|
* flag set. If it is not marked, only probe with drivers
|
|
|
|
* with the default flag not set.
|
|
|
|
*/
|
|
|
|
card = AP_QID_CARD(to_ap_queue(dev)->qid);
|
|
|
|
queue = AP_QID_QUEUE(to_ap_queue(dev)->qid);
|
|
|
|
mutex_lock(&ap_perms_mutex);
|
|
|
|
devres = test_bit_inv(card, ap_perms.apm)
|
|
|
|
&& test_bit_inv(queue, ap_perms.aqm);
|
|
|
|
mutex_unlock(&ap_perms_mutex);
|
|
|
|
drvres = ap_drv->flags & AP_DRIVER_FLAG_DEFAULT;
|
|
|
|
if (!!devres != !!drvres)
|
|
|
|
return -ENODEV;
|
|
|
|
}
|
2014-07-15 01:11:48 +08:00
|
|
|
|
2017-05-24 16:26:29 +08:00
|
|
|
/* Add queue/card to list of active queues/cards */
|
|
|
|
spin_lock_bh(&ap_list_lock);
|
|
|
|
if (is_card_dev(dev))
|
|
|
|
list_add(&to_ap_card(dev)->list, &ap_card_list);
|
|
|
|
else
|
|
|
|
list_add(&to_ap_queue(dev)->list,
|
|
|
|
&to_ap_queue(dev)->card->queues);
|
|
|
|
spin_unlock_bh(&ap_list_lock);
|
|
|
|
|
2015-09-14 23:01:23 +08:00
|
|
|
ap_dev->drv = ap_drv;
|
2006-09-20 21:58:25 +08:00
|
|
|
rc = ap_drv->probe ? ap_drv->probe(ap_dev) : -ENODEV;
|
2017-05-24 16:26:29 +08:00
|
|
|
|
|
|
|
if (rc) {
|
|
|
|
spin_lock_bh(&ap_list_lock);
|
|
|
|
if (is_card_dev(dev))
|
|
|
|
list_del_init(&to_ap_card(dev)->list);
|
|
|
|
else
|
|
|
|
list_del_init(&to_ap_queue(dev)->list);
|
|
|
|
spin_unlock_bh(&ap_list_lock);
|
2015-09-14 23:01:23 +08:00
|
|
|
ap_dev->drv = NULL;
|
2017-05-24 16:26:29 +08:00
|
|
|
}
|
|
|
|
|
2006-09-20 21:58:25 +08:00
|
|
|
return rc;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int ap_device_remove(struct device *dev)
|
|
|
|
{
|
|
|
|
struct ap_device *ap_dev = to_ap_dev(dev);
|
|
|
|
struct ap_driver *ap_drv = ap_dev->drv;
|
|
|
|
|
2017-05-24 16:26:29 +08:00
|
|
|
if (ap_drv->remove)
|
|
|
|
ap_drv->remove(ap_dev);
|
|
|
|
|
|
|
|
/* Remove queue/card from list of active queues/cards */
|
2016-08-25 17:16:03 +08:00
|
|
|
spin_lock_bh(&ap_list_lock);
|
|
|
|
if (is_card_dev(dev))
|
|
|
|
list_del_init(&to_ap_card(dev)->list);
|
|
|
|
else
|
|
|
|
list_del_init(&to_ap_queue(dev)->list);
|
|
|
|
spin_unlock_bh(&ap_list_lock);
|
2017-05-24 16:26:29 +08:00
|
|
|
|
2006-09-20 21:58:25 +08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
int ap_driver_register(struct ap_driver *ap_drv, struct module *owner,
|
|
|
|
char *name)
|
|
|
|
{
|
|
|
|
struct device_driver *drv = &ap_drv->driver;
|
|
|
|
|
s390/zcrypt: Fix kernel crash on systems without AP bus support
On systems without AP bus (e.g. KVM) the kernel crashes during init
calls when zcrypt is built-in:
kernel BUG at drivers/base/driver.c:153!
illegal operation: 0001 ilc:1 [#1] SMP
Modules linked in:
CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.2.0+ #221
task: 0000000010a40000 ti: 0000000010a48000 task.ti:0000000010a48000
Krnl PSW : 0704c00180000000 0000000000592bd6(driver_register+0x106/0x140)
R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 EA:3
0000000000000012 0000000000000000 0000000000c45328 0000000000c44e30
00000000009ef63c 000000000067f598 0000000000cf3c58 0000000000000000
000000000000007b 0000000000cb1030 0000000000000002 0000000000000000
0000000000ca8580 0000000010306700 00000000001001d8 0000000010a4bd88
Krnl Code: 0000000000592bc6: f0b00004ebcf srp 4(12,%r0),3023(%r14),0
0000000000592bcc: f0a0000407f4 srp 4(11,%r0),2036,0
#0000000000592bd2: a7f40001 brc 15,592bd4
>0000000000592bd6: e330d0000004 lg %r3,0(%r13)
0000000000592bdc: c0200021edfd larl %r2,9d07d6
0000000000592be2: c0e500126d8f brasl %r14,7e0700
0000000000592be8: e330d0080004 lg %r3,8(%r13)
0000000000592bee: a7f4ffab brc 15,592b44
Call Trace:
([<00000000001001c8>] do_one_initcall+0x90/0x1d0)
[<0000000000c6dd34>] kernel_init_freeable+0x1e4/0x2a0
[<00000000007db53a>] kernel_init+0x2a/0x120
[<00000000007e8ece>] kernel_thread_starter+0x6/0xc
[<00000000007e8ec8>] kernel_thread_starter+0x0/0xc
Last Breaking-Event-Address:
[<0000000000592bd2>] driver_register+0x102/0x140
When zcrypt is built as a module, the module loader ensures that the
driver modules cannot be loaded if the AP bus module returns an error
during initialisation. But if zcrypt and the driver are built-in, the
driver is getting initialised even if the AP bus initialisation
failed. The driver invokes ap_driver_register() during initialisation,
which then causes operations on uninitialised data structures to be
performed.
Explicitly protect ap_driver_register() by introducing an
"initialised" flag that gets set iff the AP bus initialisation was
successful. When the AP bus initialisation failed,
ap_driver_register() will error out with -ENODEV, causing the driver
initialisation to fail as well.
Test results:
1. Inside KVM (no AP bus), zcrypt built-in
Boots. /sys/bus/ap not present (expected).
2. Inside KVM (no AP bus), zcrypt as module
Boots. Loading zcrypt_cex4 fails because loading ap_bus fails
(expected).
3. On LPAR with CEX5, zcrypt built-in
Boots. /sys/bus/ap/devices/card* present but .../card*/type missing
(i.e. zcrypt_device_register() fails, unrelated issue).
4. On LPAR with CEX5, zcrypt as module
Boots. Loading zcrypt_cex4 successful,
/sys/bus/ap/devices/card*/type present. No further testing
(user-space functionality) was done.
Signed-off-by: Sascha Silbe <silbe@linux.vnet.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2015-10-28 01:29:52 +08:00
|
|
|
if (!initialised)
|
|
|
|
return -ENODEV;
|
|
|
|
|
2006-09-20 21:58:25 +08:00
|
|
|
drv->bus = &ap_bus_type;
|
|
|
|
drv->probe = ap_device_probe;
|
|
|
|
drv->remove = ap_device_remove;
|
|
|
|
drv->owner = owner;
|
|
|
|
drv->name = name;
|
|
|
|
return driver_register(drv);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(ap_driver_register);
|
|
|
|
|
|
|
|
void ap_driver_unregister(struct ap_driver *ap_drv)
|
|
|
|
{
|
|
|
|
driver_unregister(&ap_drv->driver);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(ap_driver_unregister);
|
|
|
|
|
2012-09-11 03:34:26 +08:00
|
|
|
void ap_bus_force_rescan(void)
|
|
|
|
{
|
2015-07-17 19:43:18 +08:00
|
|
|
if (ap_suspend_flag)
|
|
|
|
return;
|
2013-04-12 23:52:08 +08:00
|
|
|
/* processing a asynchronous bus rescan */
|
2015-07-23 16:55:59 +08:00
|
|
|
del_timer(&ap_config_timer);
|
2015-07-27 18:47:40 +08:00
|
|
|
queue_work(system_long_wq, &ap_scan_work);
|
|
|
|
flush_work(&ap_scan_work);
|
2012-09-11 03:34:26 +08:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(ap_bus_force_rescan);
|
|
|
|
|
2008-04-17 13:46:28 +08:00
|
|
|
/*
|
2018-08-20 21:27:45 +08:00
|
|
|
* hex2bitmap() - parse hex mask string and set bitmap.
|
|
|
|
* Valid strings are "0x012345678" with at least one valid hex number.
|
|
|
|
* Rest of the bitmap to the right is padded with 0. No spaces allowed
|
|
|
|
* within the string, the leading 0x may be omitted.
|
|
|
|
* Returns the bitmask with exactly the bits set as given by the hex
|
|
|
|
* string (both in big endian order).
|
2006-09-20 21:58:25 +08:00
|
|
|
*/
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
static int hex2bitmap(const char *str, unsigned long *bitmap, int bits)
|
|
|
|
{
|
|
|
|
int i, n, b;
|
|
|
|
|
|
|
|
/* bits needs to be a multiple of 8 */
|
|
|
|
if (bits & 0x07)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
if (str[0] == '0' && str[1] == 'x')
|
|
|
|
str++;
|
|
|
|
if (*str == 'x')
|
|
|
|
str++;
|
|
|
|
|
|
|
|
for (i = 0; isxdigit(*str) && i < bits; str++) {
|
|
|
|
b = hex_to_bin(*str);
|
|
|
|
for (n = 0; n < 4; n++)
|
|
|
|
if (b & (0x08 >> n))
|
|
|
|
set_bit_inv(i + n, bitmap);
|
|
|
|
i += 4;
|
|
|
|
}
|
|
|
|
|
2018-08-20 21:27:45 +08:00
|
|
|
if (*str == '\n')
|
|
|
|
str++;
|
|
|
|
if (*str)
|
|
|
|
return -EINVAL;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
2018-09-05 13:45:11 +08:00
|
|
|
* modify_bitmap() - parse bitmask argument and modify an existing
|
|
|
|
* bit mask accordingly. A concatenation (done with ',') of these
|
|
|
|
* terms is recognized:
|
2018-08-20 21:27:45 +08:00
|
|
|
* +<bitnr>[-<bitnr>] or -<bitnr>[-<bitnr>]
|
|
|
|
* <bitnr> may be any valid number (hex, decimal or octal) in the range
|
|
|
|
* 0...bits-1; the leading + or - is required. Here are some examples:
|
|
|
|
* +0-15,+32,-128,-0xFF
|
|
|
|
* -0-255,+1-16,+0x128
|
|
|
|
* +1,+2,+3,+4,-5,-7-10
|
2018-09-05 13:45:11 +08:00
|
|
|
* Returns the new bitmap after all changes have been applied. Every
|
|
|
|
* positive value in the string will set a bit and every negative value
|
|
|
|
* in the string will clear a bit. As a bit may be touched more than once,
|
|
|
|
* the last 'operation' wins:
|
|
|
|
* +0-255,-128 = first bits 0-255 will be set, then bit 128 will be
|
|
|
|
* cleared again. All other bits are unmodified.
|
2018-08-20 21:27:45 +08:00
|
|
|
*/
|
2018-09-05 13:45:11 +08:00
|
|
|
static int modify_bitmap(const char *str, unsigned long *bitmap, int bits)
|
2018-08-20 21:27:45 +08:00
|
|
|
{
|
|
|
|
int a, i, z;
|
|
|
|
char *np, sign;
|
|
|
|
|
|
|
|
/* bits needs to be a multiple of 8 */
|
|
|
|
if (bits & 0x07)
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
return -EINVAL;
|
|
|
|
|
2018-08-20 21:27:45 +08:00
|
|
|
while (*str) {
|
|
|
|
sign = *str++;
|
|
|
|
if (sign != '+' && sign != '-')
|
|
|
|
return -EINVAL;
|
|
|
|
a = z = simple_strtoul(str, &np, 0);
|
|
|
|
if (str == np || a >= bits)
|
|
|
|
return -EINVAL;
|
|
|
|
str = np;
|
|
|
|
if (*str == '-') {
|
|
|
|
z = simple_strtoul(++str, &np, 0);
|
|
|
|
if (str == np || a > z || z >= bits)
|
|
|
|
return -EINVAL;
|
|
|
|
str = np;
|
|
|
|
}
|
|
|
|
for (i = a; i <= z; i++)
|
2018-09-05 13:45:11 +08:00
|
|
|
if (sign == '+')
|
|
|
|
set_bit_inv(i, bitmap);
|
|
|
|
else
|
|
|
|
clear_bit_inv(i, bitmap);
|
2018-08-20 21:27:45 +08:00
|
|
|
while (*str == ',' || *str == '\n')
|
|
|
|
str++;
|
|
|
|
}
|
|
|
|
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2018-08-20 21:27:45 +08:00
|
|
|
/*
|
|
|
|
* process_mask_arg() - parse a bitmap string and clear/set the
|
|
|
|
* bits in the bitmap accordingly. The string may be given as
|
|
|
|
* absolute value, a hex string like 0x1F2E3D4C5B6A" simple over-
|
|
|
|
* writing the current content of the bitmap. Or as relative string
|
|
|
|
* like "+1-16,-32,-0x40,+128" where only single bits or ranges of
|
|
|
|
* bits are cleared or set. Distinction is done based on the very
|
|
|
|
* first character which may be '+' or '-' for the relative string
|
|
|
|
* and othewise assume to be an absolute value string. If parsing fails
|
|
|
|
* a negative errno value is returned. All arguments and bitmaps are
|
|
|
|
* big endian order.
|
|
|
|
*/
|
|
|
|
static int process_mask_arg(const char *str,
|
|
|
|
unsigned long *bitmap, int bits,
|
|
|
|
struct mutex *lock)
|
|
|
|
{
|
2018-09-05 13:45:11 +08:00
|
|
|
unsigned long *newmap, size;
|
|
|
|
int rc;
|
2018-08-20 21:27:45 +08:00
|
|
|
|
|
|
|
/* bits needs to be a multiple of 8 */
|
|
|
|
if (bits & 0x07)
|
|
|
|
return -EINVAL;
|
|
|
|
|
2018-09-05 13:45:11 +08:00
|
|
|
size = BITS_TO_LONGS(bits)*sizeof(unsigned long);
|
|
|
|
newmap = kmalloc(size, GFP_KERNEL);
|
|
|
|
if (!newmap)
|
|
|
|
return -ENOMEM;
|
|
|
|
if (mutex_lock_interruptible(lock)) {
|
|
|
|
kfree(newmap);
|
|
|
|
return -ERESTARTSYS;
|
|
|
|
}
|
|
|
|
|
2018-08-20 21:27:45 +08:00
|
|
|
if (*str == '+' || *str == '-') {
|
2018-09-05 13:45:11 +08:00
|
|
|
memcpy(newmap, bitmap, size);
|
|
|
|
rc = modify_bitmap(str, newmap, bits);
|
2018-08-20 21:27:45 +08:00
|
|
|
} else {
|
2018-09-05 13:45:11 +08:00
|
|
|
memset(newmap, 0, size);
|
|
|
|
rc = hex2bitmap(str, newmap, bits);
|
2018-08-20 21:27:45 +08:00
|
|
|
}
|
2018-09-05 13:45:11 +08:00
|
|
|
if (rc == 0)
|
|
|
|
memcpy(bitmap, newmap, size);
|
2018-08-20 21:27:45 +08:00
|
|
|
mutex_unlock(lock);
|
2018-09-05 13:45:11 +08:00
|
|
|
kfree(newmap);
|
|
|
|
return rc;
|
2018-08-20 21:27:45 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* AP bus attributes.
|
|
|
|
*/
|
|
|
|
|
2006-09-20 21:58:25 +08:00
|
|
|
static ssize_t ap_domain_show(struct bus_type *bus, char *buf)
|
|
|
|
{
|
|
|
|
return snprintf(buf, PAGE_SIZE, "%d\n", ap_domain_index);
|
|
|
|
}
|
|
|
|
|
2016-08-25 17:11:30 +08:00
|
|
|
static ssize_t ap_domain_store(struct bus_type *bus,
|
|
|
|
const char *buf, size_t count)
|
|
|
|
{
|
|
|
|
int domain;
|
|
|
|
|
|
|
|
if (sscanf(buf, "%i\n", &domain) != 1 ||
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
domain < 0 || domain > ap_max_domain_id ||
|
|
|
|
!test_bit_inv(domain, ap_perms.aqm))
|
2016-08-25 17:11:30 +08:00
|
|
|
return -EINVAL;
|
|
|
|
spin_lock_bh(&ap_domain_lock);
|
|
|
|
ap_domain_index = domain;
|
|
|
|
spin_unlock_bh(&ap_domain_lock);
|
2016-11-24 13:45:21 +08:00
|
|
|
|
2017-05-12 22:35:14 +08:00
|
|
|
AP_DBF(DBF_DEBUG, "stored new default domain=%d\n", domain);
|
2016-11-24 13:45:21 +08:00
|
|
|
|
2016-08-25 17:11:30 +08:00
|
|
|
return count;
|
|
|
|
}
|
|
|
|
|
2018-08-17 18:36:01 +08:00
|
|
|
static BUS_ATTR_RW(ap_domain);
|
2006-09-20 21:58:25 +08:00
|
|
|
|
2013-11-20 17:47:13 +08:00
|
|
|
static ssize_t ap_control_domain_mask_show(struct bus_type *bus, char *buf)
|
|
|
|
{
|
2015-06-26 22:55:35 +08:00
|
|
|
if (!ap_configuration) /* QCI not supported */
|
|
|
|
return snprintf(buf, PAGE_SIZE, "not supported\n");
|
2016-08-25 17:16:03 +08:00
|
|
|
|
2015-06-26 22:55:35 +08:00
|
|
|
return snprintf(buf, PAGE_SIZE,
|
|
|
|
"0x%08x%08x%08x%08x%08x%08x%08x%08x\n",
|
2013-11-20 17:47:13 +08:00
|
|
|
ap_configuration->adm[0], ap_configuration->adm[1],
|
|
|
|
ap_configuration->adm[2], ap_configuration->adm[3],
|
|
|
|
ap_configuration->adm[4], ap_configuration->adm[5],
|
|
|
|
ap_configuration->adm[6], ap_configuration->adm[7]);
|
|
|
|
}
|
|
|
|
|
2018-08-17 18:36:01 +08:00
|
|
|
static BUS_ATTR_RO(ap_control_domain_mask);
|
2013-11-20 17:47:13 +08:00
|
|
|
|
2016-08-25 17:16:03 +08:00
|
|
|
static ssize_t ap_usage_domain_mask_show(struct bus_type *bus, char *buf)
|
|
|
|
{
|
|
|
|
if (!ap_configuration) /* QCI not supported */
|
|
|
|
return snprintf(buf, PAGE_SIZE, "not supported\n");
|
|
|
|
|
|
|
|
return snprintf(buf, PAGE_SIZE,
|
|
|
|
"0x%08x%08x%08x%08x%08x%08x%08x%08x\n",
|
|
|
|
ap_configuration->aqm[0], ap_configuration->aqm[1],
|
|
|
|
ap_configuration->aqm[2], ap_configuration->aqm[3],
|
|
|
|
ap_configuration->aqm[4], ap_configuration->aqm[5],
|
|
|
|
ap_configuration->aqm[6], ap_configuration->aqm[7]);
|
|
|
|
}
|
|
|
|
|
2018-08-17 18:36:01 +08:00
|
|
|
static BUS_ATTR_RO(ap_usage_domain_mask);
|
2006-09-20 21:58:25 +08:00
|
|
|
|
2008-12-25 20:38:41 +08:00
|
|
|
static ssize_t ap_interrupts_show(struct bus_type *bus, char *buf)
|
|
|
|
{
|
|
|
|
return snprintf(buf, PAGE_SIZE, "%d\n",
|
|
|
|
ap_using_interrupts() ? 1 : 0);
|
|
|
|
}
|
|
|
|
|
2018-08-17 18:36:01 +08:00
|
|
|
static BUS_ATTR_RO(ap_interrupts);
|
|
|
|
|
|
|
|
static ssize_t config_time_show(struct bus_type *bus, char *buf)
|
|
|
|
{
|
|
|
|
return snprintf(buf, PAGE_SIZE, "%d\n", ap_config_time);
|
|
|
|
}
|
2008-12-25 20:38:41 +08:00
|
|
|
|
2018-08-17 18:36:01 +08:00
|
|
|
static ssize_t config_time_store(struct bus_type *bus,
|
|
|
|
const char *buf, size_t count)
|
2006-09-20 21:58:25 +08:00
|
|
|
{
|
|
|
|
int time;
|
|
|
|
|
|
|
|
if (sscanf(buf, "%d\n", &time) != 1 || time < 5 || time > 120)
|
|
|
|
return -EINVAL;
|
|
|
|
ap_config_time = time;
|
2015-07-23 16:55:59 +08:00
|
|
|
mod_timer(&ap_config_timer, jiffies + ap_config_time * HZ);
|
2006-09-20 21:58:25 +08:00
|
|
|
return count;
|
|
|
|
}
|
|
|
|
|
2018-08-17 18:36:01 +08:00
|
|
|
static BUS_ATTR_RW(config_time);
|
2006-09-20 21:58:25 +08:00
|
|
|
|
2018-08-17 18:36:01 +08:00
|
|
|
static ssize_t poll_thread_show(struct bus_type *bus, char *buf)
|
2006-09-20 21:58:25 +08:00
|
|
|
{
|
|
|
|
return snprintf(buf, PAGE_SIZE, "%d\n", ap_poll_kthread ? 1 : 0);
|
|
|
|
}
|
|
|
|
|
2018-08-17 18:36:01 +08:00
|
|
|
static ssize_t poll_thread_store(struct bus_type *bus,
|
|
|
|
const char *buf, size_t count)
|
2006-09-20 21:58:25 +08:00
|
|
|
{
|
|
|
|
int flag, rc;
|
|
|
|
|
|
|
|
if (sscanf(buf, "%d\n", &flag) != 1)
|
|
|
|
return -EINVAL;
|
|
|
|
if (flag) {
|
|
|
|
rc = ap_poll_thread_start();
|
|
|
|
if (rc)
|
2015-07-17 19:43:18 +08:00
|
|
|
count = rc;
|
|
|
|
} else
|
2006-09-20 21:58:25 +08:00
|
|
|
ap_poll_thread_stop();
|
|
|
|
return count;
|
|
|
|
}
|
|
|
|
|
2018-08-17 18:36:01 +08:00
|
|
|
static BUS_ATTR_RW(poll_thread);
|
2006-09-20 21:58:25 +08:00
|
|
|
|
2008-07-14 15:59:08 +08:00
|
|
|
static ssize_t poll_timeout_show(struct bus_type *bus, char *buf)
|
|
|
|
{
|
|
|
|
return snprintf(buf, PAGE_SIZE, "%llu\n", poll_timeout);
|
|
|
|
}
|
|
|
|
|
|
|
|
static ssize_t poll_timeout_store(struct bus_type *bus, const char *buf,
|
|
|
|
size_t count)
|
|
|
|
{
|
|
|
|
unsigned long long time;
|
|
|
|
ktime_t hr_time;
|
|
|
|
|
|
|
|
/* 120 seconds = maximum poll interval */
|
2008-12-25 20:38:41 +08:00
|
|
|
if (sscanf(buf, "%llu\n", &time) != 1 || time < 1 ||
|
|
|
|
time > 120000000000ULL)
|
2008-07-14 15:59:08 +08:00
|
|
|
return -EINVAL;
|
|
|
|
poll_timeout = time;
|
2016-12-25 19:30:41 +08:00
|
|
|
hr_time = poll_timeout;
|
2008-07-14 15:59:08 +08:00
|
|
|
|
2015-04-28 16:31:44 +08:00
|
|
|
spin_lock_bh(&ap_poll_timer_lock);
|
|
|
|
hrtimer_cancel(&ap_poll_timer);
|
|
|
|
hrtimer_set_expires(&ap_poll_timer, hr_time);
|
|
|
|
hrtimer_start_expires(&ap_poll_timer, HRTIMER_MODE_ABS);
|
|
|
|
spin_unlock_bh(&ap_poll_timer_lock);
|
|
|
|
|
2008-07-14 15:59:08 +08:00
|
|
|
return count;
|
|
|
|
}
|
|
|
|
|
2018-08-17 18:36:01 +08:00
|
|
|
static BUS_ATTR_RW(poll_timeout);
|
2008-07-14 15:59:08 +08:00
|
|
|
|
2015-01-23 20:27:04 +08:00
|
|
|
static ssize_t ap_max_domain_id_show(struct bus_type *bus, char *buf)
|
|
|
|
{
|
2015-06-26 22:55:35 +08:00
|
|
|
int max_domain_id;
|
|
|
|
|
|
|
|
if (ap_configuration)
|
|
|
|
max_domain_id = ap_max_domain_id ? : -1;
|
|
|
|
else
|
2015-01-23 20:27:04 +08:00
|
|
|
max_domain_id = 15;
|
|
|
|
return snprintf(buf, PAGE_SIZE, "%d\n", max_domain_id);
|
|
|
|
}
|
|
|
|
|
2018-08-17 18:36:01 +08:00
|
|
|
static BUS_ATTR_RO(ap_max_domain_id);
|
2015-01-23 20:27:04 +08:00
|
|
|
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
static ssize_t apmask_show(struct bus_type *bus, char *buf)
|
|
|
|
{
|
|
|
|
int rc;
|
|
|
|
|
|
|
|
if (mutex_lock_interruptible(&ap_perms_mutex))
|
|
|
|
return -ERESTARTSYS;
|
|
|
|
rc = snprintf(buf, PAGE_SIZE,
|
|
|
|
"0x%016lx%016lx%016lx%016lx\n",
|
|
|
|
ap_perms.apm[0], ap_perms.apm[1],
|
|
|
|
ap_perms.apm[2], ap_perms.apm[3]);
|
|
|
|
mutex_unlock(&ap_perms_mutex);
|
|
|
|
|
|
|
|
return rc;
|
|
|
|
}
|
|
|
|
|
|
|
|
static ssize_t apmask_store(struct bus_type *bus, const char *buf,
|
|
|
|
size_t count)
|
|
|
|
{
|
2018-08-20 21:27:45 +08:00
|
|
|
int rc;
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
|
2018-08-20 21:27:45 +08:00
|
|
|
rc = process_mask_arg(buf, ap_perms.apm, AP_DEVICES, &ap_perms_mutex);
|
|
|
|
if (rc)
|
|
|
|
return rc;
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
|
|
|
|
ap_bus_revise_bindings();
|
|
|
|
|
|
|
|
return count;
|
|
|
|
}
|
|
|
|
|
|
|
|
static BUS_ATTR_RW(apmask);
|
|
|
|
|
|
|
|
static ssize_t aqmask_show(struct bus_type *bus, char *buf)
|
|
|
|
{
|
|
|
|
int rc;
|
|
|
|
|
|
|
|
if (mutex_lock_interruptible(&ap_perms_mutex))
|
|
|
|
return -ERESTARTSYS;
|
|
|
|
rc = snprintf(buf, PAGE_SIZE,
|
|
|
|
"0x%016lx%016lx%016lx%016lx\n",
|
|
|
|
ap_perms.aqm[0], ap_perms.aqm[1],
|
|
|
|
ap_perms.aqm[2], ap_perms.aqm[3]);
|
|
|
|
mutex_unlock(&ap_perms_mutex);
|
|
|
|
|
|
|
|
return rc;
|
|
|
|
}
|
|
|
|
|
|
|
|
static ssize_t aqmask_store(struct bus_type *bus, const char *buf,
|
|
|
|
size_t count)
|
|
|
|
{
|
2018-08-20 21:27:45 +08:00
|
|
|
int rc;
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
|
2018-08-20 21:27:45 +08:00
|
|
|
rc = process_mask_arg(buf, ap_perms.aqm, AP_DOMAINS, &ap_perms_mutex);
|
|
|
|
if (rc)
|
|
|
|
return rc;
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
|
|
|
|
ap_bus_revise_bindings();
|
|
|
|
|
|
|
|
return count;
|
|
|
|
}
|
|
|
|
|
|
|
|
static BUS_ATTR_RW(aqmask);
|
|
|
|
|
2006-09-20 21:58:25 +08:00
|
|
|
static struct bus_attribute *const ap_bus_attrs[] = {
|
|
|
|
&bus_attr_ap_domain,
|
2013-11-20 17:47:13 +08:00
|
|
|
&bus_attr_ap_control_domain_mask,
|
2016-08-25 17:16:03 +08:00
|
|
|
&bus_attr_ap_usage_domain_mask,
|
2006-09-20 21:58:25 +08:00
|
|
|
&bus_attr_config_time,
|
|
|
|
&bus_attr_poll_thread,
|
2008-12-25 20:38:41 +08:00
|
|
|
&bus_attr_ap_interrupts,
|
2008-07-14 15:59:08 +08:00
|
|
|
&bus_attr_poll_timeout,
|
2015-01-23 20:27:04 +08:00
|
|
|
&bus_attr_ap_max_domain_id,
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
&bus_attr_apmask,
|
|
|
|
&bus_attr_aqmask,
|
2008-07-14 15:59:08 +08:00
|
|
|
NULL,
|
2006-09-20 21:58:25 +08:00
|
|
|
};
|
|
|
|
|
|
|
|
/**
|
2008-04-17 13:46:28 +08:00
|
|
|
* ap_select_domain(): Select an AP domain.
|
|
|
|
*
|
|
|
|
* Pick one of the 16 AP domains.
|
2006-09-20 21:58:25 +08:00
|
|
|
*/
|
2007-02-06 04:18:53 +08:00
|
|
|
static int ap_select_domain(void)
|
2006-09-20 21:58:25 +08:00
|
|
|
{
|
2015-06-26 21:40:41 +08:00
|
|
|
int count, max_count, best_domain;
|
|
|
|
struct ap_queue_status status;
|
|
|
|
int i, j;
|
2006-09-20 21:58:25 +08:00
|
|
|
|
2008-04-17 13:46:28 +08:00
|
|
|
/*
|
2006-09-20 21:58:25 +08:00
|
|
|
* We want to use a single domain. Either the one specified with
|
|
|
|
* the "domain=" parameter or the domain with the maximum number
|
|
|
|
* of devices.
|
|
|
|
*/
|
2016-08-25 17:11:30 +08:00
|
|
|
spin_lock_bh(&ap_domain_lock);
|
|
|
|
if (ap_domain_index >= 0) {
|
2006-09-20 21:58:25 +08:00
|
|
|
/* Domain has already been selected. */
|
2016-08-25 17:11:30 +08:00
|
|
|
spin_unlock_bh(&ap_domain_lock);
|
2006-09-20 21:58:25 +08:00
|
|
|
return 0;
|
2016-08-25 17:11:30 +08:00
|
|
|
}
|
2006-09-20 21:58:25 +08:00
|
|
|
best_domain = -1;
|
|
|
|
max_count = 0;
|
|
|
|
for (i = 0; i < AP_DOMAINS; i++) {
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
if (!ap_test_config_domain(i) ||
|
|
|
|
!test_bit_inv(i, ap_perms.aqm))
|
2012-08-28 22:41:50 +08:00
|
|
|
continue;
|
2006-09-20 21:58:25 +08:00
|
|
|
count = 0;
|
|
|
|
for (j = 0; j < AP_DEVICES; j++) {
|
2012-08-28 22:41:50 +08:00
|
|
|
if (!ap_test_config_card_id(j))
|
|
|
|
continue;
|
2016-11-08 14:09:13 +08:00
|
|
|
status = ap_test_queue(AP_MKQID(j, i),
|
|
|
|
ap_apft_available(),
|
|
|
|
NULL);
|
2015-06-26 21:40:41 +08:00
|
|
|
if (status.response_code != AP_RESPONSE_NORMAL)
|
2006-09-20 21:58:25 +08:00
|
|
|
continue;
|
|
|
|
count++;
|
|
|
|
}
|
|
|
|
if (count > max_count) {
|
|
|
|
max_count = count;
|
|
|
|
best_domain = i;
|
|
|
|
}
|
|
|
|
}
|
2018-08-17 18:36:01 +08:00
|
|
|
if (best_domain >= 0) {
|
2006-09-20 21:58:25 +08:00
|
|
|
ap_domain_index = best_domain;
|
2017-05-12 22:35:14 +08:00
|
|
|
AP_DBF(DBF_DEBUG, "new ap_domain_index=%d\n", ap_domain_index);
|
2016-08-25 17:11:30 +08:00
|
|
|
spin_unlock_bh(&ap_domain_lock);
|
2006-09-20 21:58:25 +08:00
|
|
|
return 0;
|
|
|
|
}
|
2016-08-25 17:11:30 +08:00
|
|
|
spin_unlock_bh(&ap_domain_lock);
|
2006-09-20 21:58:25 +08:00
|
|
|
return -ENODEV;
|
|
|
|
}
|
|
|
|
|
2017-10-16 18:28:35 +08:00
|
|
|
/*
|
|
|
|
* This function checks the type and returns either 0 for not
|
|
|
|
* supported or the highest compatible type value (which may
|
|
|
|
* include the input type value).
|
|
|
|
*/
|
|
|
|
static int ap_get_compatible_type(ap_qid_t qid, int rawtype, unsigned int func)
|
|
|
|
{
|
|
|
|
int comp_type = 0;
|
|
|
|
|
|
|
|
/* < CEX2A is not supported */
|
|
|
|
if (rawtype < AP_DEVICE_TYPE_CEX2A)
|
|
|
|
return 0;
|
|
|
|
/* up to CEX6 known and fully supported */
|
|
|
|
if (rawtype <= AP_DEVICE_TYPE_CEX6)
|
|
|
|
return rawtype;
|
|
|
|
/*
|
|
|
|
* unknown new type > CEX6, check for compatibility
|
|
|
|
* to the highest known and supported type which is
|
|
|
|
* currently CEX6 with the help of the QACT function.
|
|
|
|
*/
|
|
|
|
if (ap_qact_available()) {
|
|
|
|
struct ap_queue_status status;
|
2017-10-30 19:10:54 +08:00
|
|
|
union ap_qact_ap_info apinfo = {0};
|
2017-10-16 18:28:35 +08:00
|
|
|
|
|
|
|
apinfo.mode = (func >> 26) & 0x07;
|
|
|
|
apinfo.cat = AP_DEVICE_TYPE_CEX6;
|
|
|
|
status = ap_qact(qid, 0, &apinfo);
|
|
|
|
if (status.response_code == AP_RESPONSE_NORMAL
|
|
|
|
&& apinfo.cat >= AP_DEVICE_TYPE_CEX2A
|
|
|
|
&& apinfo.cat <= AP_DEVICE_TYPE_CEX6)
|
|
|
|
comp_type = apinfo.cat;
|
|
|
|
}
|
|
|
|
if (!comp_type)
|
|
|
|
AP_DBF(DBF_WARN, "queue=%02x.%04x unable to map type %d\n",
|
|
|
|
AP_QID_CARD(qid), AP_QID_QUEUE(qid), rawtype);
|
|
|
|
else if (comp_type != rawtype)
|
|
|
|
AP_DBF(DBF_INFO, "queue=%02x.%04x map type %d to %d\n",
|
|
|
|
AP_QID_CARD(qid), AP_QID_QUEUE(qid), rawtype, comp_type);
|
|
|
|
return comp_type;
|
|
|
|
}
|
|
|
|
|
2016-08-25 17:16:03 +08:00
|
|
|
/*
|
|
|
|
* helper function to be used with bus_find_dev
|
|
|
|
* matches for the card device with the given id
|
2006-09-20 21:58:25 +08:00
|
|
|
*/
|
2016-08-25 17:16:03 +08:00
|
|
|
static int __match_card_device_with_id(struct device *dev, void *data)
|
2006-09-20 21:58:25 +08:00
|
|
|
{
|
2016-08-25 17:16:03 +08:00
|
|
|
return is_card_dev(dev) && to_ap_card(dev)->id == (int)(long) data;
|
2006-09-20 21:58:25 +08:00
|
|
|
}
|
|
|
|
|
2016-08-25 17:16:03 +08:00
|
|
|
/* helper function to be used with bus_find_dev
|
|
|
|
* matches for the queue device with a given qid
|
|
|
|
*/
|
|
|
|
static int __match_queue_device_with_qid(struct device *dev, void *data)
|
|
|
|
{
|
|
|
|
return is_queue_dev(dev) && to_ap_queue(dev)->qid == (int)(long) data;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ap_scan_bus(): Scan the AP bus for new devices
|
|
|
|
* Runs periodically, workqueue timer (ap_config_time)
|
|
|
|
*/
|
2006-12-07 03:18:20 +08:00
|
|
|
static void ap_scan_bus(struct work_struct *unused)
|
2006-09-20 21:58:25 +08:00
|
|
|
{
|
2016-08-25 17:16:03 +08:00
|
|
|
struct ap_queue *aq;
|
|
|
|
struct ap_card *ac;
|
2006-09-20 21:58:25 +08:00
|
|
|
struct device *dev;
|
|
|
|
ap_qid_t qid;
|
2017-10-16 18:28:35 +08:00
|
|
|
int comp_type, depth = 0, type = 0;
|
|
|
|
unsigned int func = 0;
|
2017-05-12 22:35:14 +08:00
|
|
|
int rc, id, dom, borked, domains, defdomdevs = 0;
|
2006-09-20 21:58:25 +08:00
|
|
|
|
2018-08-17 18:36:01 +08:00
|
|
|
AP_DBF(DBF_DEBUG, "%s running\n", __func__);
|
2016-11-24 13:45:21 +08:00
|
|
|
|
2016-11-08 18:54:28 +08:00
|
|
|
ap_query_configuration(ap_configuration);
|
2015-07-17 19:43:18 +08:00
|
|
|
if (ap_select_domain() != 0)
|
2015-07-23 16:55:59 +08:00
|
|
|
goto out;
|
2015-06-26 22:55:35 +08:00
|
|
|
|
2016-08-25 17:16:03 +08:00
|
|
|
for (id = 0; id < AP_DEVICES; id++) {
|
|
|
|
/* check if device is registered */
|
2006-09-20 21:58:25 +08:00
|
|
|
dev = bus_find_device(&ap_bus_type, NULL,
|
2016-08-25 17:16:03 +08:00
|
|
|
(void *)(long) id,
|
|
|
|
__match_card_device_with_id);
|
|
|
|
ac = dev ? to_ap_card(dev) : NULL;
|
|
|
|
if (!ap_test_config_card_id(id)) {
|
|
|
|
if (dev) {
|
|
|
|
/* Card device has been removed from
|
|
|
|
* configuration, remove the belonging
|
|
|
|
* queue devices.
|
|
|
|
*/
|
|
|
|
bus_for_each_dev(&ap_bus_type, NULL,
|
|
|
|
(void *)(long) id,
|
|
|
|
__ap_queue_devices_with_id_unregister);
|
|
|
|
/* now remove the card device */
|
2015-09-14 23:01:23 +08:00
|
|
|
device_unregister(dev);
|
2016-08-25 17:16:03 +08:00
|
|
|
put_device(dev);
|
|
|
|
}
|
2006-09-20 21:58:25 +08:00
|
|
|
continue;
|
|
|
|
}
|
2016-08-25 17:16:03 +08:00
|
|
|
/* According to the configuration there should be a card
|
|
|
|
* device, so check if there is at least one valid queue
|
|
|
|
* and maybe create queue devices and the card device.
|
|
|
|
*/
|
|
|
|
domains = 0;
|
|
|
|
for (dom = 0; dom < AP_DOMAINS; dom++) {
|
|
|
|
qid = AP_MKQID(id, dom);
|
|
|
|
dev = bus_find_device(&ap_bus_type, NULL,
|
|
|
|
(void *)(long) qid,
|
|
|
|
__match_queue_device_with_qid);
|
|
|
|
aq = dev ? to_ap_queue(dev) : NULL;
|
|
|
|
if (!ap_test_config_domain(dom)) {
|
|
|
|
if (dev) {
|
|
|
|
/* Queue device exists but has been
|
|
|
|
* removed from configuration.
|
|
|
|
*/
|
|
|
|
device_unregister(dev);
|
|
|
|
put_device(dev);
|
|
|
|
}
|
|
|
|
continue;
|
|
|
|
}
|
2017-10-16 18:28:35 +08:00
|
|
|
rc = ap_query_queue(qid, &depth, &type, &func);
|
2016-08-25 17:16:03 +08:00
|
|
|
if (dev) {
|
|
|
|
spin_lock_bh(&aq->lock);
|
|
|
|
if (rc == -ENODEV ||
|
|
|
|
/* adapter reconfiguration */
|
2017-10-16 18:28:35 +08:00
|
|
|
(ac && ac->functions != func))
|
2016-08-25 17:16:03 +08:00
|
|
|
aq->state = AP_STATE_BORKED;
|
|
|
|
borked = aq->state == AP_STATE_BORKED;
|
|
|
|
spin_unlock_bh(&aq->lock);
|
|
|
|
if (borked) /* Remove broken device */
|
|
|
|
device_unregister(dev);
|
|
|
|
put_device(dev);
|
|
|
|
if (!borked) {
|
|
|
|
domains++;
|
2017-05-12 22:35:14 +08:00
|
|
|
if (dom == ap_domain_index)
|
|
|
|
defdomdevs++;
|
2016-08-25 17:16:03 +08:00
|
|
|
continue;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if (rc)
|
|
|
|
continue;
|
2017-10-16 18:28:35 +08:00
|
|
|
/* a new queue device is needed, check out comp type */
|
|
|
|
comp_type = ap_get_compatible_type(qid, type, func);
|
|
|
|
if (!comp_type)
|
|
|
|
continue;
|
|
|
|
/* maybe a card device needs to be created first */
|
2016-08-25 17:16:03 +08:00
|
|
|
if (!ac) {
|
2017-10-16 18:28:35 +08:00
|
|
|
ac = ap_card_create(id, depth, type,
|
|
|
|
comp_type, func);
|
2016-08-25 17:16:03 +08:00
|
|
|
if (!ac)
|
|
|
|
continue;
|
|
|
|
ac->ap_dev.device.bus = &ap_bus_type;
|
|
|
|
ac->ap_dev.device.parent = ap_root_device;
|
|
|
|
dev_set_name(&ac->ap_dev.device,
|
|
|
|
"card%02x", id);
|
|
|
|
/* Register card with AP bus */
|
|
|
|
rc = device_register(&ac->ap_dev.device);
|
|
|
|
if (rc) {
|
|
|
|
put_device(&ac->ap_dev.device);
|
|
|
|
ac = NULL;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
/* get it and thus adjust reference counter */
|
|
|
|
get_device(&ac->ap_dev.device);
|
|
|
|
}
|
|
|
|
/* now create the new queue device */
|
2017-10-16 18:28:35 +08:00
|
|
|
aq = ap_queue_create(qid, comp_type);
|
2016-08-25 17:16:03 +08:00
|
|
|
if (!aq)
|
|
|
|
continue;
|
|
|
|
aq->card = ac;
|
|
|
|
aq->ap_dev.device.bus = &ap_bus_type;
|
|
|
|
aq->ap_dev.device.parent = &ac->ap_dev.device;
|
|
|
|
dev_set_name(&aq->ap_dev.device,
|
|
|
|
"%02x.%04x", id, dom);
|
|
|
|
/* Start with a device reset */
|
|
|
|
spin_lock_bh(&aq->lock);
|
|
|
|
ap_wait(ap_sm_event(aq, AP_EVENT_POLL));
|
|
|
|
spin_unlock_bh(&aq->lock);
|
|
|
|
/* Register device */
|
|
|
|
rc = device_register(&aq->ap_dev.device);
|
|
|
|
if (rc) {
|
|
|
|
put_device(&aq->ap_dev.device);
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
domains++;
|
2017-05-12 22:35:14 +08:00
|
|
|
if (dom == ap_domain_index)
|
|
|
|
defdomdevs++;
|
2016-08-25 17:16:03 +08:00
|
|
|
} /* end domain loop */
|
|
|
|
if (ac) {
|
|
|
|
/* remove card dev if there are no queue devices */
|
|
|
|
if (!domains)
|
|
|
|
device_unregister(&ac->ap_dev.device);
|
|
|
|
put_device(&ac->ap_dev.device);
|
2015-09-14 23:01:23 +08:00
|
|
|
}
|
2016-08-25 17:16:03 +08:00
|
|
|
} /* end device loop */
|
2017-05-12 22:35:14 +08:00
|
|
|
|
|
|
|
if (defdomdevs < 1)
|
2018-08-17 18:36:01 +08:00
|
|
|
AP_DBF(DBF_INFO,
|
|
|
|
"no queue device with default domain %d available\n",
|
2017-05-12 22:35:14 +08:00
|
|
|
ap_domain_index);
|
|
|
|
|
2015-07-23 16:55:59 +08:00
|
|
|
out:
|
|
|
|
mod_timer(&ap_config_timer, jiffies + ap_config_time * HZ);
|
2006-09-20 21:58:25 +08:00
|
|
|
}
|
|
|
|
|
2017-10-25 18:27:37 +08:00
|
|
|
static void ap_config_timeout(struct timer_list *unused)
|
2006-09-20 21:58:25 +08:00
|
|
|
{
|
2015-07-17 19:43:18 +08:00
|
|
|
if (ap_suspend_flag)
|
|
|
|
return;
|
2015-07-27 18:47:40 +08:00
|
|
|
queue_work(system_long_wq, &ap_scan_work);
|
2006-09-20 21:58:25 +08:00
|
|
|
}
|
2006-12-16 00:18:17 +08:00
|
|
|
|
2018-04-04 13:14:17 +08:00
|
|
|
static int __init ap_debug_init(void)
|
2016-11-24 13:45:21 +08:00
|
|
|
{
|
|
|
|
ap_dbf_info = debug_register("ap", 1, 1,
|
|
|
|
DBF_MAX_SPRINTF_ARGS * sizeof(long));
|
|
|
|
debug_register_view(ap_dbf_info, &debug_sprintf_view);
|
|
|
|
debug_set_level(ap_dbf_info, DBF_ERR);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
static void __init ap_perms_init(void)
|
|
|
|
{
|
2018-08-20 21:27:45 +08:00
|
|
|
/* all resources useable if no kernel parameter string given */
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
memset(&ap_perms.apm, 0xFF, sizeof(ap_perms.apm));
|
|
|
|
memset(&ap_perms.aqm, 0xFF, sizeof(ap_perms.aqm));
|
|
|
|
|
2018-08-20 21:27:45 +08:00
|
|
|
/* apm kernel parameter string */
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
if (apm_str) {
|
2018-08-20 21:27:45 +08:00
|
|
|
memset(&ap_perms.apm, 0, sizeof(ap_perms.apm));
|
|
|
|
process_mask_arg(apm_str, ap_perms.apm, AP_DEVICES,
|
|
|
|
&ap_perms_mutex);
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
}
|
|
|
|
|
2018-08-20 21:27:45 +08:00
|
|
|
/* aqm kernel parameter string */
|
|
|
|
if (aqm_str) {
|
|
|
|
memset(&ap_perms.aqm, 0, sizeof(ap_perms.aqm));
|
|
|
|
process_mask_arg(aqm_str, ap_perms.aqm, AP_DOMAINS,
|
|
|
|
&ap_perms_mutex);
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2006-09-20 21:58:25 +08:00
|
|
|
/**
|
2008-04-17 13:46:28 +08:00
|
|
|
* ap_module_init(): The module initialization code.
|
|
|
|
*
|
|
|
|
* Initializes the module.
|
2006-09-20 21:58:25 +08:00
|
|
|
*/
|
2018-04-04 13:14:17 +08:00
|
|
|
static int __init ap_module_init(void)
|
2006-09-20 21:58:25 +08:00
|
|
|
{
|
2015-06-26 22:55:35 +08:00
|
|
|
int max_domain_id;
|
2006-09-20 21:58:25 +08:00
|
|
|
int rc, i;
|
|
|
|
|
2016-11-24 13:45:21 +08:00
|
|
|
rc = ap_debug_init();
|
|
|
|
if (rc)
|
|
|
|
return rc;
|
|
|
|
|
2018-08-09 17:59:34 +08:00
|
|
|
if (!ap_instructions_available()) {
|
2015-06-26 22:55:35 +08:00
|
|
|
pr_warn("The hardware system does not support AP instructions\n");
|
|
|
|
return -ENODEV;
|
|
|
|
}
|
|
|
|
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
/* set up the AP permissions (ap and aq masks) */
|
|
|
|
ap_perms_init();
|
|
|
|
|
2015-06-26 22:55:35 +08:00
|
|
|
/* Get AP configuration data if available */
|
|
|
|
ap_init_configuration();
|
|
|
|
|
|
|
|
if (ap_configuration)
|
2017-05-12 22:35:14 +08:00
|
|
|
max_domain_id =
|
|
|
|
ap_max_domain_id ? ap_max_domain_id : AP_DOMAINS - 1;
|
2015-06-26 22:55:35 +08:00
|
|
|
else
|
|
|
|
max_domain_id = 15;
|
s390/zcrypt: AP bus support for alternate driver(s)
The current AP bus, AP devices and AP device drivers implementation
uses a clearly defined mapping for binding AP devices to AP device
drivers. So for example a CEX6C queue will always be bound to the
cex4queue device driver.
The Linux Device Driver model has no sensitivity for more than one
device driver eligible for one device type. If there exist more than
one drivers matching to the device type, simple all drivers are tried
consecutively. There is no way to determine and influence the probing
order of the drivers.
With KVM there is a need to provide additional device drivers matching
to the very same type of AP devices. With a simple implementation the
KVM drivers run in competition to the regular drivers. Whichever
'wins' a device depends on build order and implementation details
within the common Linux Device Driver Model and is not
deterministic. However, a userspace process could figure out which
device should be bound to which driver and sort out the correct
binding by manipulating attributes in the sysfs.
If for security reasons a AP device must not get bound to the 'wrong'
device driver the sorting out has to be done within the Linux kernel
by the AP bus code. This patch modifies the behavior of the AP bus
for probing drivers for devices in a way that two sets of drivers are
usable. Two new bitmasks 'apmask' and 'aqmask' are used to mark a
subset of the APQN range for 'usable by the ap bus and the default
drivers' or 'not usable by the default drivers and thus available for
alternate drivers like vfio-xxx'. So an APQN which is addressed by
this masking only the default drivers will be probed. In contrary an
APQN which is not addressed by the masks will never be probed and
bound to default drivers but onny to alternate drivers.
Eventually the two masks give a way to divide the range of APQNs into
two pools: one pool of APQNs used by the AP bus and the default
drivers and thus via zcrypt drivers available to the userspace of the
system. And another pool where no zcrypt drivers are bound to and
which can be used by alternate drivers (like vfio-xxx) for their
needs. This division is hot-plug save and makes sure a APQN assigned
to an alternate driver is at no time somehow exploitable by the wrong
party.
The two masks are located in sysfs at /sys/bus/ap/apmask and
/sys/bus/ap/aqmask. The mask syntax is exactly the same as the
already existing mask attributes in the /sys/bus/ap directory (for
example ap_usage_domain_mask and ap_control_domain_mask).
By default all APQNs belong to the ap bus and the default drivers:
cat /sys/bus/ap/apmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
cat /sys/bus/ap/aqmask
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
The masks can be changed at boot time with the kernel command line
like this:
... ap.apmask=0xffff ap.aqmask=0x40
This would give these two pools:
default drivers pool: adapter 0 - 15, domain 1
alternate drivers pool: adapter 0 - 15, all but domain 1
adapter 16-255, all domains
The sysfs attributes for this two masks are writeable and an
administrator is able to reconfigure the assignements on the fly by
writing new mask values into. With changing the mask(s) a revision of
the existing queue to driver bindings is done. So all APQNs which are
bound to the 'wrong' driver are reprobed via kernel function
device_reprobe() and thus the new correct driver will be assigned with
respect of the changed apmask and aqmask bits.
The mask values are bitmaps in big endian order starting with bit 0.
So adapter number 0 is the leftmost bit, mask is 0x8000... The sysfs
attributes accept 2 different formats:
- Absolute hex string starting with 0x like "0x12345678" does set
the mask starting from left to right. If the given string is shorter
than the mask it is padded with 0s on the right. If the string is
longer than the mask an error comes back (EINVAL).
- '+' or '-' followed by a numerical value. Valid examples are "+1",
"-13", "+0x41", "-0xff" and even "+0" and "-0". Only the addressed
bit in the mask is switched on ('+') or off ('-').
This patch will also be the base for an upcoming extension to the
zcrypt drivers to be able to provide additional zcrypt device nodes
with filtering based on ap and aq masks.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2018-07-20 14:36:53 +08:00
|
|
|
if (ap_domain_index < -1 || ap_domain_index > max_domain_id ||
|
|
|
|
(ap_domain_index >= 0 &&
|
|
|
|
!test_bit_inv(ap_domain_index, ap_perms.aqm))) {
|
2015-06-26 22:55:35 +08:00
|
|
|
pr_warn("%d is not a valid cryptographic domain\n",
|
|
|
|
ap_domain_index);
|
2017-05-12 22:35:14 +08:00
|
|
|
ap_domain_index = -1;
|
2006-09-20 21:58:25 +08:00
|
|
|
}
|
2009-09-23 04:58:51 +08:00
|
|
|
/* In resume callback we need to know if the user had set the domain.
|
|
|
|
* If so, we can not just reset it.
|
|
|
|
*/
|
|
|
|
if (ap_domain_index >= 0)
|
|
|
|
user_set_domain = 1;
|
|
|
|
|
2008-12-25 20:38:41 +08:00
|
|
|
if (ap_interrupts_available()) {
|
2013-06-24 16:30:41 +08:00
|
|
|
rc = register_adapter_interrupt(&ap_airq);
|
|
|
|
ap_airq_flag = (rc == 0);
|
2008-12-25 20:38:41 +08:00
|
|
|
}
|
|
|
|
|
2006-09-20 21:58:25 +08:00
|
|
|
/* Create /sys/bus/ap. */
|
|
|
|
rc = bus_register(&ap_bus_type);
|
|
|
|
if (rc)
|
|
|
|
goto out;
|
|
|
|
for (i = 0; ap_bus_attrs[i]; i++) {
|
|
|
|
rc = bus_create_file(&ap_bus_type, ap_bus_attrs[i]);
|
|
|
|
if (rc)
|
|
|
|
goto out_bus;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Create /sys/devices/ap. */
|
2008-12-15 20:58:29 +08:00
|
|
|
ap_root_device = root_device_register("ap");
|
2018-07-19 12:42:05 +08:00
|
|
|
rc = PTR_ERR_OR_ZERO(ap_root_device);
|
2006-09-20 21:58:25 +08:00
|
|
|
if (rc)
|
|
|
|
goto out_bus;
|
|
|
|
|
2008-04-17 13:46:28 +08:00
|
|
|
/* Setup the AP bus rescan timer. */
|
2017-10-25 18:27:37 +08:00
|
|
|
timer_setup(&ap_config_timer, ap_config_timeout, 0);
|
2006-09-20 21:58:25 +08:00
|
|
|
|
2015-09-14 23:01:23 +08:00
|
|
|
/*
|
|
|
|
* Setup the high resultion poll timer.
|
2008-07-14 15:59:08 +08:00
|
|
|
* If we are running under z/VM adjust polling to z/VM polling rate.
|
|
|
|
*/
|
|
|
|
if (MACHINE_IS_VM)
|
|
|
|
poll_timeout = 1500000;
|
2009-12-07 19:52:00 +08:00
|
|
|
spin_lock_init(&ap_poll_timer_lock);
|
2008-07-14 15:59:08 +08:00
|
|
|
hrtimer_init(&ap_poll_timer, CLOCK_MONOTONIC, HRTIMER_MODE_ABS);
|
|
|
|
ap_poll_timer.function = ap_poll_timeout;
|
|
|
|
|
2006-09-20 21:58:25 +08:00
|
|
|
/* Start the low priority AP bus poll thread. */
|
|
|
|
if (ap_thread_flag) {
|
|
|
|
rc = ap_poll_thread_start();
|
|
|
|
if (rc)
|
|
|
|
goto out_work;
|
|
|
|
}
|
|
|
|
|
2015-07-17 19:43:18 +08:00
|
|
|
rc = register_pm_notifier(&ap_power_notifier);
|
|
|
|
if (rc)
|
|
|
|
goto out_pm;
|
|
|
|
|
2015-07-27 18:47:40 +08:00
|
|
|
queue_work(system_long_wq, &ap_scan_work);
|
s390/zcrypt: Fix kernel crash on systems without AP bus support
On systems without AP bus (e.g. KVM) the kernel crashes during init
calls when zcrypt is built-in:
kernel BUG at drivers/base/driver.c:153!
illegal operation: 0001 ilc:1 [#1] SMP
Modules linked in:
CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.2.0+ #221
task: 0000000010a40000 ti: 0000000010a48000 task.ti:0000000010a48000
Krnl PSW : 0704c00180000000 0000000000592bd6(driver_register+0x106/0x140)
R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 EA:3
0000000000000012 0000000000000000 0000000000c45328 0000000000c44e30
00000000009ef63c 000000000067f598 0000000000cf3c58 0000000000000000
000000000000007b 0000000000cb1030 0000000000000002 0000000000000000
0000000000ca8580 0000000010306700 00000000001001d8 0000000010a4bd88
Krnl Code: 0000000000592bc6: f0b00004ebcf srp 4(12,%r0),3023(%r14),0
0000000000592bcc: f0a0000407f4 srp 4(11,%r0),2036,0
#0000000000592bd2: a7f40001 brc 15,592bd4
>0000000000592bd6: e330d0000004 lg %r3,0(%r13)
0000000000592bdc: c0200021edfd larl %r2,9d07d6
0000000000592be2: c0e500126d8f brasl %r14,7e0700
0000000000592be8: e330d0080004 lg %r3,8(%r13)
0000000000592bee: a7f4ffab brc 15,592b44
Call Trace:
([<00000000001001c8>] do_one_initcall+0x90/0x1d0)
[<0000000000c6dd34>] kernel_init_freeable+0x1e4/0x2a0
[<00000000007db53a>] kernel_init+0x2a/0x120
[<00000000007e8ece>] kernel_thread_starter+0x6/0xc
[<00000000007e8ec8>] kernel_thread_starter+0x0/0xc
Last Breaking-Event-Address:
[<0000000000592bd2>] driver_register+0x102/0x140
When zcrypt is built as a module, the module loader ensures that the
driver modules cannot be loaded if the AP bus module returns an error
during initialisation. But if zcrypt and the driver are built-in, the
driver is getting initialised even if the AP bus initialisation
failed. The driver invokes ap_driver_register() during initialisation,
which then causes operations on uninitialised data structures to be
performed.
Explicitly protect ap_driver_register() by introducing an
"initialised" flag that gets set iff the AP bus initialisation was
successful. When the AP bus initialisation failed,
ap_driver_register() will error out with -ENODEV, causing the driver
initialisation to fail as well.
Test results:
1. Inside KVM (no AP bus), zcrypt built-in
Boots. /sys/bus/ap not present (expected).
2. Inside KVM (no AP bus), zcrypt as module
Boots. Loading zcrypt_cex4 fails because loading ap_bus fails
(expected).
3. On LPAR with CEX5, zcrypt built-in
Boots. /sys/bus/ap/devices/card* present but .../card*/type missing
(i.e. zcrypt_device_register() fails, unrelated issue).
4. On LPAR with CEX5, zcrypt as module
Boots. Loading zcrypt_cex4 successful,
/sys/bus/ap/devices/card*/type present. No further testing
(user-space functionality) was done.
Signed-off-by: Sascha Silbe <silbe@linux.vnet.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
2015-10-28 01:29:52 +08:00
|
|
|
initialised = true;
|
2015-09-14 23:01:23 +08:00
|
|
|
|
2006-09-20 21:58:25 +08:00
|
|
|
return 0;
|
|
|
|
|
2015-07-17 19:43:18 +08:00
|
|
|
out_pm:
|
|
|
|
ap_poll_thread_stop();
|
2006-09-20 21:58:25 +08:00
|
|
|
out_work:
|
2008-07-14 15:59:08 +08:00
|
|
|
hrtimer_cancel(&ap_poll_timer);
|
2008-12-15 20:58:29 +08:00
|
|
|
root_device_unregister(ap_root_device);
|
2006-09-20 21:58:25 +08:00
|
|
|
out_bus:
|
|
|
|
while (i--)
|
|
|
|
bus_remove_file(&ap_bus_type, ap_bus_attrs[i]);
|
|
|
|
bus_unregister(&ap_bus_type);
|
|
|
|
out:
|
2013-06-24 16:30:41 +08:00
|
|
|
if (ap_using_interrupts())
|
|
|
|
unregister_adapter_interrupt(&ap_airq);
|
2015-06-26 22:55:35 +08:00
|
|
|
kfree(ap_configuration);
|
2006-09-20 21:58:25 +08:00
|
|
|
return rc;
|
|
|
|
}
|
2017-02-09 22:48:10 +08:00
|
|
|
device_initcall(ap_module_init);
|