From: Chaoyong He <chaoyong.he@corigine.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
oss-drivers <oss-drivers@corigine.com>,
Zerun Fu <zerun.fu@nephogine.com>,
"mukawa@igel.co.jp" <mukawa@igel.co.jp>,
"stable@dpdk.org" <stable@dpdk.org>,
Long Wu <Long.Wu@nephogine.com>,
Nole Zhang <peng.zhang@corigine.com>
Subject: RE: [PATCH v3 1/2] bus/pci: fix secondary process PCI uio resource map problem
Date: Fri, 28 Jun 2024 01:03:00 +0000 [thread overview]
Message-ID: <SJ0PR13MB5545F6055CC9BC87E106A5479ED02@SJ0PR13MB5545.namprd13.prod.outlook.com> (raw)
In-Reply-To: <2723233.FGBNh6B6GM@thomas>
> 19/04/2024 05:26, Chaoyong He:
> > From: Zerun Fu <zerun.fu@corigine.com>
> >
> > For the primary process, the logic loops all BARs and will skip the
> > map of BAR with an invalid physical address (0), also will assign
> > 'uio_res->nb_maps' with the real mapped BARs number. But for the
> > secondary process, instead of loops all BARs, the logic using the
> > 'uio_res->nb_map' as index. If the device uses continuous BARs there
> > will be no problem, whereas if it uses discrete BARs, it will lead to
> > mapping errors.
> >
> > Fix this problem by also loops all BARs and skip the map of BAR with
> > an invalid physical address in secondary process.
> >
> > Fixes: 9b957f378abf ("pci: merge uio functions for linux and bsd")
> > Cc: mukawa@igel.co.jp
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Zerun Fu <zerun.fu@corigine.com>
> > Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
> > Reviewed-by: Long Wu <long.wu@corigine.com>
> > Reviewed-by: Peng Zhang <peng.zhang@corigine.com>
>
> You should have kept the ack from Anatoly here.
>
> > drivers/bus/pci/pci_common_uio.c | 40
> > ++++++++++++++++++++------------
> > 1 file changed, 25 insertions(+), 15 deletions(-)
>
> There are too many changes in this sensitive code.
> Please could you introduce a first patch for the renaming of the variable "i"?
> It should make this patch simpler to read.
>
> Thank you
>
Okay, will do it in the next version patch.
Thanks for your review.
next prev parent reply other threads:[~2024-06-28 1:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 10:45 [PATCH] " Chaoyong He
[not found] ` <20240129092231.3531217-1-chaoyong.he@corigine.com>
2024-01-29 9:22 ` [PATCH v2 1/2] " Chaoyong He
2024-01-30 4:00 ` fengchengwen
2024-01-30 7:12 ` huangdengdui
2024-03-14 10:55 ` Burakov, Anatoly
2024-01-29 9:22 ` [PATCH v2 2/2] bus/pci: fix secondary process save 'FD' problem Chaoyong He
2024-01-30 6:16 ` fengchengwen
2024-03-14 11:01 ` Burakov, Anatoly
[not found] ` <20240419032630.1215256-1-chaoyong.he@corigine.com>
2024-04-19 3:26 ` [PATCH v3 1/2] bus/pci: fix secondary process PCI uio resource map problem Chaoyong He
2024-06-27 14:00 ` Thomas Monjalon
2024-06-28 1:03 ` Chaoyong He [this message]
2024-04-19 3:26 ` [PATCH v3 2/2] bus/pci: fix secondary process save 'FD' problem Chaoyong He
[not found] ` <20240628073624.4122899-1-chaoyong.he@corigine.com>
2024-06-28 7:36 ` [PATCH v4 2/3] bus/pci: fix secondary process PCI uio resource map problem Chaoyong He
2024-06-28 7:36 ` [PATCH v4 3/3] bus/pci: fix secondary process save 'FD' problem Chaoyong He
2024-07-01 14:14 ` David Marchand
2024-07-02 1:53 ` Chaoyong He
[not found] ` <20240702021946.4194102-1-chaoyong.he@corigine.com>
2024-07-02 2:19 ` [PATCH v5 2/3] bus/pci: fix secondary process PCI uio resource map problem Chaoyong He
2024-07-02 2:19 ` [PATCH v5 3/3] bus/pci: fix secondary process save 'FD' problem Chaoyong He
[not found] ` <20240702074007.1547-1-chaoyong.he@corigine.com>
2024-07-02 7:40 ` [PATCH v6 1/2] bus/pci: fix secondary process PCI uio resource map problem Chaoyong He
2024-07-04 9:00 ` Chenbo Xia
2024-07-02 7:40 ` [PATCH v6 2/2] bus/pci: fix secondary process save 'FD' problem Chaoyong He
2024-07-12 17:30 ` David Marchand
2024-07-15 2:24 ` Chenbo Xia
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=SJ0PR13MB5545F6055CC9BC87E106A5479ED02@SJ0PR13MB5545.namprd13.prod.outlook.com \
--to=chaoyong.he@corigine.com \
--cc=Long.Wu@nephogine.com \
--cc=dev@dpdk.org \
--cc=mukawa@igel.co.jp \
--cc=oss-drivers@corigine.com \
--cc=peng.zhang@corigine.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=zerun.fu@nephogine.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).