DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, Bruce Richardson <bruce.richardson@intel.com>,
	Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
	Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>,
	Dmitry Malloy <dmitrym@microsoft.com>,
	Pallavi Kadam <pallavi.kadam@intel.com>,
	Ray Kinsella <mdr@ashroe.eu>, Neil Horman <nhorman@tuxdriver.com>,
	Matan Azrad <matan@nvidia.com>,
	Shahaf Shuler <shahafs@nvidia.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH v2] build: list symbols exports in a single file
Date: Wed, 07 Apr 2021 00:39:59 +0200
Message-ID: <2532967.nAU1F58lTY@thomas> (raw)
In-Reply-To: <CAJFAV8xW=b6Ri1A5QUATgWyNA9SfjdnNNHW+Y-DnU2wWjwAmzw@mail.gmail.com>

06/04/2021 22:09, David Marchand:
> On Tue, Apr 6, 2021 at 8:53 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> >
> > About the title, it is not a single file but one file per lib/driver.
> > I think it would better convey the idea by saying "remove .def files".
> 
> Ok.
> 
> >
> > 06/04/2021 19:59, David Marchand:
> > > Rather than have two files that keeps getting out of sync, let's
> > > annotate the version.map to generate the Windows export file.
> > >
> > > Note: Existing version.map annotation achieved with:
> > > $ for dir in lib/librte_eal drivers/common/mlx5; do
> > >     ./buildtools/map-list-symbol.sh $dir/*.map |
> > >     while read file version sym; do
> > >       ! git grep -qw $sym $dir/*.def || continue;
> > >       sed -i -e "s/$sym;/$sym; # WINDOWS_NO_EXPORT/" $dir/*.map;
> > >     done;
> > >   done
> >
> > This patch keeps the exact same behaviour, right?
> 
> I checked by sorting/diff'ing previously committed .def files for EAL
> and common/mlx5 with the newly generated ones.
> No difference, once aligning the mlx5 version.map.
> 
> There is one change in behavior.
> I thought as exports.def being a subset of the map files, and this
> patch enforces it.
> It seems there were some tries at going the opposite way, looking at
> the comment in check-symbol-maps.sh.
> But looking at the current common/mlx5 state, I don't see this as a
> requirement (Linux and Windows share the same interface).
> 
> 
> > There are a lot of symbols in EAL and mlx5 which should
> > be exported for Windows too, but it is open for future fixes, right?
> 
> Not sure I get this question.
> 
> We have exports missing in EAL for some series posted on the ml
> waiting for merges.
> I suspect some recent merged changes have issues too (but did not check yet).
> This current patch does not address such issues and we need fixes
> afterwards if this is what you mean.

Yes this is what I mean.
I wanted to make clear to people in Cc list that some fixes are required
as follow-up: some symbols in EAL and mlx5 are missing for Windows.




  reply	other threads:[~2021-04-06 22:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06 16:32 [dpdk-dev] [PATCH] " David Marchand
2021-04-06 16:40 ` David Marchand
2021-04-06 16:50 ` Bruce Richardson
2021-04-06 16:53   ` David Marchand
2021-04-07 20:06   ` Kinsella, Ray
2021-04-06 17:59 ` [dpdk-dev] [PATCH v2] " David Marchand
2021-04-06 18:52   ` Thomas Monjalon
2021-04-06 20:09     ` David Marchand
2021-04-06 22:39       ` Thomas Monjalon [this message]
2021-04-07  8:16       ` David Marchand
2021-04-07  8:53         ` Dmitry Kozlyuk
2021-04-07  8:57           ` Thomas Monjalon
2021-04-07 11:38             ` Tal Shnaiderman
2021-04-08 14:51   ` Thomas Monjalon
2021-04-08 16:11   ` David Marchand

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=2532967.nAU1F58lTY@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=dmitrym@microsoft.com \
    --cc=matan@nvidia.com \
    --cc=mdr@ashroe.eu \
    --cc=navasile@linux.microsoft.com \
    --cc=nhorman@tuxdriver.com \
    --cc=pallavi.kadam@intel.com \
    --cc=shahafs@nvidia.com \
    --cc=viacheslavo@nvidia.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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git