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 816F2A0A0E; Wed, 3 Feb 2021 10:38:08 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6D55B2404AC; Wed, 3 Feb 2021 10:38:08 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mails.dpdk.org (Postfix) with ESMTP id B0C1A24049C for ; Wed, 3 Feb 2021 10:38:06 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1612345085; 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=V8kcONGP7GOrjFQhcu7gRGRAoV9jt1NmLej+PBAv/Ig=; b=bzyeAi8ooSsIMlD8DCKaTQ5asQM3dnqkk9k6j5U6o+VN5aMAkDjTF3WxaAx49/+wrH9aXd ev6BCMl86NiI3rLxWbjxlGncq93UpgdMLzsiRNg0+QI6sbyAhrtnGXGRytOwrG/Kuy6kBg ctTsJC1vkay7NRp8N3OIHZxDs4cpH5Y= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-479-q8I4YRTmPo-UdMbJZ3IJUg-1; Wed, 03 Feb 2021 04:38:02 -0500 X-MC-Unique: q8I4YRTmPo-UdMbJZ3IJUg-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id DF2301083E9D; Wed, 3 Feb 2021 09:38:00 +0000 (UTC) Received: from [10.36.110.4] (unknown [10.36.110.4]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 10F2F10016FA; Wed, 3 Feb 2021 09:37:55 +0000 (UTC) To: =?UTF-8?B?6LCi5Y2O5LyfKOatpOaXtuatpOWIu++8iQ==?= , ferruh.yigit@intel.com Cc: dev@dpdk.org, david.marchand@redhat.com, anatoly.burakov@intel.com, xuemingl@nvidia.com, grive@u256.net, chenbo.xia@intel.com References: <1611890309-99135-1-git-send-email-huawei.xhw@alibaba-inc.com> <1611890309-99135-3-git-send-email-huawei.xhw@alibaba-inc.com> From: Maxime Coquelin Message-ID: <5fea43c2-9ab3-ca5c-0bd8-e47769215f92@redhat.com> Date: Wed, 3 Feb 2021 10:37:54 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0 MIME-Version: 1.0 In-Reply-To: <1611890309-99135-3-git-send-email-huawei.xhw@alibaba-inc.com> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=maxime.coquelin@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH v6 2/2] bus/pci: support MMIO in PCI ioport accessors 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" On 1/29/21 4:18 AM, 谢华伟(此时此刻） wrote: > |From: "huawei.xhw" With IO BAR, we get > PIO(programmed IO) address. With MMIO BAR, we get mapped virtual > address. We distinguish PIO(Programmed IO) and MMIO(memory mapped IO) by > their address like how kernel does. ioread/write8/16/32 is provided to > access PIO/MMIO. By the way, for virtio on arch other than x86, BAR flag > indicates PIO but is mapped. Signed-off-by: huawei xie > Reviewed-by: Maxime Coquelin > --- drivers/bus/pci/linux/pci.c | 4 -- > drivers/bus/pci/linux/pci_uio.c | 124 > ++++++++++++++++++++++++++-------------- 2 files changed, 81 > insertions(+), 47 deletions(-)| Reviewed-by: Maxime Coquelin Thanks, Maxime