From: Thomas Monjalon <thomas@monjalon.net>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] devtools: add script to verify map files
Date: Sun, 27 May 2018 22:50:58 +0200 [thread overview]
Message-ID: <4156041.IfarTdeXU8@xps> (raw)
In-Reply-To: <9253aa4f-17d2-53f7-8b57-4a9b5d6e1f53@intel.com>
Sorry for having missed this patch during so long.
13/02/2018 11:48, Ferruh Yigit:
> On 2/12/2018 4:13 PM, Pavan Nikhilesh wrote:
> > This script checks for the symbols specified in the map files against
> > the symbols present in the map file directory.
> > Currently, the script checks for map files in drivers and lib directory.
> >
> > Example:
> > ./devtools/check-map.py
> >
> > The following symbols are unused :
> >
> > Map file : /home/pavan/Work/clean/dpdk/drivers/mempool/dpaa/...
> > ['rte_dpaa_pool_table']
> >
> > Map file : /home/pavan/Work/clean/dpdk/drivers/bus/fslmc/...
> > ['qbman_get_version', 'qbman_swp_send_multiple']
> >
> > ...
> >
> > Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
>
> +1 to improve our tools.
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
I agree we must have more tools.
I think this check can be a lot simpler as a shell script,
instead of Python. It does not need the list features of Python.
I've run it and I see it does not catch symbols which are renamed
with a prefix. Example:
vfio_get_group_fd became rte_vfio_get_group_fd
next prev parent reply other threads:[~2018-05-27 20:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 16:13 Pavan Nikhilesh
2018-02-13 10:48 ` Ferruh Yigit
2018-05-27 20:50 ` Thomas Monjalon [this message]
2018-05-27 21:54 ` [dpdk-dev] [PATCH v2] devtools: check orphan symbols in " Thomas Monjalon
2018-05-29 15:56 ` Thomas Monjalon
2018-05-28 9:21 ` [dpdk-dev] [PATCH] devtools: add script to verify " Bruce Richardson
2018-05-28 9:31 ` Thomas Monjalon
2018-05-28 13:17 ` Bruce Richardson
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=4156041.IfarTdeXU8@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=pbhagavatula@caviumnetworks.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).