DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xiao, QimaiX" <qimaix.xiao@intel.com>
To: "Zhang, AlvinX" <alvinx.zhang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Xing, Beilei" <beilei.xing@intel.com>, "Guo, Jia" <jia.guo@intel.com>
Subject: Re: [dpdk-dev] [PATCH] bus/pci: fix mmap PCI resource
Date: Thu, 9 Jul 2020 02:25:41 +0000	[thread overview]
Message-ID: <MWHPR1101MB22540DE860C4BC63B67FF9E0FB640@MWHPR1101MB2254.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200708092435.9776-1-alvinx.zhang@intel.com>

Tested-by: Xiao Qimai <qimaix.xiao@intel.com>

Regards,
Xiao Qimai

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of alvinx.zhang@intel.com
> Sent: Wednesday, July 8, 2020 5:25 PM
> To: dev@dpdk.org
> Cc: Xing, Beilei <beilei.xing@intel.com>; Guo, Jia <jia.guo@intel.com>
> Subject: [dpdk-dev] [PATCH] bus/pci: fix mmap PCI resource
> 
> From: Alvin Zhang <alvinx.zhang@intel.com>
> 
> When mapping a PCI BAR containing an MSI-X table, some devices do not
> need to actually map this BAR or only need to map part of them, which may
> cause the mapping to fail. Now some checks are added and a non-NULL initial
> value is set to the variable to avoid this situation.
> 
> Fixes: 2fd3567e5425 ("pci: use OS generic memory mapping functions")
> Cc: talshn@mellanox.com
> 
> Signed-off-by: Alvin Zhang <alvinx.zhang@intel.com>
> ---
>  drivers/bus/pci/linux/pci_vfio.c | 12 +++++++++++-
>  1 file changed, 11 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/bus/pci/linux/pci_vfio.c b/drivers/bus/pci/linux/pci_vfio.c
> index fdeb9a8..9143bfc 100644
> --- a/drivers/bus/pci/linux/pci_vfio.c
> +++ b/drivers/bus/pci/linux/pci_vfio.c
> @@ -547,6 +547,14 @@
>  			bar_index,
>  			memreg[0].offset, memreg[0].size,
>  			memreg[1].offset, memreg[1].size);
> +
> +		if (memreg[0].size == 0 && memreg[1].size == 0) {
> +			/* No need to map this BAR */
> +			RTE_LOG(DEBUG, EAL, "Skipping BAR%d\n",
> bar_index);
> +			bar->size = 0;
> +			bar->addr = 0;
> +			return 0;
> +		}
>  	} else {
>  		memreg[0].offset = bar->offset;
>  		memreg[0].size = bar->size;
> @@ -556,7 +564,9 @@
>  	bar_addr = mmap(bar->addr, bar->size, 0, MAP_PRIVATE |
>  			MAP_ANONYMOUS | additional_flags, -1, 0);
>  	if (bar_addr != MAP_FAILED) {
> -		void *map_addr = NULL;
> +		/* Set non NULL initial value for in case of no PCI mapping */
> +		void *map_addr = bar_addr;
> +
>  		if (memreg[0].size) {
>  			/* actual map of first part */
>  			map_addr = pci_map_resource(bar_addr,
> vfio_dev_fd,
> --
> 1.8.3.1


  parent reply	other threads:[~2020-07-09  2:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08  9:24 alvinx.zhang
2020-07-08  9:38 ` David Marchand
2020-07-08 13:58 ` Xia, Chenbo
2020-07-09  5:13   ` Zhang, AlvinX
2020-07-09  5:21     ` Xia, Chenbo
2020-07-09  2:25 ` Xiao, QimaiX [this message]
2020-07-10  9:54 ` David Marchand
2020-07-10 10:07   ` Thomas Monjalon
2020-07-10 12:31     ` Thomas Monjalon
2020-07-10 12:43     ` [dpdk-dev] [dpdk-ci] " Lincoln Lavoie
2020-09-23  7:34     ` [dpdk-dev] " David Marchand
2020-07-11  6:57   ` Zhang, AlvinX

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MWHPR1101MB22540DE860C4BC63B67FF9E0FB640@MWHPR1101MB2254.namprd11.prod.outlook.com \
    --to=qimaix.xiao@intel.com \
    --cc=alvinx.zhang@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jia.guo@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).