From: Leo Yan <leo.yan@linaro.org>
To: Will Deacon <will@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Brajeswar Ghosh <brajeswar.linux@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Jiri Olsa <jolsa@redhat.com>, Mark Rutland <mark.rutland@arm.com>,
Michael Petlan <mpetlan@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Song Liu <songliubraving@fb.com>,
Souptick Joarder <jrdr.linux@gmail.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>
Subject: Re: [tip: perf/core] perf tests: Disable bp_signal testing for arm64
Date: Tue, 22 Oct 2019 21:43:08 +0800 [thread overview]
Message-ID: <20191022134308.GD32731@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <20191022131423.GA17920@willie-the-truck>
On Tue, Oct 22, 2019 at 02:14:25PM +0100, Will Deacon wrote:
[...]
> > diff --git a/tools/perf/tests/bp_signal.c b/tools/perf/tests/bp_signal.c
> > index c1c2c13..166f411 100644
> > --- a/tools/perf/tests/bp_signal.c
> > +++ b/tools/perf/tests/bp_signal.c
> > @@ -49,14 +49,6 @@ asm (
> > "__test_function:\n"
> > "incq (%rdi)\n"
> > "ret\n");
> > -#elif defined (__aarch64__)
> > -extern void __test_function(volatile long *ptr);
> > -asm (
> > - ".globl __test_function\n"
> > - "__test_function:\n"
> > - "str x30, [x0]\n"
> > - "ret\n");
> > -
> > #else
> > static void __test_function(volatile long *ptr)
> > {
> > @@ -302,10 +294,15 @@ bool test__bp_signal_is_supported(void)
> > * stepping into the SIGIO handler and getting stuck on the
> > * breakpointed instruction.
> > *
> > + * Since arm64 has the same issue with arm for the single-step
> > + * handling, this case also gets suck on the breakpointed
> > + * instruction.
>
> Freudian slip?
:D sorry for typo: s/suck/stuck.
Thanks for review and will send a patch to fix it.
Thanks,
Leo Yan
next prev parent reply other threads:[~2019-10-22 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 8:55 [PATCH v1 1/3] perf tests: Remove needless headers for bp_account Leo Yan
2019-10-18 8:55 ` [PATCH v1 2/3] perf tests bp_account: Add dedicated checking helper is_supported() Leo Yan
2019-10-18 17:57 ` Arnaldo Carvalho de Melo
2019-10-21 23:18 ` [tip: perf/core] " tip-bot2 for Leo Yan
2019-10-18 8:55 ` [PATCH v1 3/3] perf tests: Disable bp_signal testing for arm64 Leo Yan
2019-10-18 17:59 ` Arnaldo Carvalho de Melo
2019-10-21 7:53 ` Leo Yan
2019-10-21 23:18 ` [tip: perf/core] " tip-bot2 for Leo Yan
2019-10-22 13:14 ` Will Deacon
2019-10-22 13:43 ` Leo Yan [this message]
2019-10-18 17:55 ` [PATCH v1 1/3] perf tests: Remove needless headers for bp_account Arnaldo Carvalho de Melo
2019-10-21 23:18 ` [tip: perf/core] " tip-bot2 for Leo Yan
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=20191022134308.GD32731@leoy-ThinkPad-X240s \
--to=leo.yan@linaro.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=brajeswar.linux@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=jolsa@redhat.com \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=will@kernel.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).