From: David Christensen <drc@linux.vnet.ibm.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] bus/pci: support iova=va on PowerNV systems
Date: Mon, 16 Mar 2020 09:09:58 -0700 [thread overview]
Message-ID: <c54a52a5-d865-577b-67b1-84c09e2f6d69@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAJFAV8z8m7sG5hZkTGb=D=x5kDY=uxPqb0uYZazQjVvMEuQ7Mw@mail.gmail.com>
>> Bare metal PowerNV systems include a DPDK supported IOMMU that allows
>> IOVA=VA support. Test for the platform type and report virtual address
>> support if running on a PowerNV system.
...
>>
>> +
>> + char *line = 0;
>
> Nit: NULL
Fixed.
>> + /* Check for a PowerNV platform */
>> + while (getline(&line, &len, fp) != -1) {
>
> From here, you leak line.
>
Fixed.
>
> Nit, to avoid multiple level of indent, how about invert the check:
>
> if (strstr(line, "platform") == NULL)
> continue;
Fixed.
>> + if (strstr(line, "PowerNV") != NULL) {
>> + RTE_LOG(DEBUG, EAL, "Running on a PowerNV system\n");
>
> Not really helpful, it does not indicate that this system iommu supports VA.
This is the advice given by the kernel developer who maintains the IOMMU
code for PPC. There's nothing in the /sys filesystem that describes the
IOMMU like there is in x86_64 platforms. All POWER systems supported by
DPDK have an IOMMU (you can't turn it off). This is true for both bare
metal systems like PowerNV (Power Non-Virtualized) as well as
virtualized systems like QEMU/KVM and PowerVM LPARs. In the case of
virtualized systems the IOMMU has different capabilities and is not
currently supported in DPDK. Thus, if I know the platform I'm running
on then I know the IOMMU is present and enabled.
Dave
next prev parent reply other threads:[~2020-03-16 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 19:50 David Christensen
2020-03-13 9:09 ` David Marchand
2020-03-16 16:09 ` David Christensen [this message]
2020-03-16 20:38 ` [dpdk-dev] [PATCH v2] " David Christensen
2020-04-25 14:54 ` David Marchand
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=c54a52a5-d865-577b-67b1-84c09e2f6d69@linux.vnet.ibm.com \
--to=drc@linux.vnet.ibm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
/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).