From: Arnd Bergmann <arnd@arndb.de>
To: Joel Fernandes <joelaf@google.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing: always define trace_{irq,preempt}_{enable_disable}
Date: Thu, 19 Oct 2017 18:04:03 +0200 [thread overview]
Message-ID: <CAK8P3a1UgCLx4BR01tY7oTNjdBCjL6erK7geCZuE2pHSUcgq3g@mail.gmail.com> (raw)
In-Reply-To: <CAJWu+oqZdsA68Cs0CGF4ixULtWcsEkrhoe7oSTbZDf5wb8TDSw@mail.gmail.com>
On Thu, Oct 19, 2017 at 5:42 PM, Joel Fernandes <joelaf@google.com> wrote:
> Hi Arnd,
>
> On Thu, Oct 19, 2017 at 1:32 AM, Arnd Bergmann <arnd@arndb.de> wrote:
>> We get a build error in the irqsoff tracer in some configurations:
>>
>> kernel/trace/trace_irqsoff.c: In function 'trace_preempt_on':
>> kernel/trace/trace_irqsoff.c:855:2: error: implicit declaration of function 'trace_preempt_enable_rcuidle'; did you mean 'trace_irq_enable_rcuidle'? [-Werror=implicit-function-declaration]
>> trace_preempt_enable_rcuidle(a0, a1);
>>
>> The problem is that trace_preempt_enable_rcuidle() has different
>> definition based on multiple Kconfig symbols, but not all combinations
>> have a valid definition.
>>
>> This changes the conditions so that we always get exactly one
>> definition of each of the four tracing macros. I have not tried
>> to verify that these definitions are sensible, but now we
>> can build all randconfig combinations again.
>>
>
> Thanks for catching this. I didn't follow why it breaks for you,
> especially I'm troubled by your proposal of defining the empty macro
> for !defined(CONFIG_DEBUG_PREEMPT) in your patch. Could you provide
> your config sample and architecture you're building for? I'm guessing
> its ARM but let me know. I will try to build it and reproduce it.
I ran into it during an arm64 randconfig build, uploaded the config file to
https://pastebin.com/s5AiqXTM
Arnd
> thanks,
> Joel
next prev parent reply other threads:[~2017-10-19 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 8:32 [PATCH] tracing: always define trace_{irq,preempt}_{enable_disable} Arnd Bergmann
2017-10-19 15:42 ` Joel Fernandes
2017-10-19 16:04 ` Arnd Bergmann [this message]
2017-10-19 18:42 ` Joel Fernandes
2017-10-31 14:13 ` Steven Rostedt
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=CAK8P3a1UgCLx4BR01tY7oTNjdBCjL6erK7geCZuE2pHSUcgq3g@mail.gmail.com \
--to=arnd@arndb.de \
--cc=joelaf@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).