From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 877DD1B53 for ; Fri, 21 Sep 2018 14:55:27 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 7B69F2118B; Fri, 21 Sep 2018 08:55:26 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 21 Sep 2018 08:55:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=cYwLSwr9i/78cslkYDJV3mfa0s 4/ZXzZ5QHz2Xd4xSI=; b=mFThqL3B394gfa84lQMX2saOFPghbOhVrzsVlU8eni c5+wHoRCu/Ay+vm6Fj4Uk+GEj89oD7A2EEQ+mp210M0wfL0EfKZvCge5BCeOMXZ0 SrAqrKBkOAid+gteygHV7Ums7jRJXW30+0WY8c0croAPgaZLu2lXUqPquE0rTnZ6 g= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=cYwLSw r9i/78cslkYDJV3mfa0s4/ZXzZ5QHz2Xd4xSI=; b=I3xZAP5bV14+fayO6Eyu1r IDQOOgJ31uKFUd0T2vmJUeuwrP4NJKNtB4J5roK5B8HqFIbeiKfSi2TPJZyZjvd2 kiPM7CjUh+9Mjm4MfpGzShIzpfyauYb/65B8Af+P1I4VZfmDvhewbyKwB2AsGtZw h2nXV4eJAgrIwgyINvhKlf300uyxy2nGJq5OF23FElCwpRXb6/WDCCW3p0ooPg4X 78Bh5PpL8Lfq6gUUULlBRj7UEG6k+vJbjniz4/fsTIXl6+5yP97n026sVaTryd9R FETGaXJLDNtZtfYjATJ9jvvCOeEBbVwyeCGmkQIc//e22VxQ+JIlheObECbihyaA == X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 9AB8D102D6; Fri, 21 Sep 2018 08:55:25 -0400 (EDT) From: Thomas Monjalon To: =?ISO-8859-1?Q?Ga=EBtan?= Rivet Cc: dev@dpdk.org Date: Fri, 21 Sep 2018 14:55:24 +0200 Message-ID: <27955989.SnTzdq47Er@xps> In-Reply-To: <20180921115312.sdegsb3ko2mbf7hc@bidouze.vm.6wind.com> References: <2305853.Xkr2rJqqKv@xps> <20180921115312.sdegsb3ko2mbf7hc@bidouze.vm.6wind.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Subject: Re: [dpdk-dev] [PATCH v2 04/13] bus/vdev: add device matching field driver X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Sep 2018 12:55:27 -0000 21/09/2018 13:53, Ga=EBtan Rivet: > On Thu, Sep 20, 2018 at 06:11:44PM +0200, Thomas Monjalon wrote: > > 19/09/2018 18:03, Gaetan Rivet: > > > The vdev bus parses a field "driver", matching > > > a vdev driver name with one passed as follows: > > >=20 > > > "bus=3Dvdev,driver=3Dxxxx" > >=20 > > I think the property should be "name". > > We already have a "driver" category. > > So it may be "bus=3Dvdev,name=3Dmytap/driver=3Dtap" > >=20 > > Until now we were using the name of the driver as a prefix for > > the device name because it was the only way of knowing the driver to us= e. > > With a richer syntax like above, this restriction can be removed. >=20 > Do you want all buses to read the driver=3D key and use it to know which > driver to probe, or is it an exception of the vdev bus? Good point. Yes, if the driver=3D key is provided, the bus should respect i= t. It may allow to have 2 different drivers supporting the same PCI ids, and let the user override the default driver to use.