All of lore.kernel.org
 help / color / mirror / Atom feed
From: wangnan0@huawei.com (Wangnan (F))
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] arm64: perf test: Improbe bp_signal
Date: Tue, 5 Jan 2016 13:09:03 +0800	[thread overview]
Message-ID: <568B4FEF.5030508@huawei.com> (raw)
In-Reply-To: <1451969880-14877-1-git-send-email-wangnan0@huawei.com>



On 2016/1/5 12:58, Wang Nan wrote:
> Will Deacon [1] has some question on patch [2]. This patch improves
> test__bp_signal so we can test:
>
>   1. A watchpoint and a breakpoint that fire on the same instruction
>   2. Nested signals
>
> For detail of this patch see the comment in patch body.
>
> Test result:
>
>   On both x86_64:

On x86_64 and arm64.

Sorry.

WARNING: multiple messages have this Message-ID (diff)
From: "Wangnan (F)" <wangnan0@huawei.com>
To: <will.deacon@arm.com>
Cc: <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 13:09:03 +0800	[thread overview]
Message-ID: <568B4FEF.5030508@huawei.com> (raw)
In-Reply-To: <1451969880-14877-1-git-send-email-wangnan0@huawei.com>



On 2016/1/5 12:58, Wang Nan wrote:
> Will Deacon [1] has some question on patch [2]. This patch improves
> test__bp_signal so we can test:
>
>   1. A watchpoint and a breakpoint that fire on the same instruction
>   2. Nested signals
>
> For detail of this patch see the comment in patch body.
>
> Test result:
>
>   On both x86_64:

On x86_64 and arm64.

Sorry.


  reply	other threads:[~2016-01-05  5: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) [this message]
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
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=568B4FEF.5030508@huawei.com \
    --to=wangnan0@huawei.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.