Re: [PATCH 0/3] generic asm: mman cleanup

2019-02-18 Thread Arnd Bergmann
On Mon, Feb 11, 2019 at 5:20 AM Michael S. Tsirkin wrote: > > On Fri, Feb 08, 2019 at 01:02:51AM -0500, Michael S. Tsirkin wrote: > > Now that we have MAP_SHARED, MAP_PRIVATE and MAP_SHARED_VALIDATE on all > > architectures, it probably makes sense to de-duplicate these > > and put them into a

Re: [PATCH 0/3] generic asm: mman cleanup

2019-02-10 Thread Michael S. Tsirkin
On Fri, Feb 08, 2019 at 01:02:51AM -0500, Michael S. Tsirkin wrote: > Now that we have MAP_SHARED, MAP_PRIVATE and MAP_SHARED_VALIDATE on all > architectures, it probably makes sense to de-duplicate these > and put them into a common header. > > Please review and consider merging though the

Re: [PATCH 0/3] generic asm: mman cleanup

2019-02-08 Thread Michael S. Tsirkin
On Fri, Feb 08, 2019 at 08:12:47PM +0200, Mike Rapoport wrote: > On Fri, Feb 08, 2019 at 01:02:51AM -0500, Michael S. Tsirkin wrote: > > Now that we have MAP_SHARED, MAP_PRIVATE and MAP_SHARED_VALIDATE on all > > architectures, it probably makes sense to de-duplicate these > > and put them into a

Re: [PATCH 0/3] generic asm: mman cleanup

2019-02-08 Thread Mike Rapoport
On Fri, Feb 08, 2019 at 01:02:51AM -0500, Michael S. Tsirkin wrote: > Now that we have MAP_SHARED, MAP_PRIVATE and MAP_SHARED_VALIDATE on all > architectures, it probably makes sense to de-duplicate these > and put them into a common header. I like the idea, but it seems there are more asm/mman.h

[PATCH 0/3] generic asm: mman cleanup

2019-02-07 Thread Michael S. Tsirkin
Now that we have MAP_SHARED, MAP_PRIVATE and MAP_SHARED_VALIDATE on all architectures, it probably makes sense to de-duplicate these and put them into a common header. Please review and consider merging though the generic tree. Build tested on x86 only. Has been in linux-next for a while now.