From: Baoquan He <bhe@redhat.com>
To: kexec@lists.infradead.org
Subject: [PATCH v2] purgatory: do not enable vectorization automatically for purgatory compiling
Date: Wed, 30 Mar 2022 17:52:43 +0800 [thread overview]
Message-ID: <20220330095243.GA2331@MiWiFi-R3L-srv> (raw)
In-Reply-To: <YkQfh7KIume8VLjU@vergenet.net>
On 03/30/22 at 11:14am, Simon Horman wrote:
> On Tue, Mar 29, 2022 at 06:12:28PM +0800, Baoquan He wrote:
> > Redhat CKI reported kdump kernel will hang a while very early after crash
> > triggered, then reset to firmware to reboot.
> >
> > This failure can only be observed with kdump or kexec reboot via
> > kexec_load system call. With kexec_file_load interface, both kdump and
> > kexec reboot work very well. And further investigation shows that gcc
> > version 11 doesn't have this issue, while gcc version 12 does.
> >
> > After checking the release notes of the latest gcc, Dave found out it's
> > because gcc 12 enables auto-vectorization for -O2 optimization level.
> > Please see below link for more information:
> >
> > https://www.phoronix.com/scan.php?page=news_item&px=GCC-12-Auto-Vec-O2
> >
> > Adding -fno-tree-vectorize to Makefile of purgatory can fix the issue.
> >
> > Signed-off-by: Baoquan He <bhe@redhat.com>
>
> Thanks, applied.
Thanks, Simon.
prev parent reply other threads:[~2022-03-30 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 10:01 [PATCH] purgatory: do not enable vectorization automatically for purgatory compiling Baoquan He
2022-03-29 10:12 ` [PATCH v2] " Baoquan He
2022-03-30 9:14 ` Simon Horman
2022-03-30 9:52 ` Baoquan He [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=20220330095243.GA2331@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=kexec@lists.infradead.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).