public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: peterz@infradead.org, Ingo Molnar <mingo@redhat.com>,
	"open list:SCHEDULER" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched/clock: Make local_clock/cpu_clock inline
Date: Wed, 13 Apr 2016 12:05:39 +0200	[thread overview]
Message-ID: <570E19F3.10601@linaro.org> (raw)
In-Reply-To: <20160413095107.GD6430@gmail.com>

On 04/13/2016 11:51 AM, Ingo Molnar wrote:
>
> * Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>
>> On 04/13/2016 11:41 AM, Ingo Molnar wrote:
>>>
>>> * Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>>>
>>>> The local_clock/cpu_clock functions were changed to prevent a double
>>>> identical test with sched_clock_cpu() when HAVE_UNSTABLE_SCHED_CLOCK
>>>> is set. That resulted in one line functions.
>>>>
>>>> As these functions are in all the cases one line functions and in the
>>>> hot path, it is useful to specify them as static inline in order to
>>>> give a strong hint to the compiler.
>>>>
>>>> After verification, it appears the compiler does not inline them
>>>> without this hint. Change those functions to static inline.
>>>>
>>>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>>>> ---
>>>>   include/linux/sched.h | 32 ++++++++++++++++++++++++++++++--
>>>>   kernel/sched/clock.c  | 41 -----------------------------------------
>>>>   2 files changed, 30 insertions(+), 43 deletions(-)
>>>
>>> Hm, this does not seem to apply to v4.6-rc3 cleanly.
>>
>> Actually I based the patches on top of tip/sched/core.
>
> This patch does not seem to apply to tip/sched/core either (2b8c41daba32).

Ah, yes. I received a compilation error because of a missing 
EXPORT_SYMBOL_GPL for an inlined function call from kbuild test:

ERROR: "sched_clock_cpu" [kernel/torture.ko] undefined!
ERROR: "sched_clock_cpu" [drivers/gpu/drm/i915/i915.ko] undefined!

So I resent a fixed V2.

https://lkml.org/lkml/2016/4/11/603
https://lkml.org/lkml/2016/4/11/602

Sorry, I did not notice you were mentioning the first version which is 
outdated. The V2 is based on top of 2b8c41daba32.

   -- Daniel

-- 
  <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

      reply	other threads:[~2016-04-13 10:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01 20:04 [PATCH] sched/clock: Make local_clock/cpu_clock inline Daniel Lezcano
2016-04-13  9:41 ` Ingo Molnar
2016-04-13  9:46   ` Daniel Lezcano
2016-04-13  9:51     ` Ingo Molnar
2016-04-13 10:05       ` Daniel Lezcano [this message]

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=570E19F3.10601@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox