From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D8BC0C432C0 for ; Wed, 20 Nov 2019 13:43:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id ABF0022528 for ; Wed, 20 Nov 2019 13:43:35 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="Tey/YfQK" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731335AbfKTNne (ORCPT ); Wed, 20 Nov 2019 08:43:34 -0500 Received: from us-smtp-2.mimecast.com ([205.139.110.61]:27256 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1731278AbfKTNnd (ORCPT ); Wed, 20 Nov 2019 08:43:33 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1574257412; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=BwFx+Dwq/n/prb7owY95fMpf8ebLIV+MGGzw0ANGQiU=; b=Tey/YfQK6Kr9DVQmT4sGWZ1+90xKm7lCBtzUGn7eA+dD8BlWqqqq1IZFZ/PuKbrnP1ODqd YEs19fIRG3bKRQIbzbRKTuy2aQOdSUJOCzcOQ2Gt5xbUuks/YPweRTclFroM6JtXv1WnsD XyH77XwUVhMpJlCou8G9uX94DBHOgy0= Received: from mail-qk1-f200.google.com (mail-qk1-f200.google.com [209.85.222.200]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-270-xQuBpJHJPA6z9QynFdyNJQ-1; Wed, 20 Nov 2019 08:43:29 -0500 Received: by mail-qk1-f200.google.com with SMTP id a16so15825248qka.10 for ; Wed, 20 Nov 2019 05:43:29 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=feQZhc67FFi+Ko9ak2oh56vIMRGjrYkPDdCN0lvuJuU=; b=HtIv2JkYGcS1J/KjQAQ/EI7GT8faYAfaN5gg0C0q/2/CVgeWx9Iu+F5gTjIQwyVbvF /DqBZ/5W/3eOxe0LGXA3Sr6ZSVojRxJt+84tkkr4CoHZG36T1BzK+yAsf+tBpzMfuXrc rq0vu1qBZovyrAonYGrD0dI0LZufhO/DpGBYAzALIYx8z82IYaR0jx0zYmf78hPpieI2 /d6BhSzdem5MrwJGf/AqulhUIo9evCeAVy7BGSQbyIE0YQUJ1ZFllFpTeWqGOROItrnK cC1KbbnnFQxFeUO6PkQMGmXhLTDkezKBPLzchhSE/uubdo3ZhgKULZlfAeKOQgmopRdx Uyqg== X-Gm-Message-State: APjAAAUq+SxM5nQ8PiFE5pgIo1iP71y6ctp/nqcS/pYHngi18MVEXflA RE9vGpxeGy/j2TFC2+LcYLs+rkVpbf4I30b2pWesnJce++eDo0Gh9Ha0CmdHfMR0FIrjqxDD0Qt OUm7kfllB1ovwTAU3 X-Received: by 2002:a37:7305:: with SMTP id o5mr2487939qkc.120.1574257408647; Wed, 20 Nov 2019 05:43:28 -0800 (PST) X-Google-Smtp-Source: APXvYqwMu4Xq4O5OheMkoMoD/p5gJRYFOHibk5C4maRW+a4TNNJe/+fxGATAgpD0kJGaqTTVXuEFhA== X-Received: by 2002:a37:7305:: with SMTP id o5mr2487922qkc.120.1574257408397; Wed, 20 Nov 2019 05:43:28 -0800 (PST) Received: from redhat.com (bzq-79-176-6-42.red.bezeqint.net. [79.176.6.42]) by smtp.gmail.com with ESMTPSA id h3sm15059129qte.62.2019.11.20.05.43.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 20 Nov 2019 05:43:27 -0800 (PST) Date: Wed, 20 Nov 2019 08:43:20 -0500 From: "Michael S. Tsirkin" To: Jason Gunthorpe Cc: Jason Wang , Parav Pandit , Jeff Kirsher , "davem@davemloft.net" , "gregkh@linuxfoundation.org" , Dave Ertman , "netdev@vger.kernel.org" , "linux-rdma@vger.kernel.org" , "nhorman@redhat.com" , "sassmann@redhat.com" , Kiran Patil , Alex Williamson , "Bie, Tiwei" Subject: Re: [net-next v2 1/1] virtual-bus: Implementation of Virtual Bus Message-ID: <20191120083908-mutt-send-email-mst@kernel.org> References: <20191119164632.GA4991@ziepe.ca> <20191119134822-mutt-send-email-mst@kernel.org> <20191119191547.GL4991@ziepe.ca> <20191119163147-mutt-send-email-mst@kernel.org> <20191119231023.GN4991@ziepe.ca> <20191119191053-mutt-send-email-mst@kernel.org> <20191120014653.GR4991@ziepe.ca> <20191120022141-mutt-send-email-mst@kernel.org> <20191120130319.GA22515@ziepe.ca> MIME-Version: 1.0 In-Reply-To: <20191120130319.GA22515@ziepe.ca> X-MC-Unique: xQuBpJHJPA6z9QynFdyNJQ-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Wed, Nov 20, 2019 at 09:03:19AM -0400, Jason Gunthorpe wrote: > On Wed, Nov 20, 2019 at 02:38:08AM -0500, Michael S. Tsirkin wrote: > > > > I don't think that extends as far as actively encouraging userspace > > > > drivers poking at hardware in a vendor specific way. =20 > > >=20 > > > Yes, it does, if you can implement your user space requirements using > > > vfio then why do you need a kernel driver? > >=20 > > People's requirements differ. You are happy with just pass through a VF > > you can already use it. Case closed. There are enough people who have > > a fixed userspace that people have built virtio accelerators, > > now there's value in supporting that, and a vendor specific > > userspace blob is not supporting that requirement. >=20 > I have no idea what you are trying to explain here. I'm not advocating > for vfio pass through. You seem to come from an RDMA background, used to userspace linking to vendor libraries to do basic things like push bits out on the network, because users live on the performance edge and rebuild their userspace often anyway. Lots of people are not like that, they would rather have the vendor-specific driver live in the kernel, with userspace being portable, thank you very much. --=20 MST