From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Vineet Gupta <Vineet.Gupta1@synopsys.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
uclinux-h8-devel@lists.sourceforge.jp,
linux-arch@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH v2] mm: cleaning per architecture MM hook header files
Date: Fri, 10 Jul 2015 14:47:18 +0200 [thread overview]
Message-ID: <559FBED6.5080902@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150709160934.888dad2b24ce45957e65b139@linux-foundation.org>
On 10/07/2015 01:09, Andrew Morton wrote:
> On Wed, 1 Jul 2015 12:17:33 +0200 Laurent Dufour <ldufour@linux.vnet.ibm.com> wrote:
>
>> The commit 2ae416b142b6 ("mm: new mm hook framework") introduced an empty
>> header file (mm-arch-hooks.h) for every architecture, even those which
>> doesn't need to define mm hooks.
>>
>> As suggested by Geert Uytterhoeven, this could be cleaned through the use
>> of a generic header file included via each per architecture
>> asm/include/Kbuild file.
>>
>> The PowerPC architecture is not impacted here since this architecture has
>> to defined the arch_remap MM hook.
>
> So the way this works is that if an arch wants to override a hook, it
> will remove the "generic-y += mm-arch-hooks.h" and add
> arch/XXX/include/asm/mm-arch-hooks.h, yes?
>
> And the new arch/XXX/include/asm/mm-arch-hooks.h only needs to define
> the hook(s) which the arch wants to override?
Yes that's the way it should work.
> So nothing will ever be added to include/asm-generic/mm-arch-hooks.h?
This file is the fallback one when no hooks is defined. It is here for
the compiler happiness, and should be kept empty.
> Seems fair enough.
>
> Oleg is angling to remove arch_remap(), so there won't be anything left
> in these files! But there are plenty of ad-hoc things which *should*
> be moved over.
I'll try to move some hooks there as soon as I've so free time.
>
>> Changes in V2:
>> --------------
>> - Vineet Gupta reported that the Kbuild files should be kept sorted.
>
> Yes, we do this to avoid patch collisions. Everyone always adds stuff
> to the end of the list (Makefiles, #includes, etc etc), thus carefully
> maximizing the number of patch collisions :(
This makes sense.
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Vineet Gupta <Vineet.Gupta1@synopsys.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
uclinux-h8-devel@lists.sourceforge.jp,
linux-arch@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH v2] mm: cleaning per architecture MM hook header files
Date: Fri, 10 Jul 2015 14:47:18 +0200 [thread overview]
Message-ID: <559FBED6.5080902@linux.vnet.ibm.com> (raw)
Message-ID: <20150710124718.-rmOyflOzthJb6u4lOTnZ_5v8X6qQb2IFQtuvBhqzVY@z> (raw)
In-Reply-To: <20150709160934.888dad2b24ce45957e65b139@linux-foundation.org>
On 10/07/2015 01:09, Andrew Morton wrote:
> On Wed, 1 Jul 2015 12:17:33 +0200 Laurent Dufour <ldufour@linux.vnet.ibm.com> wrote:
>
>> The commit 2ae416b142b6 ("mm: new mm hook framework") introduced an empty
>> header file (mm-arch-hooks.h) for every architecture, even those which
>> doesn't need to define mm hooks.
>>
>> As suggested by Geert Uytterhoeven, this could be cleaned through the use
>> of a generic header file included via each per architecture
>> asm/include/Kbuild file.
>>
>> The PowerPC architecture is not impacted here since this architecture has
>> to defined the arch_remap MM hook.
>
> So the way this works is that if an arch wants to override a hook, it
> will remove the "generic-y += mm-arch-hooks.h" and add
> arch/XXX/include/asm/mm-arch-hooks.h, yes?
>
> And the new arch/XXX/include/asm/mm-arch-hooks.h only needs to define
> the hook(s) which the arch wants to override?
Yes that's the way it should work.
> So nothing will ever be added to include/asm-generic/mm-arch-hooks.h?
This file is the fallback one when no hooks is defined. It is here for
the compiler happiness, and should be kept empty.
> Seems fair enough.
>
> Oleg is angling to remove arch_remap(), so there won't be anything left
> in these files! But there are plenty of ad-hoc things which *should*
> be moved over.
I'll try to move some hooks there as soon as I've so free time.
>
>> Changes in V2:
>> --------------
>> - Vineet Gupta reported that the Kbuild files should be kept sorted.
>
> Yes, we do this to avoid patch collisions. Everyone always adds stuff
> to the end of the list (Makefiles, #includes, etc etc), thus carefully
> maximizing the number of patch collisions :(
This makes sense.
next prev parent reply other threads:[~2015-07-10 12:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 14:25 [PATCH] mm: cleaning per architecture MM hook header files Laurent Dufour
2015-06-29 14:25 ` Laurent Dufour
2015-06-30 7:28 ` Vineet Gupta
2015-06-30 7:28 ` Vineet Gupta
2015-06-30 7:28 ` Vineet Gupta
2015-06-30 8:43 ` Laurent Dufour
2015-06-30 8:43 ` Laurent Dufour
2015-07-01 10:17 ` [PATCH v2] " Laurent Dufour
2015-07-01 10:17 ` Laurent Dufour
2015-07-01 12:51 ` Vineet Gupta
2015-07-01 12:51 ` Vineet Gupta
2015-07-01 12:51 ` Vineet Gupta
2015-07-01 12:54 ` Geert Uytterhoeven
2015-07-01 12:54 ` Geert Uytterhoeven
2015-07-09 23:09 ` Andrew Morton
2015-07-09 23:09 ` Andrew Morton
2015-07-10 12:47 ` Laurent Dufour [this message]
2015-07-10 12:47 ` Laurent Dufour
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=559FBED6.5080902@linux.vnet.ibm.com \
--to=ldufour@linux.vnet.ibm.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oleg@redhat.com \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.