From: Ingo Molnar <mingo@kernel.org>
To: John Stultz <john.stultz@linaro.org>
Cc: "David Ahern" <dsahern@gmail.com>,
"Stephane Eranian" <eranian@google.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@elte.hu>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"Jiri Olsa" <jolsa@redhat.com>,
"Namhyung Kim" <namhyung@kernel.org>,
"Rose Belcher" <cel@us.ibm.com>,
"Sukadev Bhattiprolu" <sukadev@linux.vnet.ibm.com>,
"Sonny Rao" <sonnyrao@chromium.org>,
"John Mccutchan" <johnmccutchan@google.com>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Paweł Moll" <mail@pawelmoll.com>
Subject: Re: [PATCH v2 4/4] clock: add perf_clock posix clock
Date: Wed, 18 Feb 2015 19:22:42 +0100 [thread overview]
Message-ID: <20150218182242.GC32251@gmail.com> (raw)
In-Reply-To: <CALAqxLV+tCSPN+DRhZGAd7ac1aK-pURG52hJuKJQ02NM-pemwQ@mail.gmail.com>
* John Stultz <john.stultz@linaro.org> wrote:
> > AFAIK Stephane is not proposing this patch for
> > inclusion but rather it is an unfortunate necessary
> > evil. The module exposes perf_clock (ie., local_clock)
> > to userspace and allows in this case the generation of
> > samples with a perf timestamp which is required for
> > proper sorting.
> >
> > I understand this solution is not liked, but it works,
> > requires no kernel modifications to achieve the end
> > goal and can be used for kernels going back to at least
> > 2.6.38 (perhaps earlier, have not checked).
>
> Yep. And I'm sympathetic to the fact that an alternative
> solution hasn't made it upstream yet. I'm hopeful Pawel's
> recent approach will make it in (it seems like it hasn't
> raised any flags w/ scheduler folks - but I've not always
> been able to follow the discussion closely).
So if it's part of this series and reviews fine then I'll
be happy to apply it! Nothing better than having a kernel
patch and an actual usecase go hand in hand.
Thanks,
Ingo
next prev parent reply other threads:[~2015-02-18 18:22 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
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 [this message]
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=20150218182242.GC32251@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=john.stultz@linaro.org \
--cc=johnmccutchan@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@pawelmoll.com \
--cc=mingo@elte.hu \
--cc=namhyung@kernel.org \
--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 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.