On Thu, 26 Jul 2018 21:54:13 +0200 Christian Borntraeger <borntraeger@xxxxxxxxxx> wrote: > From: Harald Freudenberger <freude@xxxxxxxxxxxxx> > > This patch enables modifications of the apmask and aqmask on a live > system. Until now these both masks are read-only on a live system. The > only way to change these masks was via kernel command line parameter. > > This patch makes the sysfs attributes /sys/bus/ap/apmask and > /sys/bus/ap/aqmask writeable by root. 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 expected input for those attributes needs to be documented. IIRC the vfio-ap driver does not support device removal in the first shot. So, what happens if an APQN is added to the reserved set? BUG()? > > Signed-off-by: Harald Freudenberger <freude@xxxxxxxxxxxxx> > Signed-off-by: Christian Borntraeger <borntraeger@xxxxxxxxxx> > --- > drivers/s390/crypto/ap_bus.c | 153 ++++++++++++++++++++++++++++++++--- > 1 file changed, 143 insertions(+), 10 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-s390" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
