All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Fomichev <stfomichev@yandex-team.ru>
To: Namhyung Kim <namhyung@kernel.org>
Cc: acme@kernel.org, artagnon@gmail.com, jolsa@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] perf timechart: add more options to IO mode
Date: Mon, 16 Jun 2014 10:15:22 +0400	[thread overview]
Message-ID: <20140616061522.GB9394@stfomichev-desktop.yandex.net> (raw)
In-Reply-To: <87lht39bx0.fsf@sejong.aot.lge.com>

> It's in nano-second unit, right?  If so, it's very unconvenient for user
> to specify.  Maybe we could support to parse unit (s, ms, us, ...) also.
Yes, it's nano-second. I didn't want to limit it to ms, because I
still want to be able to specify ns. I think it's a good idea to support
parsing units. Can I use OPT_CALLBACK or there is a better way to do that
(I couldn't find any similar conversions in perf)?

  reply	other threads:[~2014-06-16  6:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10 15:04 [PATCH v2 0/3] perf timechart io mode Stanislav Fomichev
2014-06-10 15:04 ` [PATCH 1/3] perf timechart: implement IO mode Stanislav Fomichev
2014-06-12  0:59   ` Namhyung Kim
2014-06-16  6:08     ` Stanislav Fomichev
2014-06-18  0:31       ` Namhyung Kim
2014-06-18  9:00         ` Stanislav Fomichev
2014-06-19  0:30           ` Namhyung Kim
2014-06-19  9:58             ` Stanislav Fomichev
2014-06-19 12:18               ` Stanislav Fomichev
2014-06-19 12:38                 ` Namhyung Kim
2014-06-10 15:04 ` [PATCH 2/3] perf timechart: conditionally update start_time on fork Stanislav Fomichev
2014-06-10 15:04 ` [PATCH 3/3] perf timechart: add more options to IO mode Stanislav Fomichev
2014-06-12  1:03   ` Namhyung Kim
2014-06-16  6:15     ` Stanislav Fomichev [this message]
2014-06-18  0:33       ` Namhyung Kim
2014-06-19 12:23 [PATCH v3 0/3] perf timechart io mode Stanislav Fomichev
2014-06-19 12:23 ` [PATCH 3/3] perf timechart: add more options to IO mode Stanislav Fomichev

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=20140616061522.GB9394@stfomichev-desktop.yandex.net \
    --to=stfomichev@yandex-team.ru \
    --cc=acme@kernel.org \
    --cc=artagnon@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@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.