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 4CE3F42C5A; Thu, 8 Jun 2023 09:03:49 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D891E40A84; Thu, 8 Jun 2023 09:03:48 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 16D5B40042 for ; Thu, 8 Jun 2023 09:03:46 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1686207826; 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=+MTAzluE64sHzg/35tdPhG1ixvy2iGEf2DX7ZwE8/r0=; b=iLv26OM6geLWL7yg5uj6/kD+DqgunbVednjGwOqIMGb2NUtX0CbwbDjNDJTpVdgRm6XEiT xPDz5/D/C1Rx9ATpWpj26jLJw9VLc7VxSV/VC1Zl4gUtdFYfeJ92Cu+nxBDIppptdOk2IF s6HkMQJwhOo84krhA1qeFJrqtLmSKbY= Received: from mail-pj1-f71.google.com (mail-pj1-f71.google.com [209.85.216.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-670-swq_2OmjOE-tVqoRuzCl9A-1; Thu, 08 Jun 2023 03:03:45 -0400 X-MC-Unique: swq_2OmjOE-tVqoRuzCl9A-1 Received: by mail-pj1-f71.google.com with SMTP id 98e67ed59e1d1-25658dc0cdaso153965a91.3 for ; Thu, 08 Jun 2023 00:03:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686207824; x=1688799824; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=+MTAzluE64sHzg/35tdPhG1ixvy2iGEf2DX7ZwE8/r0=; b=DMNCTcvZ+ziNcbtwA6KtYS/uLCV2On46X0vu4oQsCSGjdvObsNC1TD0FixZF95004B PAXwiOBn1n28sKd9W7i/Zf7bf6+2EkZHpPxbL1ahn/4F6GBiwzHONu8JlazHeV/Cr2rf ONtcvOn01/qA+m1650d1hA4+OkXVsAJkgyMvl/zOUs0DKjcDbq1XngPwCGobs8SYRMS+ KZGfguNQIv2CphneI30+NPlBE2YyRGP3B74pEzSBiFDR2E0wv7dkNRPjIyNDJQm3h/Vw dvtETvgjyBy+uLA6S4eLUJoqe/KEOzA2oAwnVj8ezO8Xpjhdo4y9VloZ5J8amR9oCHwK GYkw== X-Gm-Message-State: AC+VfDwvHxwEvOOD86j4nYhi08VGzzRRg7iBlSCi4Oy5IMOYYZtlI0Cf QJp7T0TTBbSI9MxaapbKN6WNuTNnZvhyt8nqfj/I+BJEfqIrosjIiAiHEjVNkfIakgDxkhLUrNn GMwyl2v0nsv4EGMLKKlI= X-Received: by 2002:a17:90b:33c7:b0:258:842e:e23b with SMTP id lk7-20020a17090b33c700b00258842ee23bmr3217133pjb.34.1686207824244; Thu, 08 Jun 2023 00:03:44 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5mTOyO5Yby6MzzdiyKyheBz2b2qbAxRraGaX8KcoA+yxnQC1JFDVMktv+Th900haFDU3s0cu5H1SnYwTZ6TpI= X-Received: by 2002:a17:90b:33c7:b0:258:842e:e23b with SMTP id lk7-20020a17090b33c700b00258842ee23bmr3217118pjb.34.1686207823893; Thu, 08 Jun 2023 00:03:43 -0700 (PDT) MIME-Version: 1.0 References: <20230525163116.682000-1-miao.li@intel.com> <20230531053743.129442-1-miao.li@intel.com> In-Reply-To: From: David Marchand Date: Thu, 8 Jun 2023 09:03:32 +0200 Message-ID: Subject: Re: [PATCH v4 0/4] Support VFIO sparse mmap in PCI bus To: "Xia, Chenbo" Cc: Ali Alnubani , "Li, Miao" , "dev@dpdk.org" , "NBU-Contact-Thomas Monjalon (EXTERNAL)" , "skori@marvell.com" , "ferruh.yigit@amd.com" , "Cao, Yahui" , Patrick Robb X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 Hello Chenbo, Patrick, On Thu, Jun 8, 2023 at 8:50=E2=80=AFAM Xia, Chenbo w= rote: > > > 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. > > > > > > > Hello, > > > > I see the build failure Patrick reported as well and can confirm it's > > caused by 095cf6e68b28 ("bus/pci: introduce MMIO read/write"). > > Bugzilla ticket: https://bugs.dpdk.org/show_bug.cgi?id=3D1245 > > Thanks Ali. I just read the bz and understand what's missing. I will send > a patch today. > > But since last time CI is not reporting the error, this time how could I = make > sure the fix will perfectly work? Chenbo, In theory, this error should have been reported so go ahead and post your f= ix. Patrick, This missing report could be a mail delivery issue (I can see the test ran at UNH). I see no trace in test-report ml. Can you look at the reason? Thanks. --=20 David Marchand