All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Harald Servat <harald.servat@bsc.es>
Cc: Andi Kleen <andi@firstfloor.org>, linux-perf-users@vger.kernel.org
Subject: Re: Changing frequency rate to perf mem
Date: Mon, 28 Oct 2013 15:50:43 +0900	[thread overview]
Message-ID: <87sivl99do.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <5268D0B9.50704@bsc.es> (Harald Servat's message of "Thu, 24 Oct 2013 09:48:09 +0200")

Hi Harald,

On Thu, 24 Oct 2013 09:48:09 +0200, Harald Servat wrote:
> On 24/10/13 07:12, Andi Kleen wrote:
>> Harald Servat <harald.servat@bsc.es> writes:
>>> Unfortunately, this seems to break something and
>>> perf segfaults often. Which is the most appropriate way to tune the
>>> user frequency of perf mem?
>>
>> Best would be probably to fix it to pass through unknown
>> options, then -F/-c could be just used. I'm not sure
>> if this is possible easily with the git option parser.
>
> Sorry, I'm not sure what is the "git option parser" here.

Just implementation details.  The source code of the option parser came
from the git project.


> I think that this could be implemented extending the mem_options[] in
> file builtin-mem.c lines 205-221.

Or else, use 'perf record' directly as Andi suggested.

>
>> Alternatively you can just specify the command line perf mem record
>> would specify directly to perf record, plus -c/-F

  $ perf record -Wd -e cpu/mem-loads/pp -F 200 -- ls

  $ perf mem report


Thanks,
Namhyung

  reply	other threads:[~2013-10-28  6:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-23 15:43 Changing frequency rate to perf mem Harald Servat
2013-10-24  5:12 ` Andi Kleen
2013-10-24  7:48   ` Harald Servat
2013-10-28  6:50     ` Namhyung Kim [this message]
2013-10-28  8:15       ` Harald Servat

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=87sivl99do.fsf@sejong.aot.lge.com \
    --to=namhyung@kernel.org \
    --cc=andi@firstfloor.org \
    --cc=harald.servat@bsc.es \
    --cc=linux-perf-users@vger.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 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.