Re: [RESEND PATCH v3 1/2] mm: Introducing arch_remap hook

2015-04-15 Thread Laurent Dufour
On 14/04/2015 21:38, Andrew Morton wrote: > On Tue, 14 Apr 2015 11:26:13 +0200 Laurent Dufour > wrote: > >>> 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.

Re: [RESEND PATCH v3 1/2] mm: Introducing arch_remap hook

2015-04-14 Thread Andrew Morton
On Tue, 14 Apr 2015 11:26:13 +0200 Laurent Dufour wrote: > > 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 > > > > #ifnde

Re: [RESEND PATCH v3 1/2] mm: Introducing arch_remap hook

2015-04-14 Thread Laurent Dufour
On 13/04/2015 22:59, Andrew Morton wrote: > On Mon, 13 Apr 2015 17:02:19 +0300 "Kirill A. Shutemov" > 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 >> ,

Re: [RESEND PATCH v3 1/2] mm: Introducing arch_remap hook

2015-04-13 Thread Andrew Morton
On Mon, 13 Apr 2015 17:02:19 +0300 "Kirill A. Shutemov" 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 > , expecting it works as > . But that's not the case.

Re: [RESEND PATCH v3 1/2] mm: Introducing arch_remap hook

2015-04-13 Thread Laurent Dufour
On 13/04/2015 16:32, Pavel Emelyanov wrote: I initially thought it would be enough to put it into , expecting it works as . But that's not the case. It probably worth at some point rework all to include at the end as we do for . But that's outside the scope of t

Re: [RESEND PATCH v3 1/2] mm: Introducing arch_remap hook

2015-04-13 Thread Pavel Emelyanov
>>> I initially thought it would be enough to put it into >>> , expecting it works as >>> . But that's not the case. >>> >>> It probably worth at some point rework all to include >>> at the end as we do for . >>> But that's outside the scope of the patchset, I guess. >>> >>> I don't see any bette

Re: [RESEND PATCH v3 1/2] mm: Introducing arch_remap hook

2015-04-13 Thread Kirill A. Shutemov
On Mon, Apr 13, 2015 at 04:11:19PM +0200, Laurent Dufour wrote: > On 13/04/2015 16:02, Kirill A. Shutemov wrote: > > On Mon, Apr 13, 2015 at 04:35:21PM +0300, Pavel Emelyanov wrote: > >> On 04/13/2015 04:21 PM, Laurent Dufour wrote: > >>> On 13/04/2015 15:13, Kirill A. Shutemov wrote: > On Mon

Re: [RESEND PATCH v3 1/2] mm: Introducing arch_remap hook

2015-04-13 Thread Laurent Dufour
On 13/04/2015 16:02, Kirill A. Shutemov wrote: > On Mon, Apr 13, 2015 at 04:35:21PM +0300, Pavel Emelyanov wrote: >> On 04/13/2015 04:21 PM, Laurent Dufour wrote: >>> On 13/04/2015 15:13, Kirill A. Shutemov wrote: On Mon, Apr 13, 2015 at 02:41:22PM +0200, Laurent Dufour wrote: > On 13/04/2

Re: [RESEND PATCH v3 1/2] mm: Introducing arch_remap hook

2015-04-13 Thread Kirill A. Shutemov
On Mon, Apr 13, 2015 at 04:35:21PM +0300, Pavel Emelyanov wrote: > On 04/13/2015 04:21 PM, Laurent Dufour wrote: > > On 13/04/2015 15:13, Kirill A. Shutemov wrote: > >> On Mon, Apr 13, 2015 at 02:41:22PM +0200, Laurent Dufour wrote: > >>> On 13/04/2015 13:58, Kirill A. Shutemov wrote: > On Mon

Re: [RESEND PATCH v3 1/2] mm: Introducing arch_remap hook

2015-04-13 Thread Pavel Emelyanov
On 04/13/2015 04:21 PM, Laurent Dufour wrote: > On 13/04/2015 15:13, Kirill A. Shutemov wrote: >> On Mon, Apr 13, 2015 at 02:41:22PM +0200, Laurent Dufour wrote: >>> On 13/04/2015 13:58, Kirill A. Shutemov wrote: On Mon, Apr 13, 2015 at 11:56:27AM +0200, Laurent Dufour wrote: > Some archit

Re: [RESEND PATCH v3 1/2] mm: Introducing arch_remap hook

2015-04-13 Thread Laurent Dufour
On 13/04/2015 15:13, Kirill A. Shutemov wrote: > On Mon, Apr 13, 2015 at 02:41:22PM +0200, Laurent Dufour wrote: >> On 13/04/2015 13:58, Kirill A. Shutemov wrote: >>> On Mon, Apr 13, 2015 at 11:56:27AM +0200, Laurent Dufour wrote: Some architecture would like to be triggered when a memory area

Re: [RESEND PATCH v3 1/2] mm: Introducing arch_remap hook

2015-04-13 Thread Kirill A. Shutemov
On Mon, Apr 13, 2015 at 02:41:22PM +0200, Laurent Dufour wrote: > On 13/04/2015 13:58, Kirill A. Shutemov wrote: > > On Mon, Apr 13, 2015 at 11:56:27AM +0200, Laurent Dufour wrote: > >> Some architecture would like to be triggered when a memory area is moved > >> through the mremap system call. > >

Re: [RESEND PATCH v3 1/2] mm: Introducing arch_remap hook

2015-04-13 Thread Laurent Dufour
On 13/04/2015 13:58, Kirill A. Shutemov wrote: > On Mon, Apr 13, 2015 at 11:56:27AM +0200, Laurent Dufour wrote: >> Some architecture would like to be triggered when a memory area is moved >> through the mremap system call. >> >> This patch is introducing a new arch_remap mm hook which is placed in

Re: [RESEND PATCH v3 1/2] mm: Introducing arch_remap hook

2015-04-13 Thread Kirill A. Shutemov
On Mon, Apr 13, 2015 at 11:56:27AM +0200, Laurent Dufour wrote: > Some architecture would like to be triggered when a memory area is moved > through the mremap system call. > > This patch is introducing a new arch_remap mm hook which is placed in the > path of mremap, and is called before the old

[RESEND PATCH v3 1/2] mm: Introducing arch_remap hook

2015-04-13 Thread Laurent Dufour
Some architecture would like to be triggered when a memory area is moved through the mremap system call. This patch is introducing a new arch_remap mm hook which is placed in the path of mremap, and is called before the old area is unmapped (and the arch_unmap hook is called). The architectures w