From: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>, Jiri Olsa <jolsa@redhat.com>
Cc: alexander.shishkin@linux.intel.com, namhyung@kernel.org,
tmricht@linux.ibm.com, sandipan@linux.ibm.com,
brueckner@linux.ibm.com, kim.phillips@arm.com,
kstewart@linuxfoundation.org, tglx@linutronix.de,
naveen.n.rao@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
Ravi Bangoria <ravi.bangoria@linux.ibm.com>
Subject: Re: [PATCH] perf test: Add watchpoint test
Date: Wed, 12 Sep 2018 08:45:47 +0530 [thread overview]
Message-ID: <ae18ee33-b748-1c74-3993-8f5181c65dec@linux.ibm.com> (raw)
In-Reply-To: <20180910141830.GI5147@kernel.org>
> While testing, I got curious, as a 'perf test' user, why one of the
> tests had the "Skip" result:
>
> [root@seventh ~]# perf test watchpoint
> 22: Watchpoint :
> 22.1: Read Only Watchpoint : Skip
> 22.2: Write Only Watchpoint : Ok
> 22.3: Read / Write Watchpoint : Ok
> 22.4: Modify Watchpoint : Ok
> [root@seventh ~]#
>
> I tried with 'perf test -v watchpoint' but that didn't help, perhaps you
> could add some message after the "Skip" telling why it skipped that
> test? I.e. hardware doesn't have that capability, kernel driver not yet
> supporting that, something else?
Sure will add a message:
pr_debug("Hardware does not support read only watchpoints.");
Ravi
prev parent reply other threads:[~2018-09-12 3:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 9:58 Ravi Bangoria
2018-09-10 10:31 ` Jiri Olsa
2018-09-10 13:47 ` Arnaldo Carvalho de Melo
2018-09-10 14:18 ` Arnaldo Carvalho de Melo
2018-09-10 17:31 ` Arnaldo Carvalho de Melo
2018-09-12 3:08 ` Ravi Bangoria
2018-09-12 3:15 ` Ravi Bangoria [this message]
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=ae18ee33-b748-1c74-3993-8f5181c65dec@linux.ibm.com \
--to=ravi.bangoria@linux.ibm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=brueckner@linux.ibm.com \
--cc=jolsa@redhat.com \
--cc=kim.phillips@arm.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=sandipan@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=tmricht@linux.ibm.com \
/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
Powered by JetHome