Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp3035971imm; Fri, 10 Aug 2018 02:37:49 -0700 (PDT) X-Google-Smtp-Source: AA+uWPwAUShD0bX8/7985gGkdKSyWl8jwYS1fXRjtQPmrqawumgOiTI9fIDU0npnxm7xl7600EpM X-Received: by 2002:a62:6746:: with SMTP id b67-v6mr6281013pfc.243.1533893868995; Fri, 10 Aug 2018 02:37:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1533893868; cv=none; d=google.com; s=arc-20160816; b=covKj2J2yNSB+K38N6S5fLHtDa6ZjauKbYbEFvl1sR+siBOREGnP7QDpodCEJ0yPAQ xxjvU+dPh4ipXiGrnDubGukzAyVkCkJk7eSsOLPhQIshw0NUn3W+jStJ95UxCCDvdM7K 6gmQROOoQGMP73wz1kgVjM0ZzlJhxRawRzKpUOYUI0pVeyy7CG2ultpkbfLRK3xS7KsT JtCvreXAUUYCW4FtEHknAc/vUVFkPPLIHLqs3yt93IVxOXNNI+EcLFVhFcbK3FStKvxM DKcnMiY4Q1RRGNlCNmWpEo1xWRMvakEBqtAO6EVzGreD0qpj/RAR6pXwHl9pFXh5UKkQ eaWw== 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=UHKOxsmrhNjVB0Un4Iuw4QUXBhN/LSi8mi1/HoyoeZI=; b=ihGtEObQ6VN9v+A96K6lGRSMHV8clPkr3pRg6Fyh+/n9pU887TerygupfzBHvqPslF WL3cDAO1fUq6CdWQwVjB7aYlLT7BxojqMXLK+4oIZGOlQ3FAJ2FtZQ1tvFhTclsU8w1m RZi9dZqrwKr9b69BIIbXUKvqBFGq5VgrwtWurx5wp7RN2cfZatoQ6aM3N/O+2x1M/CJP Vgd03lKzl29m3Brb55z/igqmIet7cFia6zUN3MfG/zsmzqw2BqPq+8GOOOe+giaHjgq1 kJKsrq/kPdkVCCp2GL15pYS9OK4vBbET0H/kmP8UMM6ANS7xeREmqZ3AbBRp0IZ0FA0l 2Xvw== 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 b34-v6si7258658pla.84.2018.08.10.02.37.33; Fri, 10 Aug 2018 02:37:48 -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 S1727842AbeHJL2j (ORCPT + 99 others); Fri, 10 Aug 2018 07:28:39 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:58664 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726997AbeHJL2j (ORCPT ); Fri, 10 Aug 2018 07:28:39 -0400 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 5FAC8F2B3C; Fri, 10 Aug 2018 08:59:40 +0000 (UTC) Received: from gondolin (dhcp-192-222.str.redhat.com [10.33.192.222]) by smtp.corp.redhat.com (Postfix) with ESMTP id 61BB81018E; Fri, 10 Aug 2018 08:59:35 +0000 (UTC) Date: Fri, 10 Aug 2018 10:59:33 +0200 From: Cornelia Huck To: Pierre Morel Cc: Tony Krowiak , linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, freude@de.ibm.com, 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, 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, berrange@redhat.com, fiuczy@linux.vnet.ibm.com, buendgen@de.ibm.com, frankja@linux.ibm.com, Tony Krowiak Subject: Re: [PATCH v8 09/22] s390: vfio-ap: register matrix device with VFIO mdev framework Message-ID: <20180810105933.2431b6a0.cohuck@redhat.com> In-Reply-To: References: <1533739472-7172-1-git-send-email-akrowiak@linux.vnet.ibm.com> <1533739472-7172-10-git-send-email-akrowiak@linux.vnet.ibm.com> <20180809130607.32781b72.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.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]); Fri, 10 Aug 2018 08:59:40 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.2]); Fri, 10 Aug 2018 08:59:40 +0000 (UTC) for IP:'10.11.54.5' DOMAIN:'int-mx05.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 Thu, 9 Aug 2018 18:27:16 +0200 Pierre Morel wrote: > On 09/08/2018 13:06, Cornelia Huck wrote: > > On Wed, 8 Aug 2018 10:44:19 -0400 > > Tony Krowiak wrote: > > > >> diff --git a/drivers/s390/crypto/vfio_ap_drv.c b/drivers/s390/crypto/vfio_ap_drv.c > >> index d7e39ad..6a827f3 100644 > >> --- a/drivers/s390/crypto/vfio_ap_drv.c > >> +++ b/drivers/s390/crypto/vfio_ap_drv.c > >> @@ -12,6 +12,7 @@ > >> #include > >> #include > >> #include > >> +#include > >> #include "vfio_ap_private.h" > >> > >> #define VFIO_AP_ROOT_NAME "vfio_ap" > >> @@ -68,6 +69,18 @@ static int vfio_ap_matrix_dev_create(void) > >> { > >> int ret; > >> > >> + mutex_init(&matrix_dev.lock); > >> + INIT_LIST_HEAD(&matrix_dev.mdev_list); > >> + > >> + /* Test if PQAP(QCI) instruction is available */ > >> + if (test_facility(12)) { > >> + ret = ap_qci(&matrix_dev.info); > >> + if (ret) > >> + return ret; > >> + } > >> + > >> + atomic_set(&matrix_dev.available_instances, MAX_ZDEV_ENTRIES_EXT); > >> + > >> ret = misc_register(&matrix_dev.misc_dev); > > OK, you are adding more stuff other than the miscdevice after all... > > still, I don't think that this is a good idea. > > > > I think I had already asked this for a previous version: Why has this > > been turned into a miscdevice? (I think my reaction to the answer was > > 'meh'... but I think more and more that we should not do that.) > > Following our off-line conversation... > > I understand your concern, about the misc device and dynamically > updating the misc device structure. > > For it is your main point of contention and we do not currently have > a use case for the misc device I propose we just let it go and > rebase on the device design we had in V6 and did not seem to > make any trouble to any one. > > We will propose a v9 with the integration of all comment done > so far soon as possible. Sounds good to me!