Received: by 10.223.185.116 with SMTP id b49csp6092680wrg; Wed, 28 Feb 2018 03:59:49 -0800 (PST) X-Google-Smtp-Source: AH8x2252LnXSM2cPFjARbhfbVNAhrUTJJ84r2y54+uZGrpJzinqgVpgsqBjKCW0AvKIFOgUquWUX X-Received: by 2002:a17:902:9343:: with SMTP id g3-v6mr18043859plp.319.1519819189219; Wed, 28 Feb 2018 03:59:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519819189; cv=none; d=google.com; s=arc-20160816; b=MMDqwV7g/pe/X14yWPXlNE1su8WP+ykxr39YTsTrYcwQgZsRTiaXd64Mpswz4/mYFA sj6QRvWouGhFk/kGz4c6h9Bv7YP3s8RVLmM8A4ujNZgjPCicC5COw3g3OLD99aA8wn6N /77nT0gldAF1CCtoGa9MHMdfs+cE8I1TuE7mRO0Om47hQUK17ZAmdSs3sQUO85ZVre+6 f0k8HdUCMIT5ByUn8Z0ZCxBA/24A7ILmlzXU42yl7nNLegCRIcW93p8kb5IYYqRyBZGj wVhez0H3k7tFIgbJoWu359/X0jd0bIfLC1VTm2G0HIchuWJQwnR/t0EXvE5ADnGvBrx4 EMBQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:organization:from:references:cc:to:subject :arc-authentication-results; bh=2PzgHzN7d9/5LeqGPN5aqiDus+uB/TWEO3Rih1SWiUI=; b=zatYHmQx5bF/S706Noc2GE+sqWZJDFvc1XZlP+9xSD8D4lBGFLH9MgLeyNGkdRP/Um cEvMKuOlH9FjFa1gEHsbpapRn7Ua+gjvIeeUHYFy4/HxzhtTXSy5wQwfsvksQVCWjcBt Sq7FuHvKdnzfS+Xrm39I2UoFtJym/s/F5aww6y16KSu5ojKsd2aGuU6VSuOzKAQrK/5g eE3uyZcGaWBG+iGF/GKMRAVpsAO6gxXIuu7I77zRiBBmUNpnuYA2HZp4xWb+6MFBZI2q s3VsTThN91vbZwDauVQWr91zyXH+E8qJqkJyjVGm1aSAwBp/kg9DHkkI8Z4H1xcRsnsi z/KA== 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=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a188si955860pgc.183.2018.02.28.03.59.32; Wed, 28 Feb 2018 03:59:49 -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=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752340AbeB1L6u (ORCPT + 99 others); Wed, 28 Feb 2018 06:58:50 -0500 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:38716 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752203AbeB1L6s (ORCPT ); Wed, 28 Feb 2018 06:58:48 -0500 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 0A22C8424D; Wed, 28 Feb 2018 11:58:48 +0000 (UTC) Received: from [10.36.118.20] (unknown [10.36.118.20]) by smtp.corp.redhat.com (Postfix) with ESMTP id C185F946BF; Wed, 28 Feb 2018 11:58:42 +0000 (UTC) Subject: Re: [PATCH v2 04/15] KVM: s390: CPU model support for AP virtualization To: Christian Borntraeger , Tony Krowiak , linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org Cc: freude@de.ibm.com, schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com, cohuck@redhat.com, kwankhede@nvidia.com, bjsdjshi@linux.vnet.ibm.com, pbonzini@redhat.com, alex.williamson@redhat.com, pmorel@linux.vnet.ibm.com, alifm@linux.vnet.ibm.com, mjrosato@linux.vnet.ibm.com, jjherne@linux.vnet.ibm.com, thuth@redhat.com, pasic@linux.vnet.ibm.com, fiuczy@linux.vnet.ibm.com, buendgen@de.ibm.com References: <1519741693-17440-1-git-send-email-akrowiak@linux.vnet.ibm.com> <1519741693-17440-5-git-send-email-akrowiak@linux.vnet.ibm.com> <38deecae-53b4-c5cb-3dba-24bdfab3d9d0@redhat.com> <3a3ff176-4e6b-963c-7831-cdcd10b556eb@de.ibm.com> From: David Hildenbrand Organization: Red Hat GmbH Message-ID: <10cfdb2a-304c-989b-4765-84e19fcd423f@redhat.com> Date: Wed, 28 Feb 2018 12:58:42 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <3a3ff176-4e6b-963c-7831-cdcd10b556eb@de.ibm.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.2]); Wed, 28 Feb 2018 11:58:48 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.2]); Wed, 28 Feb 2018 11:58:48 +0000 (UTC) for IP:'10.11.54.5' DOMAIN:'int-mx05.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'david@redhat.com' RCPT:'' Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 28.02.2018 12:40, Christian Borntraeger wrote: > > > On 02/28/2018 10:48 AM, David Hildenbrand wrote: >> On 27.02.2018 15:28, Tony Krowiak wrote: >>> Introduces a new CPU model feature and two CPU model >>> facilities to support AP virtualization for KVM guests. >>> >>> CPU model feature: >>> >>> The KVM_S390_VM_CPU_FEAT_AP feature indicates that the >>> AP facilities are installed on the KVM guest. This >>> feature will be enabled by the kernel only if the AP >>> facilities are installed on the linux host. This feature >>> must be specifically turned on for the KVM guest from >>> userspace to allow guest access to AP devices installed >>> on the linux host. >>> >>> CPU model facilities: >>> >>> 1. AP Query Configuration Information (QCI) facility is installed. >>> >>> This is indicated by setting facilities bit 12 for >>> the guest. The kernel will not enable this facility >>> for the guest if it is not set on the host. This facility >>> must not be set by userspace if the KVM_S390_VM_CPU_FEAT_AP >>> feature is not installed. >>> >>> 2. AP Facilities Test facility (APFT) is installed. >>> >>> This is indicated by setting facilities bit 15 for >>> the guest. The kernel will not enable this facility for >>> the guest if it is not set on the host. This facility >>> must not be set by userspace if the KVM_S390_VM_CPU_FEAT_AP >>> feature is not installed. >>> >>> Reviewed-by: Christian Borntraeger >>> Reviewed-by: Halil Pasic >>> Signed-off-by: Tony Krowiak >>> --- >>> arch/s390/include/uapi/asm/kvm.h | 1 + >>> arch/s390/kvm/kvm-s390.c | 4 ++++ >>> arch/s390/tools/gen_facilities.c | 2 ++ >>> 3 files changed, 7 insertions(+), 0 deletions(-) >>> >>> diff --git a/arch/s390/include/uapi/asm/kvm.h b/arch/s390/include/uapi/asm/kvm.h >>> index 4cdaa55..a580dec 100644 >>> --- a/arch/s390/include/uapi/asm/kvm.h >>> +++ b/arch/s390/include/uapi/asm/kvm.h >>> @@ -130,6 +130,7 @@ struct kvm_s390_vm_cpu_machine { >>> #define KVM_S390_VM_CPU_FEAT_PFMFI 11 >>> #define KVM_S390_VM_CPU_FEAT_SIGPIF 12 >>> #define KVM_S390_VM_CPU_FEAT_KSS 13 >>> +#define KVM_S390_VM_CPU_FEAT_AP 14 >>> struct kvm_s390_vm_cpu_feat { >>> __u64 feat[16]; >>> }; >>> diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c >>> index de1e299..c68ca86 100644 >>> --- a/arch/s390/kvm/kvm-s390.c >>> +++ b/arch/s390/kvm/kvm-s390.c >>> @@ -347,6 +347,10 @@ static void kvm_s390_cpu_feat_init(void) >>> >>> if (MACHINE_HAS_ESOP) >>> allow_cpu_feat(KVM_S390_VM_CPU_FEAT_ESOP); >>> + >>> + if (ap_instructions_installed()) /* AP instructions installed on host */ >>> + allow_cpu_feat(KVM_S390_VM_CPU_FEAT_AP); >> >> Don't we have a SIE specific AP feature? So is it true, that once we >> have AP instructions, we are allowed to use them for SIE? Isn't there a >> "AP interpretation facility" or anything like that? (that unlocks ECA_APIE) > > This seems to be coupled to the AP facility and there is no facility or scp bit. > AP is too old to have that (predates STFLE) > Interesting, so we (I :) ) didn't implement vSIE support back then because we never indicated the AP facility (sensed by executing the instruction) to the guest. So ECA_APIE can be used when we sense the AP facility. Thanks! -- Thanks, David / dhildenb