From: Thomas Monjalon <thomas@monjalon.net>
To: Vijaya Mohan Guvva <vijay1054@gmail.com>
Cc: dev@dpdk.org, fiona.trahe@intel.com,
Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] bus/pci: pcidev access from secondary process
Date: Tue, 31 Mar 2020 03:54:34 +0200 [thread overview]
Message-ID: <2216574.9XhxPE3A7Q@xps> (raw)
In-Reply-To: <be140b32-8233-19c0-3861-36622be104a7@intel.com>
06/03/2020 13:28, Ferruh Yigit:
> On 3/6/2020 12:02 AM, Vijaya Mohan Guvva wrote:
> > For pci devices presented through igb_uio, pcidev->mem_resource[] is
> > not populated when the device is initialized for secondary process.
> >
> > Initialize pcidev->mem_resource[] with pci-bar mapped addresses.
> >
> > Signed-off-by: Vijaya Mohan Guvva <vijay1054@gmail.com>
>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Do you mean secondary process never worked with igb_uio?
Or is there a specific case?
What is the root cause?
Should it be backported to stable?
next prev parent reply other threads:[~2020-03-31 1:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 0:02 Vijaya Mohan Guvva
2020-03-06 12:28 ` Ferruh Yigit
2020-03-31 1:54 ` Thomas Monjalon [this message]
2020-03-31 2:12 ` vijay mohan
2020-03-31 9:11 ` Thomas Monjalon
2020-04-24 17:08 Vijaya Mohan Guvva
2020-04-25 20:28 ` 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=2216574.9XhxPE3A7Q@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=fiona.trahe@intel.com \
--cc=vijay1054@gmail.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).