From: Stephen Hemminger <stephen@networkplumber.org>
To: Jeff Shaw <jeffrey.b.shaw@intel.com>
Cc: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: simplify RTE_PMD_DEBUG_TRACE
Date: Fri, 14 Dec 2018 13:57:59 -0800 [thread overview]
Message-ID: <20181214135759.02f97f36@xeon-e3> (raw)
In-Reply-To: <20181214212007.GA6612@ae13-28.jf.intel.com>
On Fri, 14 Dec 2018 13:20:07 -0800
Jeff Shaw <jeffrey.b.shaw@intel.com> wrote:
> On Fri, Dec 14, 2018 at 12:50:55PM -0800, Stephen Hemminger wrote:
> > Use rte_log directly, eliminating no longer used rte_pmd_dev_trace
> > function. This removes variable length array which is problem on
> > Windows and other compilers not doing C99.
> >
> > Also, drop unused RTE_PROC_PRIMARY macros.
> >
> > Reported-by: Jeff Shaw <jeffrey.b.shaw@intel.com>
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> > ---
> > lib/librte_eal/common/include/rte_dev.h | 43 ++-----------------------
> > 1 file changed, 3 insertions(+), 40 deletions(-)
> >
> > diff --git a/lib/librte_eal/common/include/rte_dev.h b/lib/librte_eal/common/include/rte_dev.h
> > index a9724dc9181c..e496da440028 100644
> > --- a/lib/librte_eal/common/include/rte_dev.h
> > +++ b/lib/librte_eal/common/include/rte_dev.h
> > @@ -43,54 +43,17 @@ typedef void (*rte_dev_event_cb_fn)(const char *device_name,
> > enum rte_dev_event_type event,
> > void *cb_arg);
> >
> > -__attribute__((format(printf, 2, 0)))
> > -static inline void
> > -rte_pmd_debug_trace(const char *func_name, const char *fmt, ...)
> > -{
> > - va_list ap;
> > -
> > - va_start(ap, fmt);
> > -
> > - {
> > - char buffer[vsnprintf(NULL, 0, fmt, ap) + 1];
> > -
> > - va_end(ap);
> > -
> > - va_start(ap, fmt);
> > - vsnprintf(buffer, sizeof(buffer), fmt, ap);
> > - va_end(ap);
> > -
> > - rte_log(RTE_LOG_ERR, RTE_LOGTYPE_PMD, "%s: %s",
> > - func_name, buffer);
> > - }
> > -}
> > -
>
> Will this break applications that try to use this function? Because it is not
> a documented function, is there no guarantee it will be present?
It shouldn't be visible as part of EAL. Any code that was built that had
old MACRO would still run (ABI compatible) because it was inline.
next prev parent reply other threads:[~2018-12-14 21:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 16:38 [dpdk-dev] [PATCH] eal: remove variable length array Jeff Shaw
2018-12-14 18:36 ` Stephen Hemminger
2018-12-14 18:59 ` Jeff Shaw
2018-12-14 19:17 ` Jeff Shaw
2018-12-14 18:36 ` Mattias Rönnblom
2018-12-14 19:07 ` Jeff Shaw
2018-12-14 20:28 ` Mattias Rönnblom
2018-12-14 20:50 ` [dpdk-dev] [PATCH] eal: simplify RTE_PMD_DEBUG_TRACE Stephen Hemminger
2018-12-14 21:20 ` Jeff Shaw
2018-12-14 21:57 ` Stephen Hemminger [this message]
2018-12-21 16:17 ` Ferruh Yigit
2018-12-21 18:11 ` [dpdk-dev] [PATCH v2] " Jeff Shaw
2018-12-21 18:18 ` [dpdk-dev] [PATCH v3] " Jeff Shaw
2018-12-22 0:37 ` Ferruh Yigit
2018-12-19 21:45 ` [dpdk-dev] [PATCH] eal: remove variable length array Thomas Monjalon
2018-12-20 10:53 ` Mattias Rönnblom
2018-12-20 11:03 ` Thomas Monjalon
2018-12-14 20:40 ` [dpdk-dev] [PATCH v2] " Jeff Shaw
2018-12-15 14:26 ` Wiles, Keith
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=20181214135759.02f97f36@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=jeffrey.b.shaw@intel.com \
--cc=mattias.ronnblom@ericsson.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).