[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <ae18ee33-b748-1c74-3993-8f5181c65dec@linux.ibm.com>
Date: Wed, 12 Sep 2018 08:45:47 +0530
From: Ravi Bangoria <ravi.bangoria@...ux.ibm.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>,
Jiri Olsa <jolsa@...hat.com>
Cc: alexander.shishkin@...ux.intel.com, namhyung@...nel.org,
tmricht@...ux.ibm.com, sandipan@...ux.ibm.com,
brueckner@...ux.ibm.com, kim.phillips@....com,
kstewart@...uxfoundation.org, tglx@...utronix.de,
naveen.n.rao@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
Ravi Bangoria <ravi.bangoria@...ux.ibm.com>
Subject: Re: [PATCH] perf test: Add watchpoint test
> While testing, I got curious, as a 'perf test' user, why one of the
> tests had the "Skip" result:
>
> [root@...enth ~]# 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@...enth ~]#
>
> 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
Powered by blists - more mailing lists