From: Stan Shebs <stanshebs@earthlink.net>
To: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Tracepoint speed test
Date: Fri, 09 Sep 2011 07:28:00 -0000 [thread overview]
Message-ID: <4E6945E2.7080601@earthlink.net> (raw)
In-Reply-To: <4E69434C.2080907@earthlink.net>
On 9/8/11 3:35 PM, Stan Shebs wrote:
> This patch adds a test of tracepoint speed to the testsuite.
Oh yeah, one other thing to note: the test cases don't actually
regression-test performance numbers, since they will vary randomly; the
numbers are simply printed into the test log. It's not even clear that
we can test that "fast" tracepoints are faster than regular tracepoints,
since a target is not even required to implement them with different
mechanisms.
Stan
stan@codesourcery.com
prev parent reply other threads:[~2011-09-08 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 22:47 Stan Shebs
2011-09-09 7:28 ` Stan Shebs [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=4E6945E2.7080601@earthlink.net \
--to=stanshebs@earthlink.net \
--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