From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 6273FA0524; Tue, 25 Feb 2020 10:06:10 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 4D8302C4F; Tue, 25 Feb 2020 10:06:09 +0100 (CET) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id C4C903B5 for ; Tue, 25 Feb 2020 10:06:06 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Feb 2020 01:06:05 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.70,483,1574150400"; d="scan'208";a="271235972" Received: from rmenon-mobl.amr.corp.intel.com (HELO [10.237.220.73]) ([10.237.220.73]) by fmsmga002.fm.intel.com with ESMTP; 25 Feb 2020 01:06:04 -0800 From: Ranjit Menon To: Dmitry Kozlyuk Cc: Pallavi Kadam , Harini Ramakrishnan , dev@dpdk.org, Narcisa Ana Maria Vasile References: <20200208114546.546db2d0@Sovereign> <9a3fca13-bebc-cc87-d955-06b41fdbcdfe@intel.com> <20200210091426.17b215db@Sovereign> <20200217041424.22afb6dc@Sovereign> <13c23300-f41f-4e9a-c830-a81ace3593c8@intel.com> <20200225053749.448e0932@Sovereign> Message-ID: Date: Tue, 25 Feb 2020 01:06:03 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 In-Reply-To: <20200225053749.448e0932@Sovereign> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] Windows Draft Build 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 2/24/2020 6:37 PM, Dmitry Kozlyuk wrote: > > Oh boy! If DriverEntry() is not being called, the loader is finding something wrong and is unable to load the driver. > > > > @Harini: Can Jeffrey (@MS) help here? > > By trial and error I determined that changing device class from "Net" to a > custom one fixes the issue (see attached patch), root cause is still unknown. > >  From this point, running virtio PMD is blocked by lack of multi-BAR support > in NETUIO, which is a separate concern, outside of scope of this thread. > Dmitry... This is a very interesting find. Will this change to a custom class allow the driver to load in the native (bare-metal) case, too? Also, Naty (Narcisa) has a patch for multi-BAR support, that we (Intel) were not able to successfully use...but it's working for her. If you'd like to try it out, she can send it to you. ranjit m.