From: David Marchand <david.marchand@redhat.com>
To: Shani Peretz <shperetz@nvidia.com>
Cc: chenbox@nvidia.com, dev@dpdk.org, dsosnowski@nvidia.com,
jblunck@infradead.org, mkashani@nvidia.com, nipun.gupta@amd.com,
roretzla@linux.microsoft.com, thomas@monjalon.net
Subject: Re: [PATCH v3] eal/common: fix inconsistent representation of PCI numbers
Date: Fri, 12 Jul 2024 15:49:59 +0200 [thread overview]
Message-ID: <CAJFAV8yraBEUXMZcra_ia8_G1StmE3ih4fg=VUQ6zmXy6V4tzg@mail.gmail.com> (raw)
In-Reply-To: <20240708165145.1405107-1-shperetz@nvidia.com>
On Mon, Jul 8, 2024 at 6:52 PM Shani Peretz <shperetz@nvidia.com> wrote:
>
> DPDK allows for two ways to specify PCI device numbers:
> a full version ("0000:08:00.0") and a short version ("08:00.0").
> The problem arises when the application uses one format (e.g., full)
> when running testpmd, but then tries to use the other format (e.g., short)
> in a subsequent command, leading to a failure.
>
> The cmp_dev_name func, which is responsible for comparing PCI device names,
> is not handling the inconsistent PCI number representations correctly.
> The suggested fix is to use the pci_parse function, which can parse
> the PCI device name and fill a struct rte_pci_addr with the standardized
> representation of the PCI number.
> By comparing the struct rte_pci_addr instances instead of the string
> representations, the application can ensure consistent handling of
> PCI device numbers, regardless of the format used.
>
> Fixes: a3ee360f4440 ("eal: add hotplug add/remove device")
> Cc: jblunck@infradead.org
>
> Signed-off-by: Shani Peretz <shperetz@nvidia.com>
> Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
> Acked-by: Thomas Monjalon <thomas@monjalon.net>
I find it strange that Thomas acked this patch (for example, the
commit title prefix is wrong).
I don't understand the issue.
Please provide a reproducer.
And ideally we need a unit test to track regressions on this topic.
Thanks.
--
David Marchand
next prev parent reply other threads:[~2024-07-12 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 20:01 [PATCH] " Shani Peretz
2024-07-01 22:00 ` Stephen Hemminger
2024-07-08 16:51 ` [PATCH v3] " Shani Peretz
2024-07-12 13:49 ` David Marchand [this message]
2024-07-12 17:55 ` Thomas Monjalon
2024-10-04 22:21 ` [PATCH] " Stephen Hemminger
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='CAJFAV8yraBEUXMZcra_ia8_G1StmE3ih4fg=VUQ6zmXy6V4tzg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=jblunck@infradead.org \
--cc=mkashani@nvidia.com \
--cc=nipun.gupta@amd.com \
--cc=roretzla@linux.microsoft.com \
--cc=shperetz@nvidia.com \
--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).