Received: by 10.192.165.148 with SMTP id m20csp1069699imm; Sat, 21 Apr 2018 00:08:12 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/m8pBAkeiusoe8/+WlbjxeS00q43lltIsgCA0vxykkhZSAFg+9XHdTGEn8CGdK/5bdrR8N X-Received: by 2002:a17:902:7841:: with SMTP id e1-v6mr12976468pln.197.1524294492223; Sat, 21 Apr 2018 00:08:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524294492; cv=none; d=google.com; s=arc-20160816; b=sDCP2OCpHouukWqk+DKkZ1FndK1Y/lKzWOzKpvPS7i4eKY7saRCHEOkD6EVQEmF6ir k9bATHYfHtvvu9q39a6eesX+JcqvB+MGhOlkn75eIhmpl7H895l90/OfhKuYlugiOZf7 cHomMCk1yXMZqyBOnCmieMXpjzy7G3hJCgECO7MxJwQ4KENHu9FtTI+wC42aitVmMeTV VUd5bqOmRt3QOOjHR7uESWKWbyUpuBiFRWluyt1YrZcOkKhsgIZFBfS83vC7N64RXSyy ghi3soubEfSubqotatAo+bdgQXFc47sSy7AQZT3S9h1SOyJOG1m516CXKd0ElfX7viKa zFhw== 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:arc-authentication-results; bh=5Q7Ke1adpbbrvNvGUiBaN6gWWwbgduPCfGnf4S8gw4M=; b=u//oU13vB+Cxx6wYJwfvVKFv1S7YfHXYTVGIXHyFEiCy1GHLqbot+kWrRMxwhr/p11 Fc13HXkw5xdA/iKNWcuc9wxWpe3boihHoou8mMAK/KY8UsV9ZteyFhFXYqwSVQIV88+P BZiArltmUgqa9M7z5aOd5nkJSlmkeA6+sB0IbLxBmjHKYK4miD0lyIhCBy/FQv9fCAd+ STPIPHrMU123S4TDrxv5ZEqVTlXNJ7ZKP+W3K7WSpCnaKkkaMhNtJHJC4TUs0B2c9mJY 4+12MEsDqVKvF3vND3aRKK5BRmHsWVZpAbYFJl+qqBSPkBiPG/gW1zO7pQpaKjZx7KPR Z7rA== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e3si5946263pgr.400.2018.04.21.00.07.34; Sat, 21 Apr 2018 00:08:12 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752712AbeDUHEQ (ORCPT + 99 others); Sat, 21 Apr 2018 03:04:16 -0400 Received: from verein.lst.de ([213.95.11.211]:45063 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751258AbeDUHEO (ORCPT ); Sat, 21 Apr 2018 03:04:14 -0400 Received: by newverein.lst.de (Postfix, from userid 2407) id 70D1D7090E; Sat, 21 Apr 2018 09:05:16 +0200 (CEST) Date: Sat, 21 Apr 2018 09:05:16 +0200 From: Christoph Hellwig To: "Michael S. Tsirkin" Cc: Alexander Duyck , "Daly, Dan" , Bjorn Helgaas , "Duyck, Alexander H" , linux-pci@vger.kernel.org, virtio-dev@lists.oasis-open.org, kvm@vger.kernel.org, Netdev , LKML , linux-nvme@lists.infradead.org, Keith Busch , netanel@amazon.com, Don Dutile , Maximilian Heyne , "Wang, Liang-min" , "Rustad, Mark D" , David Woodhouse , Christoph Hellwig , dwmw@amazon.co.uk Subject: Re: [virtio-dev] [pci PATCH v7 2/5] virtio_pci: Add support for unmanaged SR-IOV on virtio_pci devices Message-ID: <20180421070516.GA24431@lst.de> References: <20180315184132.3102.90947.stgit@localhost.localdomain> <20180316183042-mutt-send-email-mst@kernel.org> <20180403161151-mutt-send-email-mst@kernel.org> <20180403212503-mutt-send-email-mst@kernel.org> <20180420030640-mutt-send-email-mst@kernel.org> <20180420180839-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180420180839-mutt-send-email-mst@kernel.org> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 20, 2018 at 06:28:50PM +0300, Michael S. Tsirkin wrote: > But maybe it's not needed here. I am not making the decisions myself. > Not too late: post to the TC list and let's see what the response is. > Without a feature bit you are making a change affecting all future > implementations without exception so the bar is a bit higher: you need > to actually post a spec text proposal not just a patch showing how to > use the feature, and TC needs to vote on it. Voting takes a week, > review a week or two depending on change complexity. Also IFF the hardware already is out we can quirk it in the PCI ID table to manually set the feature in the driver as a workaround.