LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Joel Fernandes <joelaf@google.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, LKML <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zilstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
"Cc: Android Kernel" <kernel-team@android.com>
Subject: Re: [PATCH v2 1/2] tracing: Improve design of preemptirq tracepoints and its users
Date: Sun, 18 Mar 2018 18:39:54 -0700 [thread overview]
Message-ID: <CAJWu+orG8WGqfsMd0=Z-4vCskW=LzRfWkQyNjZxSoDbE2YtKSQ@mail.gmail.com> (raw)
In-Reply-To: <201803180239.bVSVPTE1%fengguang.wu@intel.com>
On Sat, Mar 17, 2018 at 12:03 PM, kbuild test robot <lkp@intel.com> wrote:
> Hi Joel,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on linus/master]
> [also build test ERROR on v4.16-rc5 next-20180316]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
> url: https://github.com/0day-ci/linux/commits/Joel-Fernandes/Improve-preemptirq-tracepoint-usage/20180317-155535
> config: arm-moxart_defconfig (attached as .config)
> compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> make.cross ARCH=arm
>
> All errors (new ones prefixed by >>):
>
> arch/arm/kernel/entry-common.o: In function `no_work_pending':
>>> (.entry.text+0x64): undefined reference to `trace_hardirqs_on'
> arch/arm/kernel/entry-common.o: In function `vector_swi':
> (.entry.text+0xf8): undefined reference to `trace_hardirqs_on'
> arch/arm/kernel/entry-armv.o: In function `__dabt_svc':
>>> (.entry.text+0xa4): undefined reference to `trace_hardirqs_off'
> (.entry.text+0xb8): undefined reference to `trace_hardirqs_on'
> (.entry.text+0xc0): undefined reference to `trace_hardirqs_off'
> arch/arm/kernel/entry-armv.o: In function `__irq_svc':
Fixed in the next rev. Sigh :-( Turns out kernel/trace/ wasn't being
built at all because of a combination of
CONFIG_PREEMPTIRQ_TRACEPOINTS=y but CONFIG_TRACING=n
I think the next rev looks much better now and its getting there, but
I have to thoroughly test it before posting it again..
thanks,
- Joel
next prev parent reply other threads:[~2018-03-19 1:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 20:43 [PATCH v2 0/2] Improve preemptirq tracepoint usage Joel Fernandes
2018-03-15 20:44 ` [PATCH v2 1/2] tracing: Improve design of preemptirq tracepoints and its users Joel Fernandes
2018-03-17 14:49 ` [tracing] 45382b2a36: WARNING:at_kernel/locking/lockdep.c:#check_flags kernel test robot
2018-03-17 19:03 ` [PATCH v2 1/2] tracing: Improve design of preemptirq tracepoints and its users kbuild test robot
2018-03-19 1:39 ` Joel Fernandes [this message]
2018-03-15 20:44 ` [PATCH v2 2/2] tracepoint: Prevent false-positive lockdep warnings Joel Fernandes
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='CAJWu+orG8WGqfsMd0=Z-4vCskW=LzRfWkQyNjZxSoDbE2YtKSQ@mail.gmail.com' \
--to=joelaf@google.com \
--cc=kbuild-all@01.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tom.zanussi@linux.intel.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;
as well as URLs for NNTP newsgroup(s).