DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
	dev@dpdk.org, stable@dpdk.org, jianfeng.tan@intel.com,
	qi.z.zhang@intel.com, stephen@networkplumber.org,
	santosh.shukla@caviumnetworks.com, thomas@monjalon.net
Cc: peterx@redhat.com
Subject: Re: [dpdk-dev] [PATCH v3] bus/pci: forbid VA as IOVA mode if IOMMU address width too small
Date: Fri, 12 Jan 2018 11:10:51 +0000	[thread overview]
Message-ID: <89c16dd0-3938-f9ae-cc9f-189388abc0a9@intel.com> (raw)
In-Reply-To: <20180112102220.20061-1-maxime.coquelin@redhat.com>

<snip>

> +#if defined(RTE_ARCH_X86)
> +static bool
> +pci_one_device_iommu_support_va(struct rte_pci_device *dev)
> +{
> +#define VTD_CAP_MGAW_SHIFT	16
> +#define VTD_CAP_MGAW_MASK	(0x3fULL << VTD_CAP_MGAW_SHIFT)
> +#define X86_VA_WIDTH 47 /* From Documentation/x86/x86_64/mm.txt */
> +	struct rte_pci_addr *addr = &dev->addr;
> +	char filename[PATH_MAX];
> +	FILE *fp;
> +	uint64_t mgaw, vtd_cap_reg = 0;
> +
> +	snprintf(filename, sizeof(filename),
> +		 "%s/" PCI_PRI_FMT "/iommu/intel-iommu/cap",
> +		 rte_pci_get_sysfs_path(), addr->domain, addr->bus, addr->devid,
> +		 addr->function);
> +	if (access(filename, F_OK) == -1) {
> +		/* We don't have an Intel IOMMU, assume VA supported*/
> +		return true;
> +	}
> +
> +	/* We have an intel IOMMU */
> +	fp = fopen(filename, "r");
> +	if (fp == NULL) {
> +		RTE_LOG(ERR, EAL, "%s(): can't open %s\n", __func__, filename);
> +		return false;
> +	}
> +
> +	if (fscanf(fp, "%lx", &vtd_cap_reg) != 1) {
> +		RTE_LOG(ERR, EAL, "%s(): can't read %s\n", __func__, filename);
> +		fclose(fp);
> +		return false;
> +	}
> +
> +	fclose(fp);

Hi Maxime,

You probably want to use eal_parse_sysfs_value() for this.


-- 
Thanks,
Anatoly

  reply	other threads:[~2018-01-12 11:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12 10:22 Maxime Coquelin
2018-01-12 11:10 ` Burakov, Anatoly [this message]
2018-01-12 13:18   ` Maxime Coquelin
2018-01-12 22:46     ` Chas Williams
2018-01-20 15:30 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon

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=89c16dd0-3938-f9ae-cc9f-189388abc0a9@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=jianfeng.tan@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qi.z.zhang@intel.com \
    --cc=santosh.shukla@caviumnetworks.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /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).