Received: by 10.192.165.148 with SMTP id m20csp3103418imm; Mon, 23 Apr 2018 00:06:25 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/0tPF51EXHoDhWIxl5iiQy4nDpUBhgnQfqoYBkp5U3NLDu2z5KfuVvkkcDx0KStyudaTg4 X-Received: by 2002:a17:902:42a5:: with SMTP id h34-v6mr19672894pld.65.1524467185240; Mon, 23 Apr 2018 00:06:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524467185; cv=none; d=google.com; s=arc-20160816; b=m+dmSpD3xY+4LSlGrER6PquIF/kwFd4fZgOFxSCMvVsfgP0Q6HL3WOsQp3MTPIV5UF iaYu5yclyX06dKmeNUj45Fe9UUCckG2udkTLV1V/FHSPFxUipUdc0xaOLW56ymNqexw7 NJl/GeqJB8ERhOlP/fdknqLHfa9aXQ8s3QTGfMuKiGMpTJ1jljRk2hcNs0X2AqKOlZgi C93wwZ5wiw5qfetvFTcuK1Dst+PhDVExm6Db88Hf3DTJpAfgXtoYOsrbEqseIADKcOzZ wdXcH/OfpNjcu7H9eE8vwBKfgg2jelc7Sxn2DiY0nD4hbUlqY9jEJ5PMGi3j/0Y178yT 8tnA== 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:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date:arc-authentication-results; bh=sayoCV5WAkRufzpdH6U1IKmPbtuD235ZwAUyHfSuka0=; b=C3jWO6mjlsPPL8UQfnd/EkJIl6/pa5tT5dPjgXl0hGRuhQI93NdmEzeB4vBbGGS2Y2 aHh8z6mn5V4VU9kuBMhem0C91kPzMb1PrUsQYcswZvE0fXHnUcCLBjvQaOiWKe3gh2s/ g/FM1ahPcC6wmVE+rAFmzHr31nJJKaLAB11jUd8XBYEm4/5595f4w3J1BM6uMZkU1EUZ 4KbGuxdTqHYqcBW4hYOJMHlkeo56sVNjb1ck/dx+OYsZJunned5k+VWIwXqqDZwW3u3A 0FnuRUbscFZAckbvCsM+QppIgmL/ZxjZiDiHt3rpbaL8hDC4/681fXkvXpIhPkP/Fw4W Yu1w== 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 e63si5925481pfd.261.2018.04.23.00.06.09; Mon, 23 Apr 2018 00:06:25 -0700 (PDT) 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 S1754122AbeDWHE5 (ORCPT + 99 others); Mon, 23 Apr 2018 03:04:57 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:48026 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751785AbeDWHE4 (ORCPT ); Mon, 23 Apr 2018 03:04:56 -0400 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 56B46A5026; Mon, 23 Apr 2018 07:04:55 +0000 (UTC) Received: from gondolin (ovpn-116-250.ams2.redhat.com [10.36.116.250]) by smtp.corp.redhat.com (Postfix) with ESMTP id DA8C82166BAE; Mon, 23 Apr 2018 07:04:51 +0000 (UTC) Date: Mon, 23 Apr 2018 09:04:49 +0200 From: Cornelia Huck To: Tony Krowiak Cc: Pierre Morel , freude@de.ibm.com, buendgen@de.ibm.com, linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com, borntraeger@de.ibm.com, kwankhede@nvidia.com, bjsdjshi@linux.vnet.ibm.com, pbonzini@redhat.com, alex.williamson@redhat.com, alifm@linux.vnet.ibm.com, mjrosato@linux.vnet.ibm.com, jjherne@linux.vnet.ibm.com, thuth@redhat.com, pasic@linux.vnet.ibm.com, berrange@redhat.com, fiuczy@linux.vnet.ibm.com Subject: Re: [PATCH v4 01/15] s390: zcrypt: externalize AP instructions available function Message-ID: <20180423090449.32de58df.cohuck@redhat.com> In-Reply-To: References: <1523827345-11600-1-git-send-email-akrowiak@linux.vnet.ibm.com> <1523827345-11600-2-git-send-email-akrowiak@linux.vnet.ibm.com> <77bbd4ca-8412-e59d-e1ca-9a114cf495a6@linux.vnet.ibm.com> <20180416141136.04be5558.cohuck@redhat.com> <20180417185646.5b43c911.cohuck@redhat.com> Organization: Red Hat GmbH MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.2]); Mon, 23 Apr 2018 07:04:55 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.2]); Mon, 23 Apr 2018 07:04:55 +0000 (UTC) for IP:'10.11.54.6' DOMAIN:'int-mx06.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'cohuck@redhat.com' RCPT:'' Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 22 Apr 2018 13:21:16 -0400 Tony Krowiak wrote: > On 04/17/2018 12:56 PM, Cornelia Huck wrote: > > On Tue, 17 Apr 2018 09:31:00 -0400 > > Tony Krowiak wrote: > > > >> My preference would be one of the following: > >> > >> 1. All of the interfaces defined in arch/s390/include/asm/ap.h > >> are implemented in a file that is built whether ZCRYPT is > >> built or not. > >> > >> 2. The drivers/s390/crypto/ap_asm.h file containing the functions > >> that execute the AP instructions are made available outside of > >> the AP bus, for example; arch/s390/include/asm > >> > >> I requested this from the maintainer but was told we don't want to > >> have any crypto adapter support when the host AP functionality is > >> disabled (CONFIG_ZCRYPT=n). This makes sense, however; I think it is > >> a bit confusing to have a header file (arch/s390/include/asm/ap.h) > >> with interfaces that are conditionally built. > >> > >> This is why I chose the ifdeffery (as you call it) approach. The > >> only other solution I can conjure is to duplicate the asm code for > >> the AP instructions needed in KVM and bypass using the AP bus > >> interfaces. > > I think at the root of this is an unfortunate mixup in the > > architecture: The format of the crycb changes depending on some ap > > feature being installed. Providing the crycb does not have anything to > > do with ap device usage in the host, but we need to issue an ap > > instruction to get this right. [Correct me if I'm wrong; but that's > > what I get without being able to consult the actual architecture.] > > > > So, exporting *all* of the interfaces is probably not needed anyway. I > > think it boils down to either "export the interfaces where a mixup > > happened, and keep the rest to zcrypt only", or "duplicate the > > instructions for kvm usage". > > > > I hope we can find a solution here, as this seems to be one of the main > > discussion points :/ (FWIW, I think the basic driver interface is sane.) > > I spoke with Harald Freudenberger and he is going to refactor the AP bus > code to make the two functions//I need static in the kernel: > > int ap_instructions_installed(void); > int ap_query_configuration(struct ap_config_info *info); > // > > > Excellent, looking forward to it.