From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 38640A054F; Tue, 2 Mar 2021 13:48:37 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0340F22A30A; Tue, 2 Mar 2021 13:48:37 +0100 (CET) Received: from out0-143.mail.aliyun.com (out0-143.mail.aliyun.com [140.205.0.143]) by mails.dpdk.org (Postfix) with ESMTP id 72F1A22A303 for ; Tue, 2 Mar 2021 13:48:35 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1614689313; h=Subject:To:From:Message-ID:Date:MIME-Version:Content-Type; bh=WUBFADrMVq4bn1s+L7rXElvB8cSpwSeDSkbzVTJ7ZVM=; b=RH0seCgNWeDPcG8JubGgf6Kil0rEwXNTjpZlu+t5nh9Uxr8JTqu03VSjun0D42PWy5yGq7tRASvpCMhg4i3OwhqKk93WK1GAxHRB/WXock6zqQP2c7W/66lHiiaXybauFgEYYYuE6a1kq2RNcvfMJP0yKrJ3GGZEJH8Wi7MbkCU= X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R101e4; CH=green; DM=||false|; DS=||; FP=0|-1|-1|-1|0|-1|-1|-1; HT=ay29a033018047201; MF=huawei.xhw@alibaba-inc.com; NM=1; PH=DS; RN=8; SR=0; TI=SMTPD_---.JfPtzNA_1614689313; Received: from 30.43.73.114(mailfrom:huawei.xhw@alibaba-inc.com fp:SMTPD_---.JfPtzNA_1614689313) by smtp.aliyun-inc.com(127.0.0.1); Tue, 02 Mar 2021 20:48:33 +0800 To: ferruh.yigit@intel.com, maxime.coquelin@redhat.com, david.marchand@redhat.com Cc: dev@dpdk.org, anatoly.burakov@intel.com, xuemingl@nvidia.com, grive@u256.net, chenbo.xia@intel.com References: <1614014118-91150-1-git-send-email-huawei.xhw@alibaba-inc.com> <1614614483-75891-1-git-send-email-huawei.xhw@alibaba-inc.com> From: "=?UTF-8?B?6LCi5Y2O5LyfKOatpOaXtuatpOWIu++8iQ==?=" Message-ID: <50960672-267a-a8b7-2474-3534314b3db7@alibaba-inc.com> Date: Tue, 02 Mar 2021 20:48:25 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: <1614614483-75891-1-git-send-email-huawei.xhw@alibaba-inc.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Subject: Re: [dpdk-dev] [PATCH v8 0/2] support both PIO and MMIO BAR for legacy device in virtio PMD X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 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" Hi David and ferru: Any other issue integrating this patch? On 2021/3/2 0:01, 谢华伟(此时此刻) wrote: > From: "huawei.xhw" > > virtio PMD assumes legacy device only supports PIO BAR resource. This is wrong. > As we need to create lots of devices, as PIO resource on x86 is very limited, > we expose MMIO(memory IO) BAR. > > Kernel supports both PIO and MMIO BAR for legacy virtio-pci device, and for all > other pci devices. This patchset handles different type of BAR in the similar way. > > In previous implementation, under igb_uio driver we get PIO address from igb_uio > sysfs entry; with uio_pci_generic, we get PIO address from /proc/ioports for x86, > and for other ARCHs, we get PIO address from standard PCI sysfs entry. > For PIO/MMIO RW, there is different path for different drivers and arch.