qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RISU PATCH v5 12/13] new: record_traces.sh helper script
Date: Tue, 20 Jun 2017 15:57:37 +0100	[thread overview]
Message-ID: <87vanqu2ou.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA_oRmWiQKyj=xSHyR1n-zDWfGJ4n3d4DzzWQtn3rTr1yA@mail.gmail.com>


Peter Maydell <peter.maydell@linaro.org> writes:

> On 19 June 2017 at 11:46, Alex Bennée <alex.bennee@linaro.org> wrote:
>> A simple script to run through a bunch of binaries and generate their
>> trace files.
>>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>>
>> ---
>> v5
>>   - author, license and usage header
>> v3
>>   - allow overriding of RISU binary
>> ---
>>  record_traces.sh | 32 ++++++++++++++++++++++++++++++++
>>  1 file changed, 32 insertions(+)
>>  create mode 100755 record_traces.sh
>
> Another one for contrib/, I think.

OK will do.

>
> thanks
> -- PMM


--
Alex Bennée

  reply	other threads:[~2017-06-20 14:57 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-19 10:46 [Qemu-devel] [RISU PATCH v5 00/13] RISU record/replay patches Alex Bennée
2017-06-19 10:46 ` [Qemu-devel] [RISU PATCH v5 01/13] .gitignore: ignore build directories Alex Bennée
2017-06-19 10:46 ` [Qemu-devel] [RISU PATCH v5 02/13] README: document the coding style used for risu Alex Bennée
2017-06-20 12:54   ` Peter Maydell
2017-06-19 10:46 ` [Qemu-devel] [RISU PATCH v5 03/13] all: fix up code consitency Alex Bennée
2017-06-20 13:13   ` Peter Maydell
2017-06-20 14:16     ` Peter Maydell
2017-06-19 10:46 ` [Qemu-devel] [RISU PATCH v5 04/13] build-all-archs: support --static flag Alex Bennée
2017-06-20 14:07   ` Peter Maydell
2017-06-19 10:46 ` [Qemu-devel] [RISU PATCH v5 05/13] build-all-archs: support cross building via docker Alex Bennée
2017-06-20 14:09   ` Peter Maydell
2017-06-20 14:57     ` Alex Bennée
2017-06-19 10:46 ` [Qemu-devel] [RISU PATCH v5 06/13] risu: a bit more verbosity when starting Alex Bennée
2017-06-20 13:33   ` Peter Maydell
2017-06-19 10:46 ` [Qemu-devel] [RISU PATCH v5 07/13] risu: paramterise send/receive functions Alex Bennée
2017-06-20 13:40   ` Peter Maydell
2017-06-20 13:54     ` Alex Bennée
2017-06-29 15:45     ` Alex Bennée
2017-06-19 10:46 ` [Qemu-devel] [RISU PATCH v5 08/13] risu: add header to trace stream Alex Bennée
2017-06-20 13:55   ` Peter Maydell
2017-06-19 10:46 ` [Qemu-devel] [RISU PATCH v5 09/13] risu: add simple trace and replay support Alex Bennée
2017-06-20 14:06   ` Peter Maydell
2017-06-19 10:46 ` [Qemu-devel] [RISU PATCH v5 10/13] risu: handle trace through stdin/stdout Alex Bennée
2017-06-20 14:14   ` Peter Maydell
2017-06-20 14:58     ` Alex Bennée
2017-06-19 10:46 ` [Qemu-devel] [RISU PATCH v5 11/13] risu: add support compressed tracefiles Alex Bennée
2017-06-20 14:15   ` Peter Maydell
2017-06-19 10:46 ` [Qemu-devel] [RISU PATCH v5 12/13] new: record_traces.sh helper script Alex Bennée
2017-06-20 14:12   ` Peter Maydell
2017-06-20 14:57     ` Alex Bennée [this message]
2017-06-19 10:46 ` [Qemu-devel] [RISU PATCH v5 13/13] new: run_risu.sh script Alex Bennée
2017-06-20 14:11   ` Peter Maydell
2017-06-20 14:57     ` Alex Bennée

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=87vanqu2ou.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).