From: Thomas Monjalon <thomas@monjalon.net>
To: Alejandro Lucero <alejandro.lucero@netronome.com>
Cc: dev@dpdk.org, "Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] bus/pci: use device driver name instead of handler type
Date: Mon, 29 Oct 2018 01:05:38 +0100 [thread overview]
Message-ID: <3242136.KigKuMniXL@xps> (raw)
In-Reply-To: <073701fc-1189-19f8-a635-4e92e52f948b@intel.com>
26/10/2018 16:03, Burakov, Anatoly:
> On 25-Oct-18 11:49 AM, Alejandro Lucero wrote:
> > Invoking the right pci read/write functions is based on interrupt
> > handler type. However, this is not configured for secondary processes
> > precluding to use those functions.
> >
> > This patch fixes the issue using the driver name the device is bound
> > to instead.
> >
> > Fixes: 632b2d1deeed ("eal: provide functions to access PCI config")
> >
> > v2:
> > - Use #ifdef for VFIO functions
> >
> > Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com>
> > ---
> > drivers/bus/pci/linux/pci.c | 32 ++++++++++++++------------------
> > 1 file changed, 14 insertions(+), 18 deletions(-)
> >
> > diff --git a/drivers/bus/pci/linux/pci.c b/drivers/bus/pci/linux/pci.c
> > index 5cf78d7..59a2086 100644
> > --- a/drivers/bus/pci/linux/pci.c
> > +++ b/drivers/bus/pci/linux/pci.c
> > @@ -673,23 +673,21 @@ enum rte_iova_mode
> > int rte_pci_read_config(const struct rte_pci_device *device,
> > void *buf, size_t len, off_t offset)
> > {
> > + char devname[RTE_DEV_NAME_MAX_LEN] = {0};
>
> Probably "" instead of {0} is better. Same in other case.
>
> Otherwise, LGTM
>
> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
Applied with above change, thanks.
Title fixed: bus/pci: compare kernel driver instead of interrupt handler
next prev parent reply other threads:[~2018-10-29 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 10:49 Alejandro Lucero
2018-10-26 14:03 ` Burakov, Anatoly
2018-10-29 0:05 ` Thomas Monjalon [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-25 10:48 Alejandro Lucero
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=3242136.KigKuMniXL@xps \
--to=thomas@monjalon.net \
--cc=alejandro.lucero@netronome.com \
--cc=anatoly.burakov@intel.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).