From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8056 invoked by alias); 1 Nov 2013 07:36:40 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 8046 invoked by uid 89); 1 Nov 2013 07:36:39 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FROM_12LTRDOM autolearn=ham version=3.3.2 X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 01 Nov 2013 07:36:37 +0000 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1Vc9HW-0006Qa-65 from Yao_Qi@mentor.com for gdb-patches@sourceware.org; Fri, 01 Nov 2013 00:36:34 -0700 Received: from SVR-ORW-FEM-02.mgc.mentorg.com ([147.34.96.206]) by svr-orw-fem-01.mgc.mentorg.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 1 Nov 2013 00:36:34 -0700 Received: from qiyao.dyndns.org (147.34.91.1) by svr-orw-fem-02.mgc.mentorg.com (147.34.96.168) with Microsoft SMTP Server id 14.2.247.3; Fri, 1 Nov 2013 00:36:33 -0700 From: Yao Qi To: Subject: [PATCH 0/4 V4] GDB Performance testing Date: Fri, 01 Nov 2013 07:36:00 -0000 Message-ID: <1383291300-13917-1-git-send-email-yao@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2013-11/txt/msg00004.txt.bz2 Hi, Here is the V4 of GDB performance testing. Doug approved V3 except patch 2/4. V4 addresses review comments to V3, including Pedro's suggestion on renaming parameters. 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" *** BLURB HERE *** Yao Qi (4): New make target 'check-perf' and new dir gdb.perf Perf test framework Mention perf test in testsuite/README Test on solib load and unload gdb/Makefile.in | 8 + gdb/testsuite/Makefile.in | 4 + gdb/testsuite/README | 27 ++++ gdb/testsuite/configure | 3 +- gdb/testsuite/configure.ac | 2 +- gdb/testsuite/gdb.perf/Makefile.in | 15 ++ gdb/testsuite/gdb.perf/lib/perftest/__init__.py | 17 +++ gdb/testsuite/gdb.perf/lib/perftest/measure.py | 146 ++++++++++++++++++++ gdb/testsuite/gdb.perf/lib/perftest/perftest.py | 73 ++++++++++ gdb/testsuite/gdb.perf/lib/perftest/reporter.py | 64 +++++++++ gdb/testsuite/gdb.perf/lib/perftest/testresult.py | 57 ++++++++ gdb/testsuite/gdb.perf/solib.c | 83 ++++++++++++ gdb/testsuite/gdb.perf/solib.exp | 85 ++++++++++++ gdb/testsuite/gdb.perf/solib.py | 73 ++++++++++ gdb/testsuite/lib/gdb.exp | 16 +++ gdb/testsuite/lib/perftest.exp | 148 +++++++++++++++++++++ 16 files changed, 819 insertions(+), 2 deletions(-) create mode 100644 gdb/testsuite/gdb.perf/Makefile.in create mode 100644 gdb/testsuite/gdb.perf/lib/perftest/__init__.py create mode 100644 gdb/testsuite/gdb.perf/lib/perftest/measure.py create mode 100644 gdb/testsuite/gdb.perf/lib/perftest/perftest.py create mode 100644 gdb/testsuite/gdb.perf/lib/perftest/reporter.py create mode 100644 gdb/testsuite/gdb.perf/lib/perftest/testresult.py create mode 100644 gdb/testsuite/gdb.perf/solib.c create mode 100644 gdb/testsuite/gdb.perf/solib.exp create mode 100644 gdb/testsuite/gdb.perf/solib.py create mode 100644 gdb/testsuite/lib/perftest.exp -- 1.7.7.6