DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Gangurde, Abhijit" <abhijit.gangurde@amd.com>
To: David Marchand <david.marchand@redhat.com>
Cc: "Gupta, Nipun" <Nipun.Gupta@amd.com>,
	"Agarwal, Nikhil" <nikhil.agarwal@amd.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Yigit, Ferruh" <Ferruh.Yigit@amd.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>
Subject: RE: [PATCH v3] bus/cdx: provide driver flag for optional resource mapping
Date: Wed, 4 Oct 2023 10:06:44 +0000	[thread overview]
Message-ID: <DM4PR12MB7765A5F8A2FACAB60E947D7C8FCBA@DM4PR12MB7765.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8xBJFp7Qsw1GO9J78rU4v+6DVWyAdykYJBxvyCks2EwgA@mail.gmail.com>

[AMD Official Use Only - General]

> <abhijit.gangurde@amd.com> wrote:
> > @@ -383,10 +384,12 @@ cdx_probe_one_driver(struct rte_cdx_driver *dr,
> >         CDX_BUS_DEBUG("  probe device %s using driver: %s", dev_name,
> >                 dr->driver.name);
> >
> > -       ret = cdx_vfio_map_resource(dev);
> > -       if (ret != 0) {
> > -               CDX_BUS_ERR("CDX map device failed: %d", ret);
> > -               goto error_map_device;
> > +       if (dr->drv_flags & RTE_CDX_DRV_NEED_MAPPING) {
> > +               ret = cdx_vfio_map_resource(dev);
> > +               if (ret != 0) {
> > +                       CDX_BUS_ERR("CDX map device failed: %d", ret);
> > +                       goto error_map_device;
> > +               }
> >         }
> >
> >         /* call the driver probe() function */
> > diff --git a/drivers/bus/cdx/rte_bus_cdx.h b/drivers/bus/cdx/rte_bus_cdx.h
> > new file mode 100644
> > index 0000000000..4ca12f90c4
> > --- /dev/null
> > +++ b/drivers/bus/cdx/rte_bus_cdx.h
> > @@ -0,0 +1,52 @@
> > +/* SPDX-License-Identifier: BSD-3-Clause
> > + * Copyright (C) 2023, Advanced Micro Devices, Inc.
> > + */
> > +
> > +#ifndef RTE_BUS_CDX_H
> > +#define RTE_BUS_CDX_H
> > +
> > +/**
> > + * @file
> > + * CDX device & driver interface
> > + */
> > +
> > +#ifdef __cplusplus
> > +extern "C" {
> > +#endif
> > +
> > +/* Forward declarations */
> > +struct rte_cdx_device;
> > +
> > +/**
> > + * Map the CDX device resources in user space virtual memory address.
> > + *
> > + * Note that driver should not call this function when flag
> > + * RTE_CDX_DRV_NEED_MAPPING is set, as EAL will do that for
> > + * you when it's on.
>
> Why should we export this function in the application ABI, if it is
> only used by drivers?

This can be called from an application as well if this flag is not set hence, we need to export this function.
If needed, I can update the description of the API.

Thanks,
Abhijit

  reply	other threads:[~2023-10-04 10:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 10:39 [PATCH] " Abhijit Gangurde
2023-07-04 11:22 ` Gupta, Nipun
2023-07-05  6:52 ` [PATCH v2] " Abhijit Gangurde
2023-07-11  5:51   ` [PATCH v3] " Abhijit Gangurde
2023-07-11 15:05     ` Gupta, Nipun
2023-09-29 15:17     ` David Marchand
2023-10-04 10:06       ` Gangurde, Abhijit [this message]
2023-10-04 12:54         ` David Marchand
2023-10-13 11:51           ` Gangurde, Abhijit
2023-10-13 12:15             ` David Marchand
2023-07-07  8:35 ` [PATCH] " Gupta, Nipun
2023-10-16  9:16 ` [PATCH v4 1/1] " Abhijit Gangurde
2023-10-16 15:21   ` 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=DM4PR12MB7765A5F8A2FACAB60E947D7C8FCBA@DM4PR12MB7765.namprd12.prod.outlook.com \
    --to=abhijit.gangurde@amd.com \
    --cc=Ferruh.Yigit@amd.com \
    --cc=Nipun.Gupta@amd.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=nikhil.agarwal@amd.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).