Re: [PATCH] mm: Support compiling out madvise and fadvise

From: josh
Date: Thu Sep 25 2014 - 14:27:15 EST


On Thu, Sep 25, 2014 at 01:21:13PM -0400, Johannes Weiner wrote:
> On Mon, Sep 22, 2014 at 09:11:16AM -0700, Josh Triplett wrote:
> > @@ -3,7 +3,7 @@
> > #
> >
> > mmu-y := nommu.o
> > -mmu-$(CONFIG_MMU) := fremap.o gup.o highmem.o madvise.o memory.o mincore.o \
> > +mmu-$(CONFIG_MMU) := fremap.o gup.o highmem.o memory.o mincore.o \
> > mlock.o mmap.o mprotect.o mremap.o msync.o rmap.o \
> > vmalloc.o pagewalk.o pgtable-generic.o
> >
> > @@ -11,7 +11,7 @@ ifdef CONFIG_CROSS_MEMORY_ATTACH
> > mmu-$(CONFIG_MMU) += process_vm_access.o
> > endif
> >
> > -obj-y := filemap.o mempool.o oom_kill.o fadvise.o \
> > +obj-y := filemap.o mempool.o oom_kill.o \
> > maccess.o page_alloc.o page-writeback.o \
> > readahead.o swap.o truncate.o vmscan.o shmem.o \
> > util.o mmzone.o vmstat.o backing-dev.o \
> > @@ -28,6 +28,9 @@ else
> > obj-y += bootmem.o
> > endif
> >
> > +ifdef CONFIG_MMU
> > + obj-$(CONFIG_ADVISE_SYSCALLS) += fadvise.o madvise.o
> > +endif
>
> That makes fadvise MMU-only, but I don't see why it should be.
>
> Was that intentional?

No. Fixed in v2; will send out momentarily. Thanks!

- Josh Triplett
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/