From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/4 V4] GDB Performance testing
Date: Wed, 06 Nov 2013 06:42:00 -0000 [thread overview]
Message-ID: <5279D384.2080901@codesourcery.com> (raw)
In-Reply-To: <1383291300-13917-1-git-send-email-yao@codesourcery.com>
On 11/01/2013 03:34 PM, Yao Qi wrote:
> The changes in V4 can be found in each patch.
>
> The basic usages of performance testing are,
>
> $ make check-perf
> $ make check-perf RUNTESTFLAGS="--target_board=native-gdbserver solib.exp"
> $ make check-perf RUNTESTFLAGS="solib.exp SOLIB_COUNT=512"
>
> We can skip compilation step like,
>
> $ make check-perf RUNTESTFLAGS='solib.exp GDB_PERFTEST_MODE=run'
>
> or only compile test cases,
>
> $ make check-perf RUNTESTFLAGS='solib.exp GDB_PERFTEST_MODE=compile'
>
> in default, GDB_PERFTEST_MODE=both.
>
> If the perf test case takes much time, we can specify timeout by
> GDB_PERFTEST_TIMEOUT=1000.
>
> $ make check-perf RUNTESTFLAGS="--target_board=native-gdbserver GDB_PERFTEST_TIMEOUT=4000 solib.exp"
This patch series is committed! Thanks to Doug and Tom's patient
review. I'll submit other test cases and try to run them nightly to
monitor performance changes.
--
Yao (é½å°§)
prev parent reply other threads:[~2013-11-06 5:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 7:36 Yao Qi
2013-11-01 7:36 ` [PATCH 3/4] Mention perf test in testsuite/README Yao Qi
2013-11-01 7:36 ` [PATCH 1/4] New make target 'check-perf' and new dir gdb.perf Yao Qi
2013-11-01 7:36 ` [PATCH 2/4] Perf test framework Yao Qi
2013-11-01 19:43 ` Doug Evans
2013-11-01 20:46 ` Tom Tromey
2013-11-02 2:42 ` Yao Qi
2013-11-04 16:27 ` Tom Tromey
2013-11-06 5:30 ` Yao Qi
2013-11-01 7:36 ` [PATCH 4/4] Test on solib load and unload Yao Qi
2013-11-01 20:35 ` Tom Tromey
2013-11-02 2:50 ` Yao Qi
2013-11-04 17:37 ` Tom Tromey
2013-11-06 6:42 ` Yao Qi [this message]
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=5279D384.2080901@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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