From: kbuild test robot <lkp@intel.com>
To: Alexander Potapenko <glider@google.com>
Cc: kbuild-all@01.org, dvyukov@google.com, kcc@google.com,
aryabinin@virtuozzo.com, x86@kernel.org, rostedt@goodmis.org,
mingo@redhat.com, kasan-dev@googlegroups.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] x86, kasan, ftrace: Put APIC interrupt handlers into .irqentry.text
Date: Fri, 15 Jul 2016 17:19:46 +0800 [thread overview]
Message-ID: <201607151724.ql1tGSy2%fengguang.wu@intel.com> (raw)
In-Reply-To: <1468515848-34152-1-git-send-email-glider@google.com>
[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]
Hi,
[auto build test WARNING on tip/x86/core]
[also build test WARNING on v4.7-rc7 next-20160714]
[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/Alexander-Potapenko/x86-kasan-ftrace-Put-APIC-interrupt-handlers-into-irqentry-text/20160715-152601
config: x86_64-acpi-redef (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
>> arch/x86/entry/entry_64.S:674:15: warning: extra tokens at end of #ifdef directive
#ifdef defined(CONFIG_FUNCTION_GRAPH_TRACER) || defined(CONFIG_KASAN)
^
vim +674 arch/x86/entry/entry_64.S
658 END(\sym)
659 .endm
660
661 #ifdef CONFIG_TRACING
662 #define trace(sym) trace_##sym
663 #define smp_trace(sym) smp_trace_##sym
664
665 .macro trace_apicinterrupt num sym
666 apicinterrupt3 \num trace(\sym) smp_trace(\sym)
667 .endm
668 #else
669 .macro trace_apicinterrupt num sym do_sym
670 .endm
671 #endif
672
673 /* Make sure APIC interrupt handlers end up in the irqentry section. */
> 674 #ifdef defined(CONFIG_FUNCTION_GRAPH_TRACER) || defined(CONFIG_KASAN)
675 #define PUSH_SECTION_IRQENTRY .pushsection .irqentry.text, "ax"
676 #define POP_SECTION_IRQENTRY .popsection
677 #else
678 #define PUSH_SECTION_IRQENTRY
679 #define POP_SECTION_IRQENTRY
680 #endif
681
682 .macro apicinterrupt num sym do_sym
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 27963 bytes --]
next prev parent reply other threads:[~2016-07-15 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 17:04 Alexander Potapenko
2016-07-15 9:19 ` kbuild test robot [this message]
2016-07-27 12:45 ` Steven Rostedt
2016-07-27 12:52 ` Andrey Ryabinin
2016-07-27 13:01 ` 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=201607151724.ql1tGSy2%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kbuild-all@01.org \
--cc=kcc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®