Received: by 2002:ac0:8c9a:0:0:0:0:0 with SMTP id r26csp231588ima; Thu, 31 Jan 2019 15:35:54 -0800 (PST) X-Google-Smtp-Source: AHgI3IZ9UQGSRy2euFoVBTzDPz+vy+wDvRaMP2BssU5ff8LVt3ssjs0cJej+3S+xV16B/QRgtdIO X-Received: by 2002:a63:5518:: with SMTP id j24mr285pgb.208.1548977753959; Thu, 31 Jan 2019 15:35:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548977753; cv=none; d=google.com; s=arc-20160816; b=Yz62z3P3NE3m1pIddMv2XR19sMlPmo4ISEJQZJ0U+hxNSR3T+WqPFkEos0tQ2Ygf8m jCz/zI6mw5xy08vpRjRn5HxLEU7CvyU+X2yXpt9o0AUMM0zHRYShToVP2zjtEYKs5f+B JtwI/aiOrEeAd/2ilKpElesJNIaxfuViFDWD/T7qhkvHMRNZTqOjfAlfH6eH/+dUPklZ X/fiU1me64zJWy2uCUMPCTet1oQtVsFnEYKW+xmLknhWhnBI9f2y+im6QlzbS01K+FXr vwajcmHLTLz6kY13cQM1iLSKkobdK3IfqmCx3nmpEG5oM7q5KLWycb4gRrBRhl+gVFXX 1GrQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date:from :references:cc:to:subject; bh=3pxkisUn3kAiBc+PI2XKAZxE51nDWoQ1AbeSp2gotho=; b=wOzuShnsEGB9qfkyx61SaQctuhIxhkMWbkkXRo0wuG5TNgehDR7GS7Yku++OyPR5Ax 63fEVgLU7qcAt2sfFzl3ZdW+EjHdZmlegtFO1/17EQOobXHGSDsyPu1eNPigordkK0Al lu+eB8OBUkQ/JXRXdCQkmAC5dJbrV1p7GR2uAtM616ZBRq0Le0dQpD68PdDi6jS4jX8K 81sU8K5VnqIlD1DERQrElX9Y7A/kzFvO6sO2Sc2Ahleg5zvT2X6Owd4Au5dX/ZCRmyOp wXJSQFSu6FHMLQH6x/waiFLRKwsbvpZovLIuk4aLUpUF7WV+e3TZpp40lAtdjYYXkaIx kXOQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a18si4930844pgj.77.2019.01.31.15.35.39; Thu, 31 Jan 2019 15:35:53 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727621AbfAaXcn (ORCPT + 99 others); Thu, 31 Jan 2019 18:32:43 -0500 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:44940 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725915AbfAaXcm (ORCPT ); Thu, 31 Jan 2019 18:32:42 -0500 Received: from pps.filterd (m0098393.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x0VNSoRe055384 for ; Thu, 31 Jan 2019 18:32:41 -0500 Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by mx0a-001b2d01.pphosted.com with ESMTP id 2qcaq205k5-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 31 Jan 2019 18:32:41 -0500 Received: from localhost by e32.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 31 Jan 2019 23:32:40 -0000 Received: from b03cxnp08026.gho.boulder.ibm.com (9.17.130.18) by e32.co.us.ibm.com (192.168.1.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Thu, 31 Jan 2019 23:32:37 -0000 Received: from b03ledav002.gho.boulder.ibm.com (b03ledav002.gho.boulder.ibm.com [9.17.130.233]) by b03cxnp08026.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x0VNWWjU18284726 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 31 Jan 2019 23:32:32 GMT Received: from b03ledav002.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 7779513604F; Thu, 31 Jan 2019 23:32:32 +0000 (GMT) Received: from b03ledav002.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id F401A136055; Thu, 31 Jan 2019 23:32:30 +0000 (GMT) Received: from [9.80.226.197] (unknown [9.80.226.197]) by b03ledav002.gho.boulder.ibm.com (Postfix) with ESMTP; Thu, 31 Jan 2019 23:32:30 +0000 (GMT) Subject: Re: [PATCH] zcrypt: handle AP Info notification from CHSC SEI command To: pmorel@linux.ibm.com, linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org Cc: schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com, sebott@linux.ibm.com, oberpar@linux.ibm.com, freude@linux.ibm.com, pasic@linux.ibm.com, cohuck@redhat.com References: <1548870526-30595-1-git-send-email-akrowiak@linux.ibm.com> <95a29dd5-11d5-0984-ffbd-73ef92ed1aba@linux.ibm.com> From: Tony Krowiak Date: Thu, 31 Jan 2019 18:32:30 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <95a29dd5-11d5-0984-ffbd-73ef92ed1aba@linux.ibm.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TM-AS-GCONF: 00 x-cbid: 19013123-0004-0000-0000-000014DAD8FF X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00010512; HX=3.00000242; KW=3.00000007; PH=3.00000004; SC=3.00000277; SDB=6.01154551; UDB=6.00602056; IPR=6.00934983; MB=3.00025380; MTD=3.00000008; XFM=3.00000015; UTC=2019-01-31 23:32:39 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19013123-0005-0000-0000-00008A6E42B5 Message-Id: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-01-31_13:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1901310169 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/31/19 4:09 AM, Pierre Morel wrote: > On 30/01/2019 18:48, Tony Krowiak wrote: >> The current AP bus implementation periodically polls the AP configuration >> to detect changes. When the AP configuration is dynamically changed >> via the >> SE or an SCLP instruction, the changes will not be reflected to sysfs >> until >> the next time the AP configuration is polled. The CHSC architecture >> provides a Store Event Information (SEI)command to make notification >> of an >> AP configuration change. This patch introduces a handler to process >> notification from the CHSC SEI command BY immediately kickING off an >> AP bus >> scan. >> >> Signed-off-by: Tony Krowiak >> Reviewed-by: Halil Pasic >> --- >>   arch/s390/include/asm/ap.h   | 12 ++++++++++++ >>   drivers/s390/cio/chsc.c      | 12 ++++++++++++ >>   drivers/s390/cio/chsc.h      |  1 + >>   drivers/s390/crypto/ap_bus.c | 12 ++++++++++++ >>   4 files changed, 37 insertions(+) >> >> diff --git a/arch/s390/include/asm/ap.h b/arch/s390/include/asm/ap.h >> index 1a6a7092d942..c778593d509f 100644 >> --- a/arch/s390/include/asm/ap.h >> +++ b/arch/s390/include/asm/ap.h >> @@ -360,4 +360,16 @@ static inline struct ap_queue_status >> ap_dqap(ap_qid_t qid, >>       return reg1; >>   } >> +/* >> + * Interface to tell the AP bus code that a configuration >> + * change has happened. The bus code should at least do >> + * an ap bus resource rescan. >> + */ >> +#if IS_ENABLED(CONFIG_ZCRYPT) >> +void ap_bus_cfg_chg(void); >> +#else >> +#error "no CONFIG_ZCRYPT" >> +static void ap_bus_cfg_chg(void){}; >> +#endif >> + >>   #endif /* _ASM_S390_AP_H_ */ >> diff --git a/drivers/s390/cio/chsc.c b/drivers/s390/cio/chsc.c >> index a0baee25134c..dccccc337078 100644 >> --- a/drivers/s390/cio/chsc.c >> +++ b/drivers/s390/cio/chsc.c >> @@ -586,6 +586,15 @@ static void chsc_process_sei_scm_avail(struct >> chsc_sei_nt0_area *sei_area) >>                     " failed (rc=%d).\n", ret); >>   } >> +static void chsc_process_sei_ap_cfg_chg(struct chsc_sei_nt0_area >> *sei_area) >> +{ >> +    CIO_CRW_EVENT(3, "chsc: ap config changed\n"); >> +    if (sei_area->rs != 5) > > Why just return if the rs code is 5? > > The event content code concerns the AP configuration change. > > Should the source of the reporting of this change hold us from > rescanning the available AP? Why rescan if the RS code does not indicate the AP configuration changed? > > > Regards, > Pierre > > >> +        return; >> + >> +    ap_bus_cfg_chg(); >> +} >> + >>   static void chsc_process_sei_nt2(struct chsc_sei_nt2_area *sei_area) >>   { >>       switch (sei_area->cc) { >> @@ -612,6 +621,9 @@ static void chsc_process_sei_nt0(struct >> chsc_sei_nt0_area *sei_area) >>       case 2: /* i/o resource accessibility */ >>           chsc_process_sei_res_acc(sei_area); >>           break; >> +    case 3: /* ap config changed */ >> +        chsc_process_sei_ap_cfg_chg(sei_area); >> +        break; >>       case 7: /* channel-path-availability information */ >>           chsc_process_sei_chp_avail(sei_area); >>           break; >> diff --git a/drivers/s390/cio/chsc.h b/drivers/s390/cio/chsc.h >> index 78aba8d94eec..5651066c46e3 100644 >> --- a/drivers/s390/cio/chsc.h >> +++ b/drivers/s390/cio/chsc.h >> @@ -9,6 +9,7 @@ >>   #include >>   #include >>   #include >> +#include >>   #define CHSC_SDA_OC_MSS   0x2 >> diff --git a/drivers/s390/crypto/ap_bus.c b/drivers/s390/crypto/ap_bus.c >> index 48ea0004a56d..94f621783d6b 100644 >> --- a/drivers/s390/crypto/ap_bus.c >> +++ b/drivers/s390/crypto/ap_bus.c >> @@ -35,6 +35,7 @@ >>   #include >>   #include >>   #include >> +#include >>   #include "ap_bus.h" >>   #include "ap_debug.h" >> @@ -860,6 +861,17 @@ void ap_bus_force_rescan(void) >>   EXPORT_SYMBOL(ap_bus_force_rescan); >>   /* >> +* A config change has happened, Force an ap bus rescan. >> +*/ >> +void ap_bus_cfg_chg(void) >> +{ >> +    AP_DBF(DBF_INFO, "%s config change, forcing bus rescan\n", >> __func__); >> + >> +    ap_bus_force_rescan(); >> +} >> +EXPORT_SYMBOL(ap_bus_cfg_chg); >> + >> +/* >>    * 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 >> > >