From: Kevin Hilman <khilman@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Will Deacon <Will.Deacon@arm.com>,
Simon Horman <horms@verge.net.au>,
Tyler Baker <tyler.baker@linaro.org>, Nishanth Menon <nm@ti.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Arnd Bergmann <arnd@arndb.de>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Magnus Damm <magnus.damm@gmail.com>,
"grygorii.strashko@linaro.org" <grygorii.strashko@linaro.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] mm/migrate: Mark unmap_and_move() "noinline" to avoid ICE in gcc 4.7.3
Date: Wed, 01 Apr 2015 14:54:59 -0700 [thread overview]
Message-ID: <7hwq1v4iq4.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20150401124007.20c440cc43a482f698f461b8@linux-foundation.org> (Andrew Morton's message of "Wed, 1 Apr 2015 12:40:07 -0700")
Andrew Morton <akpm@linux-foundation.org> writes:
> On Wed, 01 Apr 2015 10:47:49 +0100 Marc Zyngier <marc.zyngier@arm.com> wrote:
>
>> > -static int unmap_and_move(new_page_t get_new_page, free_page_t put_new_page,
>> > - unsigned long private, struct page *page, int force,
>> > - enum migrate_mode mode)
>> > +static noinline int unmap_and_move(new_page_t get_new_page,
>> > + free_page_t put_new_page,
>> > + unsigned long private, struct page *page,
>> > + int force, enum migrate_mode mode)
>> > {
>> > int rc = 0;
>> > int *result = NULL;
>> >
>>
>> Ouch. That's really ugly. And on 32bit ARM, we end-up spilling half of
>> the parameters on the stack, which is not going to help performance
>> either (not that this would be useful on 32bit ARM anyway...).
>>
>> Any chance you could make this dependent on some compiler detection
>> mechanism?
>
> With my arm compiler (gcc-4.4.4) the patch makes no difference -
> unmap_and_move() isn't being inlined anyway.
>
> How does this look?
>
> Kevin, could you please retest? I might have fat-fingered something...
Your patch on top of Geert's still compiles fine for me with gcc-4.7.3.
However, I'm not sure how specific we can be on the versions.
/me goes to test a few more compilers... OK...
ICE: 4.7.1, 4.7.3, 4.8.3
OK: 4.6.3, 4.9.2, 4.9.3
The diff below[2] on top of yours compiles fine here and at least covers
the compilers I *know* to trigger the ICE.
Kevin
[1]
diff --git a/mm/migrate.c b/mm/migrate.c
index 25fd7f6291de..6e15ae3248e0 100644
--- a/mm/migrate.c
+++ b/mm/migrate.c
@@ -901,10 +901,10 @@ out:
}
/*
- * gcc-4.7.3 on arm gets an ICE when inlining unmap_and_move(). Work around
+ * gcc 4.7 and 4.8 on arm gets an ICE when inlining unmap_and_move(). Work around
* it.
*/
-#if GCC_VERSION == 40703 && defined(CONFIG_ARM)
+#if (GCC_VERSION >= 40700 && GCC_VERSION < 40900) && defined(CONFIG_ARM)
#define ICE_noinline noinline
#else
#define ICE_noinline
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-04-01 21:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150324004537.GA24816@verge.net.au>
[not found] ` <CAKv+Gu-0jPk=KQ4gY32ELc+BVbe=1QdcrwQ+Pb=RkdwO9K3Vkw@mail.gmail.com>
[not found] ` <20150324161358.GA694@kahuna>
[not found] ` <20150326003939.GA25368@verge.net.au>
[not found] ` <20150326133631.GB2805@arm.com>
[not found] ` <CANMBJr68dsbYvvHUzy6U4m4fEM6nq8dVHBH4kLQ=0c4QNOhLPQ@mail.gmail.com>
[not found] ` <20150327002554.GA5527@verge.net.au>
[not found] ` <20150327100612.GB1562@arm.com>
[not found] ` <7hbnj99epe.fsf@deeprootsystems.com>
[not found] ` <CAKv+Gu_ZHZFm-1eXn+r7fkEHOxqSmj+Q+Mmy7k6LK531vSfAjQ@mail.gmail.com>
[not found] ` <7h8uec95t2.fsf@deeprootsystems.com>
2015-04-01 9:37 ` [PATCH] mm/migrate: Mark unmap_and_move() "noinline" to avoid ICE in gcc 4.7.3 (was: Re: Possible regression in gcc 4.7.3 next-20150323 due to "ARM, arm64: kvm: get rid of the bounce page") Geert Uytterhoeven
2015-04-01 9:47 ` [PATCH] mm/migrate: Mark unmap_and_move() "noinline" to avoid ICE in gcc 4.7.3 Marc Zyngier
2015-04-01 19:40 ` Andrew Morton
2015-04-01 21:54 ` Kevin Hilman [this message]
2015-04-01 21:59 ` Russell King - ARM Linux
2015-04-02 7:17 ` Geert Uytterhoeven
2015-04-02 19:12 ` Lina Iyer
2015-04-02 21:12 ` Kevin Hilman
2015-04-02 21:53 ` Lina Iyer
2015-04-07 17:57 ` Kevin Hilman
2015-04-07 20:17 ` Andrew Morton
2015-04-07 22:41 ` Kevin Hilman
2015-04-07 22:53 ` Andrew Morton
2015-04-07 23:27 ` Kevin Hilman
2015-04-07 23:36 ` Andrew Morton
2015-04-08 0:15 ` Kevin Hilman
2015-04-01 19:27 ` Kevin Hilman
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=7hwq1v4iq4.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=Catalin.Marinas@arm.com \
--cc=Will.Deacon@arm.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=grygorii.strashko@linaro.org \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=marc.zyngier@arm.com \
--cc=nm@ti.com \
--cc=tyler.baker@linaro.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