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 E9C2B42C52; Wed, 7 Jun 2023 18:31:04 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7C67C42C76; Wed, 7 Jun 2023 18:31:04 +0200 (CEST) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by mails.dpdk.org (Postfix) with ESMTP id 4945642C4D for ; Wed, 7 Jun 2023 18:31:03 +0200 (CEST) Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 5224C320099E; Wed, 7 Jun 2023 12:31:00 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Wed, 07 Jun 2023 12:31:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm1; t= 1686155459; x=1686241859; bh=/gL4savEJGhMSSkkvxcfllVwPlJBfwxxf64 OCsj7rVM=; b=bZvVmQO1I53g3jDQNbB4aYpEqXpvvtUFmgLRoY5JUu/v91HRYpw 0iiMIShFDH3ezCJwYUGUnWaII5dbmGETi50nqn8SckZ8z/MnCMLUhnRAaRxwXsW/ cPuKrncPC5w2qhz8ypFssUQIUo5C+Yuvbz4GM2PJnxfhbZSgQ02reZKcIWNbR9zK BaHsQQ6uMwLYfothUHCibf3MWIe1h2AEqI3S6jyMdTwTJtd2sQbhrIQdB1f6FN3X 75Ongb9DWHemYq9zKc33C+caj2QodlIN75S1a5xreg4EBFIqqlnfLcCGYby4qLGq vHxD7dOnHJVh1W2Zbr3BpeVkXB31Tq9sCag== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1686155459; x=1686241859; bh=/gL4savEJGhMSSkkvxcfllVwPlJBfwxxf64 OCsj7rVM=; b=hLBcQF50okun4KQPoxIc+XNYf6Znwxo58UMQ/LDP0jy8vjjL7AJ /48LmUbI3GRltmvg0A8LMHzH0FBnY75syPkMmgJP1PwsJ/j6HEjS3+FCQrnPEnit 8BBZy7d+zfPP0b2/oe4HA2Oe3mLNIFk2x1xsdvoWqNltUuDSOsTRa3oIcIeZEcYg 6w+3utdj2WVfS+SCBfREX+3gbZnwKiEEfvxNsf231orj0UbHYT1WH6p9eoQGG/kG Q4TCCpHbS8cSEkO/5F05Yx18lG/rYBMuXZmbPZfLQPchnjFi1kmX7nbkdUXyLGEP a0HLh9SXrtF/Se6e8UmIZotgssLxSwY/tBQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrgedtgedguddtvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvfevufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhho mhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqne cuggftrfgrthhtvghrnheptdejieeifeehtdffgfdvleetueeffeehueejgfeuteeftddt ieekgfekudehtdfgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 7 Jun 2023 12:30:58 -0400 (EDT) From: Thomas Monjalon To: Miao Li Cc: dev@dpdk.org, skori@marvell.com, david.marchand@redhat.com, ferruh.yigit@amd.com, chenbo.xia@intel.com, yahui.cao@intel.com Subject: Re: [PATCH v4 0/4] Support VFIO sparse mmap in PCI bus Date: Wed, 07 Jun 2023 18:30:57 +0200 Message-ID: <3692203.tiCG3LdiiZ@thomas> In-Reply-To: <20230531053743.129442-1-miao.li@intel.com> References: <20230525163116.682000-1-miao.li@intel.com> <20230531053743.129442-1-miao.li@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 31/05/2023 07:37, Miao Li: > This series introduces a VFIO standard capability, called sparse > mmap to PCI bus. In linux kernel, it's defined as > VFIO_REGION_INFO_CAP_SPARSE_MMAP. Sparse mmap means instead of > mmap whole BAR region into DPDK process, only mmap part of the > BAR region after getting sparse mmap information from kernel. > For the rest of BAR region that is not mmap-ed, DPDK process > can use pread/pwrite system calls to access. Sparse mmap is > useful when kernel does not want userspace to mmap whole BAR > region, or kernel wants to control over access to specific BAR > region. Vendors can choose to enable this feature or not for > their devices in their specific kernel modules. > > In this patchset: > > Patch 1-3 is mainly for introducing BAR access APIs so that > driver could use them to access specific BAR using pread/pwrite > system calls when part of the BAR is not mmap-able. Patch 4 > adds the VFIO sparse mmap support finally. > > v4: > 1. add sparse mmap information allocation and release > 2. add release note for BAR access APIs > > v3: > fix variable 'pdev' and 'info' uninitialized error > > v2: > 1. add PCI device internal structure in bus/pci/windows/pci.c > 2. fix parameter type error > > Chenbo Xia (3): > bus/pci: introduce an internal representation of PCI device > bus/pci: avoid depending on private value in kernel source > bus/pci: introduce helper for MMIO read and write > > Miao Li (1): > bus/pci: add VFIO sparse mmap support Applied, thanks. Is there some drivers which may reuse the new MMIO helpers?