Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp2832760iog; Mon, 20 Jun 2022 05:55:12 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tVmMBoBL4rJswVPVjwhbH2EXcquBanja4mizpeWyWnWCz5M7oqA8bmZB6CnXYIqsUTcEN1 X-Received: by 2002:a17:907:7f16:b0:722:d5ee:ff2e with SMTP id qf22-20020a1709077f1600b00722d5eeff2emr1033274ejc.454.1655729712325; Mon, 20 Jun 2022 05:55:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1655729712; cv=none; d=google.com; s=arc-20160816; b=oj67kHrnf4Q4ECBcf7ALPWGcMsNOWvfJlFHjAFW12tKnwxnOiuv5GgnfmoEd+GOC4H STpZtuq0b4+0RuwVxYUs0esvIUTerG1TxZR3IeWZzlYXfatEOjLqJm83zhXskVLCqWYH l56Dgs1/h8/BF9RHX/hkyDm249LTdrJTUQWWWrF7020PLwdQq5BXZn6keVh91Z5UYxzK iR5nfx964t99GvI8fjxRdOUX7cFu1a3A4y2VC8sEUBrHdqibmTF6wug+bm6NBwWsD8Ma ySBdpeY1X+hMqntNli27vfkf80nG6vXRKaMIMCpHGUSWBFhbr/CgdxOsBClMAbgWHlRY bwhQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=3DwiYxmDd0APKvshXNHFVRSOuNmyc0gCYDA2b4ZZ0Ko=; b=uJINKvPuOCSD0dmy6cn1wir03SOyAKcCUFozYIrirQYPaU8PcpUOOzeBIfPFHTu8cE Uh7wm04Mal7c8wd7zHtAoCUgjh/rf6vVP5Y/wi1HYIHUFCDxwddlPto5vYW8K0zVQwxz ehitQtddGuP2Mj6hl1VE0mhZgC4Uu+dyUe0nGQ56ClHpfbRpT+PrVFIxxYR+xZmCBU98 nABtiTasOvm4EmDH8FAGQ/jSCmnI/SkewPyZRh2gb3Sk1ayJIZoq5nG3gGkRh8GZ3B15 Xy0IR+BuDYvYPoirz4ObPO8Jd4OsmwaoryQPC5HXd4gieC1o2RFSrYzdJz7o0XERmNrm FARg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ibm.com header.s=pp1 header.b=eAE0vqYu; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id p4-20020aa7c884000000b004358f57d80asi696729eds.452.2022.06.20.05.54.46; Mon, 20 Jun 2022 05:55:12 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@ibm.com header.s=pp1 header.b=eAE0vqYu; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241509AbiFTMu0 (ORCPT + 99 others); Mon, 20 Jun 2022 08:50:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:32990 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229690AbiFTMuX (ORCPT ); Mon, 20 Jun 2022 08:50:23 -0400 Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0FC672C3; Mon, 20 Jun 2022 05:50:23 -0700 (PDT) Received: from pps.filterd (m0098409.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 25KC5TMV032767; Mon, 20 Jun 2022 12:50:22 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ibm.com; h=from : to : cc : subject : date : message-id : mime-version : content-transfer-encoding; s=pp1; bh=3DwiYxmDd0APKvshXNHFVRSOuNmyc0gCYDA2b4ZZ0Ko=; b=eAE0vqYuyfxAtBXbfMIe43s3jPuedwhtkdUsloWHG+6h+hofOcYqX0m4TNovt99Jb/Dy wOHKj2LlEndML7N11ujJiteVaEWC7ao2c4Wc/q3TmRZk3VHTiH/5QlQJtK66IXlGZXzI OxFdTlHFEawsf7aUQ+vQ/Ya/xt+Cz7O6nZTTUvc9/ystq5/slZDDHAjrpw0o3FLeBMyw 2W0HbNkMQC73NB6agojjFq7XCkNWC8TheyMcmGgS8ssv92aNNKt6Bc4+q0ax29JNI03J 38lEKF1VVM+7UCKFYIm4JIu6C1M0oj2S9D03rurCHcwd7hFa5kxVHB+DI/p5TWAKCFXz bg== Received: from pps.reinject (localhost [127.0.0.1]) by mx0a-001b2d01.pphosted.com (PPS) with ESMTPS id 3gsr0uhgme-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 20 Jun 2022 12:50:22 +0000 Received: from m0098409.ppops.net (m0098409.ppops.net [127.0.0.1]) by pps.reinject (8.17.1.5/8.17.1.5) with ESMTP id 25KCVBbT004832; Mon, 20 Jun 2022 12:50:22 GMT Received: from ppma02fra.de.ibm.com (47.49.7a9f.ip4.static.sl-reverse.com [159.122.73.71]) by mx0a-001b2d01.pphosted.com (PPS) with ESMTPS id 3gsr0uhgju-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 20 Jun 2022 12:50:22 +0000 Received: from pps.filterd (ppma02fra.de.ibm.com [127.0.0.1]) by ppma02fra.de.ibm.com (8.16.1.2/8.16.1.2) with SMTP id 25KCZ6nb008321; Mon, 20 Jun 2022 12:50:19 GMT Received: from b06cxnps4075.portsmouth.uk.ibm.com (d06relay12.portsmouth.uk.ibm.com [9.149.109.197]) by ppma02fra.de.ibm.com with ESMTP id 3gs6b8syhu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 20 Jun 2022 12:50:19 +0000 Received: from d06av23.portsmouth.uk.ibm.com (d06av23.portsmouth.uk.ibm.com [9.149.105.59]) by b06cxnps4075.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id 25KCoGns17826124 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 20 Jun 2022 12:50:16 GMT Received: from d06av23.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 337DDA4040; Mon, 20 Jun 2022 12:50:16 +0000 (GMT) Received: from d06av23.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 79BFAA4051; Mon, 20 Jun 2022 12:50:15 +0000 (GMT) Received: from li-c6ac47cc-293c-11b2-a85c-d421c8e4747b.ibm.com.com (unknown [9.171.62.140]) by d06av23.portsmouth.uk.ibm.com (Postfix) with ESMTP; Mon, 20 Jun 2022 12:50:15 +0000 (GMT) From: Pierre Morel To: kvm@vger.kernel.org Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org, borntraeger@de.ibm.com, frankja@linux.ibm.com, cohuck@redhat.com, david@redhat.com, thuth@redhat.com, imbrenda@linux.ibm.com, hca@linux.ibm.com, gor@linux.ibm.com, pmorel@linux.ibm.com, wintera@linux.ibm.com, seiden@linux.ibm.com, nrb@linux.ibm.com Subject: [PATCH v10 0/3] s390x: KVM: CPU Topology Date: Mon, 20 Jun 2022 14:54:34 +0200 Message-Id: <20220620125437.37122-1-pmorel@linux.ibm.com> X-Mailer: git-send-email 2.27.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-TM-AS-GCONF: 00 X-Proofpoint-GUID: vA4pVF_LMeQeRO0ICtBGdEehG_JX62Wg X-Proofpoint-ORIG-GUID: usMS3epPWyS34AT1H7phIctfOn22EFD_ X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.883,Hydra:6.0.517,FMLib:17.11.64.514 definitions=2022-06-20_05,2022-06-17_01,2022-02-23_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 phishscore=0 mlxscore=0 malwarescore=0 mlxlogscore=999 lowpriorityscore=0 bulkscore=0 adultscore=0 priorityscore=1501 clxscore=1015 spamscore=0 impostorscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2204290000 definitions=main-2206200059 X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_EF,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi all, This new spin suppress the check for real cpu migration and modify the checking of valid function code inside the interception of the STSI instruction. The series provides: 0- Modification of the ipte lock handling to use KVM instead of the vcpu as an argument because ipte lock work on SCA which is uniq per KVM structure and common to all vCPUs. 1- interception of the STSI instruction forwarding the CPU topology 2- interpretation of the PTF instruction 3- a KVM capability for the userland hypervisor to ask KVM to setup PTF interpretation. 4- KVM ioctl to get and set the MTCR bit of the SCA in order to migrate this bit during a migration. 0- Foreword The S390 CPU topology is reported using two instructions: - PTF, to get information if the CPU topology did change since last PTF instruction or a subsystem reset. - STSI, to get the topology information, consisting of the topology of the CPU inside the sockets, of the sockets inside the books etc. The PTF(2) instruction report a change if the STSI(15.1.2) instruction will report a difference with the last STSI(15.1.2) instruction*. With the SIE interpretation, the PTF(2) instruction will report a change to the guest if the host sets the SCA.MTCR bit. *The STSI(15.1.2) instruction reports: - The cores address within a socket - The polarization of the cores - The CPU type of the cores - If the cores are dedicated or not We decided to implement the CPU topology for S390 in several steps: - first we report CPU hotplug In future development we will provide: - modification of the CPU mask inside sockets - handling of shared CPUs - reporting of the CPU Type - reporting of the polarization 1- Interception of STSI To provide Topology information to the guest through the STSI instruction, we forward STSI with Function Code 15 to the userland hypervisor which will take care to provide the right information to the guest. To let the guest use both the PTF instruction to check if a topology change occurred and sthe STSI_15.x.x instruction we add a new KVM capability to enable the topology facility. 2- Interpretation of PTF with FC(2) The PTF instruction reports a topology change if there is any change with a previous STSI(15.1.2) SYSIB. Changes inside a STSI(15.1.2) SYSIB occur if CPU bits are set or clear inside the CPU Topology List Entry CPU mask field, which happens with changes in CPU polarization, dedication, CPU types and adding or removing CPUs in a socket. Considering that the KVM guests currently only supports: - horizontal polarization - type 3 (Linux) CPU And that we decide to support only: - dedicated CPUs on the host - pinned vCPUs on the guest the creation of vCPU will is the only trigger to set the MTCR bit for a guest. The reporting to the guest is done using the Multiprocessor Topology-Change-Report (MTCR) bit of the utility entry of the guest's SCA which will be cleared during the interpretation of PTF. Regards, Pierre Pierre Morel (3): KVM: s390: ipte lock for SCA access should be contained in KVM KVM: s390: guest support for topology function KVM: s390: resetting the Topology-Change-Report Documentation/virt/kvm/api.rst | 31 ++++++++ arch/s390/include/asm/kvm_host.h | 11 ++- arch/s390/include/uapi/asm/kvm.h | 10 +++ arch/s390/kvm/gaccess.c | 96 ++++++++++++------------ arch/s390/kvm/gaccess.h | 6 +- arch/s390/kvm/kvm-s390.c | 123 ++++++++++++++++++++++++++++++- arch/s390/kvm/priv.c | 21 ++++-- arch/s390/kvm/vsie.c | 3 + include/uapi/linux/kvm.h | 1 + 9 files changed, 240 insertions(+), 62 deletions(-) -- 2.31.1 Changelog: from v9 to v10 - Suppression of the check on real CPU migration (Christian) - Changed the check on fc in handle_stsi (David) from v8 to v9 - bug correction in kvm_s390_topology_changed (Heiko) - simplification for ipte_lock/unlock to use kvm as arg instead of vcpu and test on sclp.has_siif instead of the SIE ECA_SII. (David) - use of a single value for reporting if the topology changed instead of a structure (David) from v7 to v8 - implement reset handling (Janosch) - change the way to check if the topology changed (Nico, Heiko) from v6 to v7 - rebase from v5 to v6 - make the subject more accurate (Claudio) - Change the kvm_s390_set_mtcr() function to have vcpu in the name (Janosch) - Replace the checks on ECB_PTF wit the check of facility 11 (Janosch) - modify kvm_arch_vcpu_load, move the check in a function in the header file (Janosh) - No magical number replace the "new cpu value" of -1 with a define (Janosch) - Make the checks for STSI validity clearer (Janosch) from v4 tp v5 - modify the way KVM_CAP is tested to be OK with vsie (David) from v3 to v4 - squatch both patches (David) - Added Documentation (David) - Modified the detection for new vCPUs (Pierre) from v2 to v3 - use PTF interpretation (Christian) - optimize arch_update_cpu_topology using PTF (Pierre) from v1 to v2: - Add a KVM capability to let QEMU know we support PTF and STSI 15 (David) - check KVM facility 11 before accepting STSI fc 15 (David) - handle all we can in userland (David) - add tracing to STSI fc 15 (Connie)