DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Michael Piszczek <mpiszczek@ddn.com>
Cc: Vipin.Varghese@amd.com, dev@dpdk.org
Subject: Re: [PATCH v4] pci: read amd iommu virtual address width
Date: Wed, 12 Oct 2022 10:18:27 +0100	[thread overview]
Message-ID: <c08a92fc-9d73-cfbb-0d5b-8ab68bcc4f73@amd.com> (raw)
In-Reply-To: <20221011140854.777428-1-mpiszczek@ddn.com>

On 10/11/2022 3:08 PM, Michael Piszczek wrote:
> Add code to read the virtual address width for AMD processors.
> 
> Signed-off-by: Michael Piszczek <mpiszczek@ddn.com>
> ---
>   drivers/bus/pci/linux/pci.c | 48 ++++++++++++++++++++++++-------------
>   1 file changed, 32 insertions(+), 16 deletions(-)
> 
> diff --git a/drivers/bus/pci/linux/pci.c b/drivers/bus/pci/linux/pci.c
> index ebd1395502..cdac634e6c 100644
> --- a/drivers/bus/pci/linux/pci.c
> +++ b/drivers/bus/pci/linux/pci.c
> @@ -480,15 +480,18 @@ rte_pci_scan(void)
>   }
>   
>   #if defined(RTE_ARCH_X86)
> +
>   bool
>   pci_device_iommu_support_va(const struct rte_pci_device *dev)
>   {
>   #define VTD_CAP_MGAW_SHIFT	16
>   #define VTD_CAP_MGAW_MASK	(0x3fULL << VTD_CAP_MGAW_SHIFT)
> +#define RD_AMD_CAP_VASIZE_SHIFT 15
> +#define RD_AMD_CAP_VASIZE_MASK  (0x7F << RD_AMD_CAP_VASIZE_SHIFT)
>   	const struct rte_pci_addr *addr = &dev->addr;
>   	char filename[PATH_MAX];
>   	FILE *fp;
> -	uint64_t mgaw, vtd_cap_reg = 0;
> +	uint64_t mgaw = 0, cap_reg = 0;
>   
>   	snprintf(filename, sizeof(filename),
>   		 "%s/" PCI_PRI_FMT "/iommu/intel-iommu/cap",
> @@ -496,26 +499,39 @@ pci_device_iommu_support_va(const struct rte_pci_device *dev)
>   		 addr->function);
>   
>   	fp = fopen(filename, "r");
> -	if (fp == NULL) {
> -		/* We don't have an Intel IOMMU, assume VA supported */
> -		if (errno == ENOENT)
> -			return true;
> -
> -		RTE_LOG(ERR, EAL, "%s(): can't open %s: %s\n",
> -			__func__, filename, strerror(errno));
> -		return false;
> -	}
> +	if (fp != NULL) {
> +		/* We have an Intel IOMMU */
> +		if (fscanf(fp, "%" PRIx64, &cap_reg) != 1) {
> +			   RTE_LOG(ERR, EAL, "%s(): can't read %s\n", __func__, filename);
> +			fclose(fp);
> +			return false;
> +		}
>   
> -	/* We have an Intel IOMMU */
> -	if (fscanf(fp, "%" PRIx64, &vtd_cap_reg) != 1) {
> -		RTE_LOG(ERR, EAL, "%s(): can't read %s\n", __func__, filename);
>   		fclose(fp);
> -		return false;
> +		mgaw = ((cap_reg & VTD_CAP_MGAW_MASK) >> VTD_CAP_MGAW_SHIFT) + 1;
>   	}
> +	else {
> +		snprintf(filename, sizeof(filename),
> +			 "%s/" PCI_PRI_FMT "/iommu/amd-iommu/cap",
> +			  rte_pci_get_sysfs_path(), addr->domain, addr->bus, addr->devid,
> +			  addr->function);
> +


As suggested in v3, instead of first trying to open intel file later amd 
file, what do you think to use glob() function to detect the file?

> +		fp = fopen(filename, "r");
> +		if (fp != NULL) {
> +			/* We have an Amd IOMMU */
> +			if (fscanf(fp, "%" PRIx64, &cap_reg) != 1) {
> +				   RTE_LOG(ERR, EAL, "%s(): can't read %s\n", __func__, filename);
> +				fclose(fp);
> +				return false;
> +			}
>   
> -	fclose(fp);
> +			fclose(fp);
> +			mgaw = ((cap_reg & RD_AMD_CAP_VASIZE_MASK) >> RD_AMD_CAP_VASIZE_SHIFT) + 1;
> +		}
> +	}
>   
> -	mgaw = ((vtd_cap_reg & VTD_CAP_MGAW_MASK) >> VTD_CAP_MGAW_SHIFT) + 1;
> +	if (mgaw == 0)
> +		return false;
>   
>   	/*
>   	 * Assuming there is no limitation by now. We can not know at this point


  parent reply	other threads:[~2022-10-12  9:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12 16:01 [PATCH 0/1] " Michael Piszczek
2022-09-12 16:01 ` [PATCH 1/1] " Michael Piszczek
2022-09-14 13:49   ` [PATCH v2] " Michael Piszczek
2022-10-03  7:48     ` David Marchand
2022-10-10 13:12       ` Varghese, Vipin
2022-10-10 21:47   ` [PATCH v3] " Michael Piszczek
2022-10-10 21:47     ` Michael Piszczek
2022-10-11 22:00     ` Ferruh Yigit
2022-10-11 14:08   ` [PATCH v4] " Michael Piszczek
2022-10-11 14:08     ` Michael Piszczek
2022-10-12  9:18     ` Ferruh Yigit [this message]
2022-10-12 15:15     ` Stephen Hemminger
2022-10-13 18:16   ` [PATCH v5] " Michael Piszczek
2022-10-13 18:16     ` Michael Piszczek
2022-10-24 18:09       ` Stephen Hemminger
2022-10-25  7:56         ` Ferruh Yigit
2022-10-17 15:45   ` [PATCH v6] " Michael Piszczek
2022-10-17 15:45     ` Michael Piszczek
2022-10-25 11:54       ` David Marchand
2023-08-08  7:31         ` David Marchand
2023-08-08 13:53           ` Michael Piszczek

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=c08a92fc-9d73-cfbb-0d5b-8ab68bcc4f73@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=Vipin.Varghese@amd.com \
    --cc=dev@dpdk.org \
    --cc=mpiszczek@ddn.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).