From: David Marchand <david.marchand@redhat.com>
To: fengchengwen <fengchengwen@huawei.com>
Cc: Aaron Conole <aconole@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>, dev <dev@dpdk.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v2 3/3] test: support trace-autotest when enable trace
Date: Tue, 21 Jun 2022 11:06:37 +0200 [thread overview]
Message-ID: <CAJFAV8ybaAC4Gtorm2LVW1B0g9W8du4Gxoyv0qnBkCtGhLD3Ug@mail.gmail.com> (raw)
In-Reply-To: <382eda43-9a03-60b9-ea8c-316e44a29d1f@huawei.com>
On Fri, Jun 17, 2022 at 4:43 AM fengchengwen <fengchengwen@huawei.com> wrote:
>
> Hi David, thanks for your review.
>
> On 2022/6/15 22:00, David Marchand wrote:
> > On Tue, Jun 14, 2022 at 8:06 AM Chengwen Feng <fengchengwen@huawei.com> wrote:
> >>
> >> There are a bug[1] when exit application while enable tracing, this
> >> bug has not been discovered for a long time, to quickly detect such
> >> bugs, this patch was introduced.
> >>
> >> This patch adds a testcase with trace enabling, it also depends on
> >> patch[2] because it has a long file-prefix.
> >>
> >> [1] eal: fix segment fault when exit trace
> >> [2] eal: fix trace init fail with long file-prefix
> >
> > This commitlog feels more like a cover letter.
> >
> > Please describe what the impact of the patch is, like mention that the
> > trace_autotest unit test is being called twice, once with traces
> > disabled, and once with traces enabled.
> > And that the traces file is being written in a directory part of the
> > build directory.
> >
> >
> >>
> >> Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
> >> ---
> >> app/test/meson.build | 11 +++++++++++
> >> 1 file changed, 11 insertions(+)
> >>
> >> diff --git a/app/test/meson.build b/app/test/meson.build
> >> index 7fe261cae8..eb37aa632a 100644
> >> --- a/app/test/meson.build
> >> +++ b/app/test/meson.build
> >> @@ -509,6 +509,17 @@ foreach arg : fast_tests
> >> is_parallel : false,
> >> suite : 'fast-tests')
> >> endif
> >> +
> >> + if run_test and arg[0] == 'trace_autotest' and (not is_windows)
> >
> > Calling this test on Windows should not be an issue.
> > Is it not the case?
>
> I notice that eal_parse_common_option still keep windows macro for trace parameter parse:
>
> #ifndef RTE_EXEC_ENV_WINDOWS
> case OPT_TRACE_NUM: {
> ...
> case OPT_TRACE_MODE_NUM: {
> if (eal_trace_mode_args_save(optarg) < 0) {
> RTE_LOG(ERR, EAL, "invalid parameters for --"
> OPT_TRACE_MODE "\n");
> return -1;
> }
> break;
> }
> #endif /* !RTE_EXEC_ENV_WINDOWS */
>
> Maybe trace already support in windows, but I havn't the windows enviorment to verify it.
>
> So I think we should keep '(not is_windows)' currently.
Indeed.
--
David Marchand
next prev parent reply other threads:[~2022-06-21 9:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 12:00 [PATCH] eal: fix segment fault when exit trace Chengwen Feng
2022-06-07 12:26 ` fengchengwen
2022-06-13 14:15 ` David Marchand
2022-06-14 0:33 ` fengchengwen
2022-06-07 13:00 ` David Marchand
2022-06-08 10:31 ` Jerin Jacob
2022-06-14 5:58 ` [PATCH v2 0/3] bugfix for trace Chengwen Feng
2022-06-14 5:58 ` [PATCH v2 1/3] eal: fix segment fault when exit trace Chengwen Feng
2022-06-14 8:25 ` David Marchand
2022-06-14 5:58 ` [PATCH v2 2/3] eal: fix trace init fail with long file-prefix Chengwen Feng
2022-06-15 14:02 ` David Marchand
2022-06-15 18:11 ` Jerin Jacob
2022-06-14 5:59 ` [PATCH v2 3/3] test: support trace-autotest when enable trace Chengwen Feng
2022-06-15 14:00 ` David Marchand
2022-06-17 2:42 ` fengchengwen
2022-06-21 9:06 ` David Marchand [this message]
2022-06-17 2:29 ` [PATCH v3 0/4] bugfix for trace Chengwen Feng
2022-06-17 2:29 ` [PATCH v3 1/4] eal: fix segment fault when exit trace Chengwen Feng
2022-06-17 2:29 ` [PATCH v3 2/4] eal: fix errno not set if strftime return zero Chengwen Feng
2022-06-21 9:05 ` David Marchand
2022-06-17 2:29 ` [PATCH v3 3/4] eal: fix trace init fail with long file-prefix Chengwen Feng
2022-06-17 2:29 ` [PATCH v3 4/4] test: introduce trace-autotest with traces enabled Chengwen Feng
2022-06-21 9:07 ` David Marchand
2022-06-21 9:07 ` [PATCH v3 0/4] bugfix for trace 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=CAJFAV8ybaAC4Gtorm2LVW1B0g9W8du4Gxoyv0qnBkCtGhLD3Ug@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=jerinj@marvell.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).