From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>
Cc: Rik van Riel <riel@redhat.com>,
Pavel Emelyanov <xemul@parallels.com>,
Hugh Dickins <hughd@google.com>,
linux-kernel@vger.kernel.org, criu@openvz.org,
linux-mm@kvack.org, Paul Mackerras <paulus@samba.org>,
Mel Gorman <mgorman@suse.de>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
linuxppc-dev@lists.ozlabs.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
cov@codeaurora.org
Subject: Re: [RESEND PATCH v3 1/2] mm: Introducing arch_remap hook
Date: Tue, 14 Apr 2015 11:26:13 +0200 [thread overview]
Message-ID: <552CDD35.2030901@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150413135951.b3d9f431892dbfa7156cc1b0@linux-foundation.org>
On 13/04/2015 22:59, Andrew Morton wrote:
> On Mon, 13 Apr 2015 17:02:19 +0300 "Kirill A. Shutemov" <kirill@shutemov.name> wrote:
>
>>> Kirill, if I'm right with it, can you suggest the header where to put
>>> the "generic" mremap hook's (empty) body?
>>
>> I initially thought it would be enough to put it into
>> <asm-generic/mmu_context.h>, expecting it works as
>> <asm-generic/pgtable.h>. But that's not the case.
>>
>> It probably worth at some point rework all <asm/mmu_context.h> to include
>> <asm-generic/mmu_context.h> at the end as we do for <asm/pgtable.h>.
>> But that's outside the scope of the patchset, I guess.
>>
>> I don't see any better candidate for such dummy header. :-/
>
> Do away with __HAVE_ARCH_REMAP and do it like this:
>
> arch/x/include/asm/y.h:
>
> extern void arch_remap(...);
> #define arch_remap arch_remap
>
> include/linux/z.h:
>
> #include <asm/y.h>
>
> #ifndef arch_remap
> static inline void arch_remap(...) { }
> #define arch_remap arch_remap
> #endif
Hi Andrew,
I like your idea, but I can't find any good candidate for <asm/y.h> and
<linux/z.h>.
I tried with <linux/mm.h> and <asm/mmu_context.h> but
<asm/mmu_context.h> is already including <linux/mm.h>.
Do you have any suggestion ?
Another option could be to do it like the actual arch_unmap() in
<asm-generic/mm_hooks.h> but this is the opposite of your idea, and Ingo
was not comfortable with this idea due to the impact of the other
architectures.
Cheers,
Laurent.
next prev parent reply other threads:[~2015-04-14 9:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 9:56 [RESEND PATCH v3 0/2] Tracking user space vDSO remaping Laurent Dufour
2015-04-13 9:56 ` [RESEND PATCH v3 1/2] mm: Introducing arch_remap hook Laurent Dufour
2015-04-13 11:58 ` Kirill A. Shutemov
2015-04-13 12:41 ` Laurent Dufour
2015-04-13 13:13 ` Kirill A. Shutemov
2015-04-13 13:21 ` Laurent Dufour
2015-04-13 13:35 ` Pavel Emelyanov
2015-04-13 14:02 ` Kirill A. Shutemov
2015-04-13 14:11 ` Laurent Dufour
2015-04-13 14:26 ` Kirill A. Shutemov
2015-04-13 14:32 ` Pavel Emelyanov
2015-04-13 15:27 ` Laurent Dufour
2015-04-13 20:59 ` Andrew Morton
2015-04-14 9:26 ` Laurent Dufour [this message]
2015-04-14 19:38 ` Andrew Morton
2015-04-15 11:57 ` Laurent Dufour
2015-04-15 14:16 ` [PATCH v5 0/3] Tracking user space vDSO remaping Laurent Dufour
2015-04-15 14:16 ` [PATCH v5 1/3] mm: New mm hook framework Laurent Dufour
2015-04-15 14:16 ` [PATCH v5 2/3] mm: New arch_remap hook Laurent Dufour
2015-04-15 14:16 ` [PATCH v5 3/3] powerpc/mm: Tracking vDSO remap Laurent Dufour
2015-04-13 9:56 ` [RESEND PATCH v3 2/2] " 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=552CDD35.2030901@linux.vnet.ibm.com \
--to=ldufour@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=cov@codeaurora.org \
--cc=criu@openvz.org \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=paulus@samba.org \
--cc=riel@redhat.com \
--cc=xemul@parallels.com \
/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).