linux-stable.git/tools/testing/selftests/vm/Makefile, branch linux-5.14.y

secretmem: test: add basic selftest for memfd_secret(2)

2021-07-08T18:48:21+00:00

The test verifies that file descriptor created with memfd_secret does not
allow read/write operations, that secret memory mappings respect
RLIMIT_MEMLOCK and that remote accesses with process_vm_read() and
ptrace() to the secret memory fail.

Link: https://lkml.kernel.org/r/20210518072034.31572-8-rppt@kernel.org
Signed-off-by: Mike Rapoport 
Acked-by: James Bottomley 
Cc: Alexander Viro 
Cc: Andy Lutomirski 
Cc: Arnd Bergmann 
Cc: Borislav Petkov 
Cc: Catalin Marinas 
Cc: Christopher Lameter 
Cc: Dan Williams 
Cc: Dave Hansen 
Cc: David Hildenbrand 
Cc: Elena Reshetova 
Cc: Hagen Paul Pfeifer 
Cc: "H. Peter Anvin" 
Cc: Ingo Molnar 
Cc: James Bottomley 
Cc: "Kirill A. Shutemov" 
Cc: Mark Rutland 
Cc: Matthew Wilcox 
Cc: Michael Kerrisk 
Cc: Palmer Dabbelt 
Cc: Palmer Dabbelt 
Cc: Paul Walmsley 
Cc: Peter Zijlstra 
Cc: Rick Edgecombe 
Cc: Roman Gushchin 
Cc: Shakeel Butt 
Cc: Shuah Khan 
Cc: Thomas Gleixner 
Cc: Tycho Andersen 
Cc: Will Deacon 
Cc: kernel test robot 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

selftests/vm/pkeys: exercise x86 XSAVE init state

2021-07-01T18:06:06+00:00

On x86, there is a set of instructions used to save and restore register
state collectively known as the XSAVE architecture.  There are about a
dozen different features managed with XSAVE.  The protection keys
register, PKRU, is one of those features.

The hardware optimizes XSAVE by tracking when the state has not changed
from its initial (init) state.  In this case, it can avoid the cost of
writing state to memory (it would usually just be a bunch of 0's).

When the pkey register is 0x0 the hardware optionally choose to track the
register as being in the init state (optimize away the writes).  AMD CPUs
do this more aggressively compared to Intel.

On x86, PKRU is rarely in its (very permissive) init state.  Instead, the
value defaults to something very restrictive.  It is not surprising that
bugs have popped up in the rare cases when PKRU reaches its init state.

Add a protection key selftest which gets the protection keys register into
its init state in a way that should work on Intel and AMD.  Then, do a
bunch of pkey register reads to watch for inadvertent changes.

This adds "-mxsave" to CFLAGS for all the x86 vm selftests in order to
allow use of the XSAVE instruction __builtin functions.  This will make
the builtins available on all of the vm selftests, but is expected to be
harmless.

Link: https://lkml.kernel.org/r/20210611164202.1849B712@viggo.jf.intel.com
Signed-off-by: Dave Hansen 
Signed-off-by: Thomas Gleixner 
Tested-by: Aneesh Kumar K.V 
Cc: Ram Pai 
Cc: Sandipan Das 
Cc: Florian Weimer 
Cc: "Desnes A. Nunes do Rosario" 
Cc: Ingo Molnar 
Cc: Thiago Jung Bauermann 
Cc: Michael Ellerman 
Cc: Michal Hocko 
Cc: Michal Suchanek 
Cc: Shuah Khan 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

selftests/vm: add test for MADV_POPULATE_(READ|WRITE)

2021-07-01T03:47:31+00:00

Let's add a simple test for MADV_POPULATE_READ and MADV_POPULATE_WRITE,
verifying some error handling, that population works, and that softdirty
tracking works as expected.  For now, limit the test to private anonymous
memory.

Link: https://lkml.kernel.org/r/20210419135443.12822-6-david@redhat.com
Signed-off-by: David Hildenbrand 
Cc: Arnd Bergmann 
Cc: Michal Hocko 
Cc: Oscar Salvador 
Cc: Matthew Wilcox (Oracle) 
Cc: Andrea Arcangeli 
Cc: Minchan Kim 
Cc: Jann Horn 
Cc: Jason Gunthorpe 
Cc: Dave Hansen 
Cc: Hugh Dickins 
Cc: Rik van Riel 
Cc: Michael S. Tsirkin 
Cc: Kirill A. Shutemov 
Cc: Vlastimil Babka 
Cc: Richard Henderson 
Cc: Ivan Kokshaysky 
Cc: Matt Turner 
Cc: Thomas Bogendoerfer 
Cc: "James E.J. Bottomley" 
Cc: Helge Deller 
Cc: Chris Zankel 
Cc: Max Filippov 
Cc: Mike Kravetz 
Cc: Peter Xu 
Cc: Rolf Eike Beer 
Cc: Shuah Khan 
Cc: Ram Pai 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

mm: huge_memory: a new debugfs interface for splitting THP tests

2021-05-05T18:27:21+00:00

We did not have a direct user interface of splitting the compound page
backing a THP and there is no need unless we want to expose the THP
implementation details to users.  Make /split_huge_pages accept a
new command to do that.

By writing ",," to
/split_huge_pages, THPs within the given virtual address range
from the process with the given pid are split. It is used to test
split_huge_page function. In addition, a selftest program is added to
tools/testing/selftests/vm to utilize the interface by splitting
PMD THPs and PTE-mapped THPs.

This does not change the old behavior, i.e., writing 1 to the interface
to split all THPs in the system.

Link: https://lkml.kernel.org/r/20210331235309.332292-1-zi.yan@sent.com
Signed-off-by: Zi Yan 
Reviewed-by: Yang Shi 
Cc: David Hildenbrand 
Cc: David Rientjes 
Cc: John Hubbard 
Cc: "Kirill A . Shutemov" 
Cc: Matthew Wilcox 
Cc: Mika Penttila 
Cc: Sandipan Das 
Cc: Shuah Khan 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

selftests/vm: fix out-of-tree build

2021-03-25T16:22:55+00:00

When building out-of-tree, attempting to make target from $(OUTPUT) directory:

  make[1]: *** No rule to make target '$(OUTPUT)/protection_keys.c', needed by '$(OUTPUT)/protection_keys_32'.

Link: https://lkml.kernel.org/r/20210315094700.522753-1-rong.a.chen@intel.com
Signed-off-by: Rong Chen 
Reported-by: kernel test robot 
Cc: Shuah Khan 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

selftests/vm: fix building protection keys test

2020-12-29T23:36:49+00:00

Commit d8cbe8bfa7d ("tools/testing/selftests/vm: fix build error") tried
to include a ARCH check for powerpc, however ARCH is not defined in the
Makefile before including lib.mk.  This makes test building to skip on
both x86 and powerpc.

Fix the arch check by replacing it using machine type as it is already
defined and used in the test.

Link: https://lkml.kernel.org/r/20201215100402.257376-1-harish@linux.ibm.com
Fixes: d8cbe8bfa7d ("tools/testing/selftests/vm: fix build error")
Signed-off-by: Harish 
Reviewed-by: Sandipan Das 
Cc: Shuah Khan 
Cc: Sandipan Das 
Cc: John Hubbard 
Cc: Dave Hansen 
Cc: Kirill A. Shutemov 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

kselftests: vm: add mremap tests

2020-12-15T20:13:40+00:00

Patch series "Speed up mremap on large regions", v4.

mremap time can be optimized by moving entries at the PMD/PUD level if the
source and destination addresses are PMD/PUD-aligned and PMD/PUD-sized.
Enable moving at the PMD and PUD levels on arm64 and x86.  Other
architectures where this type of move is supported and known to be safe
can also opt-in to these optimizations by enabling HAVE_MOVE_PMD and
HAVE_MOVE_PUD.

Observed Performance Improvements for remapping a PUD-aligned 1GB-sized
region on x86 and arm64:

    - HAVE_MOVE_PMD is already enabled on x86 : N/A
    - Enabling HAVE_MOVE_PUD on x86   : ~13x speed up

    - Enabling HAVE_MOVE_PMD on arm64 : ~ 8x speed up
    - Enabling HAVE_MOVE_PUD on arm64 : ~19x speed up

          Altogether, HAVE_MOVE_PMD and HAVE_MOVE_PUD
          give a total of ~150x speed up on arm64.

This patch (of 4):

Test mremap on regions of various sizes and alignments and validate data
after remapping.  Also provide total time for remapping the region which
is useful for performance comparison of the mremap optimizations that move
pages at the PMD/PUD levels if HAVE_MOVE_PMD and/or HAVE_MOVE_PUD are
enabled.

Link: https://lkml.kernel.org/r/20201014005320.2233162-1-kaleshsingh@google.com
Link: https://lkml.kernel.org/r/20201014005320.2233162-2-kaleshsingh@google.com
Signed-off-by: Kalesh Singh 
Reviewed-by: John Hubbard 
Cc: Shuah Khan 
Cc: Kirill A. Shutemov 
Cc: Suren Baghdasaryan 
Cc: Minchan Kim 
Cc: Lokesh Gidra 
Cc: Thomas Gleixner 
Cc: Ingo Molnar 
Cc: Borislav Petkov 
Cc: "H. Peter Anvin" 
Cc: Catalin Marinas 
Cc: Will Deacon 
Cc: Peter Zijlstra (Intel) 
Cc: Kees Cook 
Cc: Aneesh Kumar K.V 
Cc: Arnd Bergmann 
Cc: Sami Tolvanen 
Cc: Masahiro Yamada 
Cc: Krzysztof Kozlowski 
Cc: Frederic Weisbecker 
Cc: Hassan Naveed 
Cc: Christian Brauner 
Cc: Anshuman Khandual 
Cc: Mark Rutland 
Cc: Gavin Shan 
Cc: Mike Rapoport 
Cc: Steven Price 
Cc: Jia He 
Cc: Ram Pai 
Cc: Sandipan Das 
Cc: Zi Yan 
Cc: Mina Almasry 
Cc: Ralph Campbell 
Cc: Dave Hansen 
Cc: Brian Geffon 
Cc: Masami Hiramatsu 
Cc: SeongJae Park 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

selftests/vm: hmm-tests: remove the libhugetlbfs dependency

2020-12-15T20:13:38+00:00

HMM selftests are incredibly useful, but they are only effective if people
actually build and run them.  All the other tests in selftests/vm can be
built with very standard, always-available libraries: libpthread, librt.
The hmm-tests.c program, on the other hand, requires something that is
(much) less readily available: libhugetlbfs.  And so the build will
typically fail for many developers.

A simple attempt to install libhugetlbfs will also run into complications
on some common distros these days: Fedora and Arch Linux (yes, Arch AUR
has it, but that's fragile, as always with AUR).  The library is not
maintained actively enough at the moment, for distros to deal with it.  I
had to build it from source, for Fedora, and that didn't go too smoothly
either.

It turns out that, out of 21 tests in hmm-tests.c, only 2 actually require
functionality from libhugetlbfs.  Therefore, if libhugetlbfs is missing,
simply ifdef those two tests out and allow the developer to at least have
the other 19 tests, if they don't want to pause to work through the above
issues.  Also issue a warning, so that it's clear that there is an
imperfection in the build.

In order to do that, a tiny shell script (check_config.sh) runs a quick
compile (not link, that's too prone to false failures with library paths),
and basically, if the compiler doesn't find hugetlbfs.h in its standard
locations, then the script concludes that libhugetlbfs is not available.
The output is in two files, one for inclusion in hmm-test.c
(local_config.h), and one for inclusion in the Makefile (local_config.mk).

Link: https://lkml.kernel.org/r/20201026064021.3545418-9-jhubbard@nvidia.com
Signed-off-by: John Hubbard 
Cc: Ralph Campbell 
Cc: Jérôme Glisse 
Cc: Jonathan Corbet 
Cc: Shuah Khan 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

selftests/vm: minor cleanup: Makefile and gup_test.c

2020-12-15T20:13:38+00:00

A few cleanups that don't deserve separate patches, but that also should
not clutter up other functional changes:

1. Remove an unnecessary #include 

2. Restore the sorted order of TEST_GEN_FILES.

3. Add -lpthread to the common LDLIBS, as it is harmless and several
   tests use it. This gets rid of one special rule already.

Link: https://lkml.kernel.org/r/20201026064021.3545418-5-jhubbard@nvidia.com
Signed-off-by: John Hubbard 
Cc: Jérôme Glisse 
Cc: Jonathan Corbet 
Cc: Ralph Campbell 
Cc: Shuah Khan 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

selftests/vm: rename run_vmtests --> run_vmtests.sh

2020-12-15T20:13:38+00:00

Rename to *.sh, in order to match the conventions of all of the other
items in selftest/vm.

The only reason not to use a .sh suffix a shell script like this, might be
to make it look more like a normal program, but that's not an issue here.

Link: https://lkml.kernel.org/r/20201026064021.3545418-4-jhubbard@nvidia.com
Signed-off-by: John Hubbard 
Cc: Jérôme Glisse 
Cc: Jonathan Corbet 
Cc: Ralph Campbell 
Cc: Shuah Khan 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds