From: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
To: fweisbec@gmail.com
Cc: linuxppc-dev@lists.ozlabs.org, mpe@ellerman.id,
linux-kernel@vger.kernel.org, fbarrat@linux.vnet.ibm.com,
aneesh.kumar@linux.vnet.ibm.com,
Linuxppc-dev
<linuxppc-dev-bounces+abdhalee=linux.vnet.ibm.com@lists.ozlabs.org>,
abdul <abdhalee@linux.vnet.ibm.com>
Subject: Re: next-20170220 failed to build on PowerPC
Date: Tue, 21 Feb 2017 11:10:38 +0530 [thread overview]
Message-ID: <8c472341719fe124b96de0f7cbfd1961@linux.vnet.ibm.com> (raw)
In-Reply-To: <ff521942-bf47-f9f7-4b43-4585c5d4c667@linux.vnet.ibm.com>
On 2017-02-20 16:25, abdul wrote:
> Hi,
>
> next-20170220 fails to build on Power 8 (PowerVM LPAR) with these
> errors.
>
> with same config, next-20170215 builds fine.
>
> the config file used is attached, by default
> CONFIG_VIRT_CPU_ACCOUNTING_NATIVE was not set.
>
> (X) Simple tick based cputime accounting
> ( ) Deterministic task and CPU time accounting
> ( ) Full dynticks CPU time accounting
>
> arch/powerpc/kernel/time.c: In function ‘running_clock’:
> arch/powerpc/kernel/time.c:712:25: error: implicit declaration of
> function ‘cputime_to_nsecs’
> [-Werror=implicit-function-declaration]
> return local_clock() -
> cputime_to_nsecs(kcpustat_this_cpu->cpustat[CPUTIME_STEAL]);
> ^
> cc1: all warnings being treated as errors
> make[1]: *** [arch/powerpc/kernel/time.o] Error 1
> make[1]: *** Waiting for unfinished jobs....,
>
> Note*: Problem is not seen when CONFIG_VIRT_CPU_ACCOUNTING_NATIVE is
> enabled i.e
>
> ( ) Simple tick based cputime accounting
> (X) Deterministic task and CPU time accounting
> ( ) Full dynticks CPU time accounting
>
Bisecting resulted in below commit causing the build break.
commit f22d6df0b23e66b6d9058e2570402606a6ad069a
Author: Frederic Weisbecker <fweisbec@gmail.com>
Date: Tue Jan 31 04:09:43 2017 +0100
sched/cputime: Remove jiffies based cputime
This cputime_t implementation is now unused, we can remove it.
Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Fenghua Yu <fenghua.yu@intel.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Rik van Riel <riel@redhat.com>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Tony Luck <tony.luck@intel.com>
Cc: Wanpeng Li <wanpeng.li@hotmail.com>
Link:
http://lkml.kernel.org/r/1485832191-26889-28-git-send-email-fweisbec@gmail.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Regard's
Abdul Haleem
IBM Linux Technology Center.
prev parent reply other threads:[~2017-02-21 5:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 10:55 next-20170220 failed to build on PowerPC abdul
2017-02-21 5:40 ` Abdul Haleem [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=8c472341719fe124b96de0f7cbfd1961@linux.vnet.ibm.com \
--to=abdhalee@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev-bounces+abdhalee=linux.vnet.ibm.com@lists.ozlabs.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id \
/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;
as well as URLs for NNTP newsgroup(s).