From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] acpi: fix incompatibility with mcount-based function graph tracing
Date: Tue, 21 Mar 2017 21:44:03 +0100 [thread overview]
Message-ID: <c6c72c7a0199bc79fdbe2318713e35d9@molgen.mpg.de> (raw)
In-Reply-To: <6559f36c6c6cdc2552b0bccf31de967367aa790d.1489672478.git.jpoimboe@redhat.com>
Dear Josh,
On 2017-03-16 14:56, Josh Poimboeuf wrote:
> Paul Menzel reported a warning:
>
> WARNING: CPU: 0 PID: 774 at
> /build/linux-ROBWaj/linux-4.9.13/kernel/trace/trace_functions_graph.c:233
> ftrace_return_to_handler+0x1aa/0x1e0
> Bad frame pointer: expected f6919d98, received f6919db0
> from func acpi_pm_device_sleep_wake return to c43b6f9d
>
> The warning means that function graph tracing is broken for the
> acpi_pm_device_sleep_wake() function. That's because the acpi Makefile
> unconditionally sets the '-Os' gcc flag to optimize for size. That's
> an
> issue because mcount-based function graph tracing is incompatible with
> '-Os' on x86, thanks to the following gcc bug:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42109
>
> I have another patch pending which will ensure that mcount-based
> function graph tracing is never used with CONFIG_CC_OPTIMIZE_FOR_SIZE
> on
> x86.
>
> But this patch is needed in addition to that one because the ACPI
> Makefile overrides that config option for no apparent reason. It has
> had this flag since the beginning of git history, and there's no
> related
> comment, so I don't know why it's there. As far as I can tell, there's
> no reason for it to be there. The appropriate behavior is for it to
> honor CONFIG_CC_OPTIMIZE_FOR_{SIZE,PERFORMANCE} like the rest of the
> kernel.
>
> Reported-by: Paul Menzel <pmenzel@molgen.mpg.de>
> Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
> ---
> drivers/acpi/Makefile | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/acpi/Makefile b/drivers/acpi/Makefile
> index a391bbc..d94f92f 100644
> --- a/drivers/acpi/Makefile
> +++ b/drivers/acpi/Makefile
> @@ -2,7 +2,6 @@
> # Makefile for the Linux ACPI interpreter
> #
>
> -ccflags-y := -Os
> ccflags-$(CONFIG_ACPI_DEBUG) += -DACPI_DEBUG_OUTPUT
>
> #
I checked out Linux 4.9.16, applied your patch on top, and copied the
Debian 4.9 Linux kernel configuration, did `make menuconfig`, disabled
building debugging symbols, and executed `ARCH=i386 make -j40 deb-pkg`.
I installed that package on the Lenovo X60, and the result with tracing
enabled has improved. The system suspends without a crash.
Unfortunately, instead of resuming when pressing the power button, it
starts from scratch. Suspend and resume without tracing enabled works
though.
I’ll try to collect logs, but I don’t know, if there will be any, if the
system just resets.
Maybe, this can be reproduced in QEMU?
Kind regards,
Paul
next prev parent reply other threads:[~2017-03-21 20:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 13:56 Josh Poimboeuf
2017-03-16 14:41 ` Steven Rostedt
2017-03-21 20:44 ` Paul Menzel [this message]
2017-03-22 0:04 ` Paul Menzel
2017-03-24 18:12 ` Josh Poimboeuf
2017-03-24 18:41 ` Steven Rostedt
2017-03-25 13:20 ` Rafael J. Wysocki
2017-03-27 14:08 ` Josh Poimboeuf
2017-03-27 14:54 ` [PATCH] ftrace/x86: fix x86-32 triple fault with graph tracing and suspend-to-ram Josh Poimboeuf
2017-03-27 15:01 ` Paul Menzel
2017-03-27 15:20 ` [PATCH v2] " Josh Poimboeuf
2017-03-27 15:24 ` [PATCH] " Steven Rostedt
2017-03-28 9:51 ` Paul Menzel
2017-03-28 15:39 ` Steven Rostedt
2017-03-28 15:55 ` Josh Poimboeuf
2017-03-28 21:12 ` Rafael J. Wysocki
2017-03-28 21:42 ` Josh Poimboeuf
2017-03-28 21:47 ` Rafael J. Wysocki
2017-03-27 16:59 ` [PATCH] acpi: fix incompatibility with mcount-based function graph tracing Rafael J. Wysocki
2017-03-26 20:57 [PATCH] trace: Make trace_hwlat timestamp y2038 safe Deepa Dinamani
2017-03-27 9:25 ` kbuild test robot
2017-03-27 9:55 ` Arnd Bergmann
2017-03-27 14:28 ` Steven Rostedt
2017-03-27 14:53 ` Arnd Bergmann
2017-03-27 15:30 ` Steven Rostedt
2017-03-27 15:35 ` Arnd Bergmann
2017-03-27 16:11 ` Steven Rostedt
2017-03-27 21:02 ` Deepa Dinamani
2017-03-28 7:26 ` Arnd Bergmann
2017-03-27 10:04 ` kbuild test robot
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=c6c72c7a0199bc79fdbe2318713e35d9@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=jpoimboe@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rjw@rjwysocki.net \
--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
Powered by JetHome