Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1045658yba; Thu, 9 May 2019 09:51:13 -0700 (PDT) X-Google-Smtp-Source: APXvYqxtVdlNUeYS/JuLMMi7xex01N4RTLFJSNMSul4F6HBO14DCYU7lyXAKL1rgXWT9Outus3dj X-Received: by 2002:a63:7146:: with SMTP id b6mr946879pgn.426.1557420673481; Thu, 09 May 2019 09:51:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557420673; cv=none; d=google.com; s=arc-20160816; b=nXHgMK6nB3fhN+NNggc31EZSBW6ba9MrJ6oGMN2Av9Qq2xTMevX8V2766sn6Jp6Q/C /EdjPHsD+u232OptxbD0OqQ5D1XT1JoL8a6xNLwZEfbsL4+qDzwyFlH6+c8a6imxR0lG 9X/t5x4yzW/kMfUgZB5QyEI6RI20jsyxQJ+QFhxiP3kKBZqBRpkKkfdtlF5yPaV5Ijgg aq6RqDH7GeBmB1qHfCJg665sbdiv7lk+dWSW18Nw37blJM8Ag0Q81k44pSTwlFvL+klm hxWHiKBwOZtoLfxX35KyosCC6rEJlLTS3k8F869YJ2D2Mt3O7vg25Bsrfhe7WZ6/55SL +9Tg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=ZaN7gr67xXJMFW6ONfE+Hwi9AIMTwOof3/ZnEz14Jx4=; b=Po8v0Df1cpN6Z2r1huvT4B/zKKvOEl/pb/xAe3zXDZqaq7yE0/Aukd7p8qEPJEciTZ S8ML4a2Yv24rMphoZE6TVf5+fPKi2PEARU5CWJB7CcGjTQgHuj5in26i9lDQo081IjZ1 tt7BQS0Vbl/9nDYR2rm2QTMdOw28FZUrxc4u/VDz9IfraIPTfUPvDi58yRet7uptEgeS MDfyFXhGWMSxVMB2JG0tVDPIg8GNHW5e4xBlu4a/ZkwajCOmY4IPd5E4hbr7b4jMT3ba mt6eApsOkeNCPhRkYoCqACAVYRCU8l5Of5NCXyxeCryaEnzGsPOejdWdgMq1gJXyiIeh i1Gg== 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 y4si3679100plb.283.2019.05.09.09.50.57; Thu, 09 May 2019 09:51:13 -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 S1726808AbfEIQsn (ORCPT + 99 others); Thu, 9 May 2019 12:48:43 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48374 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726620AbfEIQsn (ORCPT ); Thu, 9 May 2019 12:48:43 -0400 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 0DCCA3B712; Thu, 9 May 2019 16:48:42 +0000 (UTC) Received: from work-vm (ovpn-116-174.ams2.redhat.com [10.36.116.174]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 95FF11710E; Thu, 9 May 2019 16:48:28 +0000 (UTC) Date: Thu, 9 May 2019 17:48:26 +0100 From: "Dr. David Alan Gilbert" To: Cornelia Huck Cc: Alex Williamson , Yan Zhao , intel-gvt-dev@lists.freedesktop.org, arei.gonglei@huawei.com, aik@ozlabs.ru, Zhengxiao.zx@alibaba-inc.com, shuangtai.tst@alibaba-inc.com, qemu-devel@nongnu.org, eauger@redhat.com, yi.l.liu@intel.com, ziye.yang@intel.com, mlevitsk@redhat.com, pasic@linux.ibm.com, felipe@nutanix.com, changpeng.liu@intel.com, Ken.Xue@amd.com, jonathan.davies@nutanix.com, shaopeng.he@intel.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, libvir-list@redhat.com, eskultet@redhat.com, kevin.tian@intel.com, zhenyuw@linux.intel.com, zhi.a.wang@intel.com, cjia@nvidia.com, kwankhede@nvidia.com, berrange@redhat.com, dinechin@redhat.com Subject: Re: [PATCH v2 1/2] vfio/mdev: add version attribute for mdev device Message-ID: <20190509164825.GG2868@work-vm> References: <20190506014514.3555-1-yan.y.zhao@intel.com> <20190506014904.3621-1-yan.y.zhao@intel.com> <20190507151826.502be009@x1.home> <20190509173839.2b9b2b46.cohuck@redhat.com> <20190509154857.GF2868@work-vm> <20190509175404.512ae7aa.cohuck@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190509175404.512ae7aa.cohuck@redhat.com> User-Agent: Mutt/1.11.4 (2019-03-13) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Thu, 09 May 2019 16:48:43 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Cornelia Huck (cohuck@redhat.com) wrote: > On Thu, 9 May 2019 16:48:57 +0100 > "Dr. David Alan Gilbert" wrote: > > > * Cornelia Huck (cohuck@redhat.com) wrote: > > > On Tue, 7 May 2019 15:18:26 -0600 > > > Alex Williamson wrote: > > > > > > > On Sun, 5 May 2019 21:49:04 -0400 > > > > Yan Zhao wrote: > > > > > > > > + Errno: > > > > > + If vendor driver wants to claim a mdev device incompatible to all other mdev > > > > > + devices, it should not register version attribute for this mdev device. But if > > > > > + a vendor driver has already registered version attribute and it wants to claim > > > > > + a mdev device incompatible to all other mdev devices, it needs to return > > > > > + -ENODEV on access to this mdev device's version attribute. > > > > > + If a mdev device is only incompatible to certain mdev devices, write of > > > > > + incompatible mdev devices's version strings to its version attribute should > > > > > + return -EINVAL; > > > > > > > > I think it's best not to define the specific errno returned for a > > > > specific situation, let the vendor driver decide, userspace simply > > > > needs to know that an errno on read indicates the device does not > > > > support migration version comparison and that an errno on write > > > > indicates the devices are incompatible or the target doesn't support > > > > migration versions. > > > > > > I think I have to disagree here: It's probably valuable to have an > > > agreed error for 'cannot migrate at all' vs 'cannot migrate between > > > those two particular devices'. Userspace might want to do different > > > things (e.g. trying with different device pairs). > > > > Trying to stuff these things down an errno seems a bad idea; we can't > > get much information that way. > > So, what would be a reasonable approach? Userspace should first read > the version attributes on both devices (to find out whether migration > is supported at all), and only then figure out via writing whether they > are compatible? > > (Or just go ahead and try, if it does not care about the reason.) Well, I'm OK with something like writing to test whether it's compatible, it's just we need a better way of saying 'no'. I'm not sure if that involves reading back from somewhere after the write or what. Dave -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK