From: Peter Zijlstra <peterz@infradead.org>
To: John Stultz <john.stultz@linaro.org>
Cc: Pawel Moll <pawel.moll@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>, Oleg Nesterov <oleg@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>,
Andy Lutomirski <luto@amacapital.net>,
Stephen Boyd <sboyd@codeaurora.org>,
Baruch Siach <baruch@tkos.co.il>,
Thomas Gleixner <tglx@linutronix.de>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] sched_clock: Track monotonic raw clock
Date: Fri, 18 Jul 2014 21:34:17 +0200 [thread overview]
Message-ID: <20140718193417.GG3935@laptop> (raw)
In-Reply-To: <CALAqxLX4ia_dBO-oNY1XMnSrJdDZc87EneHj9WcxtOZaupZaCg@mail.gmail.com>
On Fri, Jul 18, 2014 at 12:25:48PM -0700, John Stultz wrote:
> Also, assuming we someday will merge the x86 sched_clock logic into
> the generic sched_clock code, we'll have to handle cases where they
> aren't the same.
I prefer that to not happen. I spend quite a bit of time and effort to
make the x86 code go fast, and that generic code doesn't look like fast
at all.
next prev parent reply other threads:[~2014-07-18 19:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 17:43 [RFC] sched_clock: Track monotonic raw clock Pawel Moll
2014-07-18 17:51 ` John Stultz
2014-07-18 19:06 ` Peter Zijlstra
2014-07-22 16:17 ` Pawel Moll
2014-07-18 19:13 ` Peter Zijlstra
2014-07-18 19:25 ` John Stultz
2014-07-18 19:34 ` Peter Zijlstra [this message]
2014-07-18 19:46 ` John Stultz
2014-07-18 20:22 ` Peter Zijlstra
2014-07-18 22:41 ` Peter Zijlstra
2014-07-22 16:17 ` Pawel Moll
2014-07-22 16:29 ` Peter Zijlstra
2014-07-22 16:17 ` Pawel Moll
2014-07-19 5:02 ` Richard Cochran
2014-07-22 16:17 ` Pawel Moll
2014-07-22 16:34 ` Peter Zijlstra
2014-07-22 16:48 ` Pawel Moll
2014-07-22 19:39 ` Richard Cochran
2014-09-12 11:45 ` Pawel Moll
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=20140718193417.GG3935@laptop \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=baruch@tkos.co.il \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=pawel.moll@arm.com \
--cc=rostedt@goodmis.org \
--cc=sboyd@codeaurora.org \
--cc=tglx@linutronix.de \
/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.