All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
	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
Subject: Re: [PATCH] perf test: Add watchpoint test
Date: Mon, 10 Sep 2018 10:47:54 -0300	[thread overview]
Message-ID: <20180910134754.GC5147@kernel.org> (raw)
In-Reply-To: <20180910103154.GD15548@krava>

Em Mon, Sep 10, 2018 at 12:31:54PM +0200, Jiri Olsa escreveu:
> On Mon, Sep 10, 2018 at 03:28:11PM +0530, Ravi Bangoria wrote:
> > We don't have perf test available to test watchpoint functionality.
> > Add simple set of tests: 
> >  - Read only watchpoint
> >  - Write only watchpoint
> >  - Read / Write watchpoint
> >  - Runtime watchpoint modification
> > 
> > Ex on powerpc:
> >   $ sudo ./perf test 22
> >   22: Watchpoint                                            :
> >   22.1: Read Only Watchpoint                                : Ok
> >   22.2: Write Only Watchpoint                               : Ok
> >   22.3: Read / Write Watchpoint                             : Ok
> >   22.4: Modify Watchpoint                                   : Ok
> 
> cool, thanks!
> 
> Acked-by: Jiri Olsa <jolsa@kernel.org>

Thanks, applied.

- Arnaldo

  reply	other threads:[~2018-09-10 13:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-10  9:58 [PATCH] perf test: Add watchpoint test Ravi Bangoria
2018-09-10 10:31 ` Jiri Olsa
2018-09-10 13:47   ` Arnaldo Carvalho de Melo [this message]
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

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=20180910134754.GC5147@kernel.org \
    --to=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=ravi.bangoria@linux.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 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.