public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, acme@redhat.com,
	peterz@infradead.org, mingo@elte.hu, ak@linux.intel.com,
	jolsa@redhat.com, namhyung@kernel.org, cel@us.ibm.com,
	sukadev@linux.vnet.ibm.com, sonnyrao@chromium.org,
	johnmccutchan@google.com, dsahern@gmail.com,
	adrian.hunter@intel.com, pawell.moll@arm.com
Subject: Re: [PATCH v2 4/4] clock: add perf_clock posix clock
Date: Wed, 18 Feb 2015 18:53:54 +0100	[thread overview]
Message-ID: <20150218175354.GA31963@gmail.com> (raw)
In-Reply-To: <1424280109-9801-5-git-send-email-eranian@google.com>


* Stephane Eranian <eranian@google.com> wrote:

> This patch is a re-packaging of David's Ahern
> posix perf clock available here:
> 
> 	https://github.com/dsahern/linux/blob/perf-full-monty/README.ahern
> 
> The patch itself is based on Pawel Moll's original post:
> 
> 	https://lkml.org/lkml/2013/3/14/523
> 
> The new clock is call PERF_CLOCK. To use it
> 
> 	#include <time.h>
> 	#include <linux/time.h>
> 
> 	struct timespec ts;
> 
> 	clock_gettime(PERF_CLOCK, &ts);

So what's the justification for this new clock, as opposed 
to say CLOCK_MONOTONIC?

Thanks,

	Ingo

  reply	other threads:[~2015-02-18 17:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18 17:21 [PATCH v2 0/4] perf: add support for profiling jitted code Stephane Eranian
2015-02-18 17:21 ` [PATCH v2 1/4] perf tools: add Java demangling support Stephane Eranian
2015-02-18 17:21 ` [PATCH v2 2/4] perf inject: add jitdump mmap injection support Stephane Eranian
2015-02-18 17:21 ` [PATCH v2 3/4] perf tools: add JVMTI agent library Stephane Eranian
2015-02-18 17:21 ` [PATCH v2 4/4] clock: add perf_clock posix clock Stephane Eranian
2015-02-18 17:53   ` Ingo Molnar [this message]
2015-02-18 18:00   ` John Stultz
2015-02-18 18:10     ` Stephane Eranian
2015-02-18 18:15       ` John Stultz
2015-02-18 18:11     ` David Ahern
2015-02-18 18:18       ` John Stultz
2015-02-18 18:21         ` Stephane Eranian
2015-02-18 18:22         ` Ingo Molnar
2015-02-18 19:00   ` Paul Bolle
2015-02-18 19:12   ` Paul Bolle
2015-02-18 17:31 ` [PATCH v2 0/4] perf: add support for profiling jitted code Ingo Molnar

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=20150218175354.GA31963@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@redhat.com \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=cel@us.ibm.com \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=johnmccutchan@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=namhyung@kernel.org \
    --cc=pawell.moll@arm.com \
    --cc=peterz@infradead.org \
    --cc=sonnyrao@chromium.org \
    --cc=sukadev@linux.vnet.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