From: Jiri Olsa <jolsa@redhat.com>
To: Jiri Pirko <jiri@mellanox.com>
Cc: Jiri Olsa <jolsa@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>, Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
"Steven Rostedt (Red Hat)" <rostedt@goodmis.org>
Subject: Re: [PATCH 3/3] perf tests: Add is_printable_array test
Date: Mon, 18 Jul 2016 14:14:09 +0200 [thread overview]
Message-ID: <20160718121409.GA4017@krava> (raw)
In-Reply-To: <20160718114602.GK2075@nanopsycho.orion>
On Mon, Jul 18, 2016 at 01:46:02PM +0200, Jiri Pirko wrote:
SNIP
> >diff --git a/tools/perf/tests/is_printable_array.c b/tools/perf/tests/is_printable_array.c
> >new file mode 100644
> >index 000000000000..42e13393e502
> >--- /dev/null
> >+++ b/tools/perf/tests/is_printable_array.c
> >@@ -0,0 +1,36 @@
> >+#include <linux/compiler.h>
> >+#include "tests.h"
> >+#include "debug.h"
> >+#include "util.h"
> >+
> >+int test__is_printable_array(int subtest __maybe_unused)
> >+{
> >+ char buf1[] = { 'k', 'r', 4, 'v', 'a', 0 };
> >+ char buf2[] = { 'k', 'r', 'a', 'v', 4, 0 };
> >+ struct {
> >+ char *buf;
> >+ unsigned int len;
> >+ int ret;
> >+ } t[] = {
> >+ { (char *) "krava", sizeof("krava"), 1 },
> >+ { (char *) "krava", sizeof("krava") - 1, 0 },
>
> "a cow" ? Really? :))
yea, trying to force it as 'perf animal' instead of that pony stuff ;-)
http://www.brendangregg.com/blog/2015-07-08/choosing-a-linux-tracer.html
jirka
next prev parent reply other threads:[~2016-07-18 12:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-16 16:11 [PATCHv3 0/3] perf python: Add support to access tracepoint fields Jiri Olsa
2016-07-16 16:11 ` [PATCH 1/3] perf script python: Fix string vs byte array resolving Jiri Olsa
2016-07-18 11:44 ` Jiri Pirko
2016-07-19 6:54 ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-07-16 16:11 ` [PATCH 2/3] perf tools: Make is_printable_array global Jiri Olsa
2016-07-18 11:44 ` Jiri Pirko
2016-07-19 6:54 ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-07-16 16:11 ` [PATCH 3/3] perf tests: Add is_printable_array test Jiri Olsa
2016-07-18 11:46 ` Jiri Pirko
2016-07-18 12:14 ` Jiri Olsa [this message]
2016-07-18 22:49 ` Arnaldo Carvalho de Melo
2016-07-19 6:55 ` [tip:perf/core] " tip-bot for Jiri Olsa
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=20160718121409.GA4017@krava \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jiri@mellanox.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.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).