From: jolsa@redhat.com (Jiri Olsa)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] arm64: perf test: Improbe bp_signal
Date: Tue, 5 Jan 2016 10:09:03 +0100 [thread overview]
Message-ID: <20160105090903.GD2192@krava.brq.redhat.com> (raw)
In-Reply-To: <1451969880-14877-1-git-send-email-wangnan0@huawei.com>
On Tue, Jan 05, 2016 at 04:58:00AM +0000, Wang Nan wrote:
SNIP
> * Following processing should happen:
> @@ -141,6 +203,21 @@ int test__bp_signal(int subtest __maybe_unused)
> * - fd1 event breakpoint hit -> count1 == 1
> * - SIGIO is delivered -> overflows == 1
> * - fd2 event breakpoint hit -> count2 == 1
> + * - SIGUSR1 is delivered -> overflows_2 == 1 (nested signal)
> + * - sig_handler_2 return
> + * - sig_handler return
> + * - fd3 event watchpoint hit -> count3 == 1 (wp and bp in one insn)
> + * - SIGIO is delivered -> overflows == 2
> + * - fd2 event breakpoint hit -> count2 == 2
> + * - SIGUSR1 is delivered -> overflows_2 == 2
> + * - sig_handler_2 return
> + * - sig_handler return
> + * - fd3 event watchpoint hit -> count3 == 2 (standalone wp)
> + * - SIGIO is delivered -> overflows = 3
> + * - fd2 event breakpoint hit -> count2 == 3
> + * - SIGUSR1 is delivered -> overflows_2 == 3
> + * - sig_handler_2 return
> + * - sig_handler return
also each line in here could be prefixed with 'code action'
that led to the result on the line, like:
* exec: result:
*
* __test_function - fd1 event breakpoint hit -> count1 == 1
* - SIGIO is delivered -> overflows == 1
* sig_handler - fd2 event breakpoint hit -> count2 == 1
* - SIGUSR1 is delivered -> overflows_2 == 1 (nested signal)
* - sig_handler_2 return
* - sig_handler return
* incq (%rdi) - fd3 event watchpoint hit -> count3 == 1 (wp and bp in one insn)
* - SIGIO is delivered -> overflows == 2
hum.. but it might take all the fun out of it ;-)
jirka
WARNING: multiple messages have this Message-ID (diff)
From: Jiri Olsa <jolsa@redhat.com>
To: Wang Nan <wangnan0@huawei.com>
Cc: will.deacon@arm.com, takahiro.akashi@linaro.org,
guohanjun@huawei.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, fengguang.wu@intel.com,
pi3orama@163.com, Jiri Olsa <jolsa@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [RFC PATCH] arm64: perf test: Improbe bp_signal
Date: Tue, 5 Jan 2016 10:09:03 +0100 [thread overview]
Message-ID: <20160105090903.GD2192@krava.brq.redhat.com> (raw)
In-Reply-To: <1451969880-14877-1-git-send-email-wangnan0@huawei.com>
On Tue, Jan 05, 2016 at 04:58:00AM +0000, Wang Nan wrote:
SNIP
> * Following processing should happen:
> @@ -141,6 +203,21 @@ int test__bp_signal(int subtest __maybe_unused)
> * - fd1 event breakpoint hit -> count1 == 1
> * - SIGIO is delivered -> overflows == 1
> * - fd2 event breakpoint hit -> count2 == 1
> + * - SIGUSR1 is delivered -> overflows_2 == 1 (nested signal)
> + * - sig_handler_2 return
> + * - sig_handler return
> + * - fd3 event watchpoint hit -> count3 == 1 (wp and bp in one insn)
> + * - SIGIO is delivered -> overflows == 2
> + * - fd2 event breakpoint hit -> count2 == 2
> + * - SIGUSR1 is delivered -> overflows_2 == 2
> + * - sig_handler_2 return
> + * - sig_handler return
> + * - fd3 event watchpoint hit -> count3 == 2 (standalone wp)
> + * - SIGIO is delivered -> overflows = 3
> + * - fd2 event breakpoint hit -> count2 == 3
> + * - SIGUSR1 is delivered -> overflows_2 == 3
> + * - sig_handler_2 return
> + * - sig_handler return
also each line in here could be prefixed with 'code action'
that led to the result on the line, like:
* exec: result:
*
* __test_function - fd1 event breakpoint hit -> count1 == 1
* - SIGIO is delivered -> overflows == 1
* sig_handler - fd2 event breakpoint hit -> count2 == 1
* - SIGUSR1 is delivered -> overflows_2 == 1 (nested signal)
* - sig_handler_2 return
* - sig_handler return
* incq (%rdi) - fd3 event watchpoint hit -> count3 == 1 (wp and bp in one insn)
* - SIGIO is delivered -> overflows == 2
hum.. but it might take all the fun out of it ;-)
jirka
next prev parent reply other threads:[~2016-01-05 9:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 8:52 [RESEND PATCH] arm64: Store breakpoint single step state into pstate Wang Nan
2015-12-23 8:52 ` Wang Nan
2015-12-23 10:44 ` kbuild test robot
2015-12-23 10:44 ` kbuild test robot
2015-12-24 1:42 ` [PATCH v2] " Wang Nan
2015-12-24 1:42 ` Wang Nan
2016-01-04 16:55 ` Will Deacon
2016-01-04 16:55 ` Will Deacon
2016-01-05 1:41 ` Wangnan (F)
2016-01-05 1:41 ` Wangnan (F)
2016-01-05 4:58 ` [RFC PATCH] arm64: perf test: Improbe bp_signal Wang Nan
2016-01-05 4:58 ` Wang Nan
2016-01-05 5:09 ` Wangnan (F)
2016-01-05 5:09 ` Wangnan (F)
2016-01-05 8:53 ` Jiri Olsa
2016-01-05 8:53 ` Jiri Olsa
2016-01-05 9:00 ` Jiri Olsa
2016-01-05 9:00 ` Jiri Olsa
2016-01-05 9:05 ` Jiri Olsa
2016-01-05 9:05 ` Jiri Olsa
2016-01-05 9:09 ` Jiri Olsa [this message]
2016-01-05 9:09 ` Jiri Olsa
2016-01-05 5:06 ` [PATCH v2] arm64: Store breakpoint single step state into pstate Wangnan (F)
2016-01-05 5:06 ` Wangnan (F)
2016-01-12 17:06 ` Will Deacon
2016-01-12 17:06 ` Will Deacon
2016-01-15 8:20 ` xiakaixu
2016-01-15 8:20 ` xiakaixu
2016-01-21 8:06 ` xiakaixu
2016-01-21 8:06 ` xiakaixu
2016-01-18 11:39 ` Wangnan (F)
2016-01-18 11:39 ` Wangnan (F)
2016-01-05 9:57 ` [RFC PATCH v2] perf test: Improve bp_signal Wang Nan
2016-01-05 9:57 ` Wang Nan
2016-01-05 10:07 ` Jiri Olsa
2016-01-05 10:07 ` 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=20160105090903.GD2192@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.