github-mirror/linux
1
0
Fork 0
mirror of https://github.com/torvalds/linux.git synced 2026-07-27 01:32:21 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity Graph

tools headers: Sync linux/gfp_types.h with the kernel sources

Browse Source 
To pick up the changes in:

  b56ca146a2 ("vmalloc: add __GFP_SKIP_KASAN support")
  6a288a4ddb ("mm/page_alloc: fix initialization of tags of the huge zero folio with init_on_free")

That just rebuilds perf, silencing this build warning.

This addresses this perf build warning:

  Warning: Kernel ABI header differences:
    diff -u tools/include/linux/gfp_types.h include/linux/gfp_types.h

Please see tools/include/uapi/README for further details.

Cc: David Hildenbrand (Arm) <david@kernel.org>
Cc: Muhammad Usama Anjum <usama.anjum@arm.com>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
This commit is contained in:
Arnaldo Carvalho de Melo 2026-06-25 13:02:08 -03:00
parent edc148762e
commit 5bbaca187c
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
tools/include/linux/gfp_types.h
View File

@ -273,17 +273,17 @@ enum {
*
* %__GFP_ZERO returns a zeroed page on success.
*
* %__GFP_ZEROTAGS zeroes memory tags at allocation time if the memory itself
* is being zeroed (either via __GFP_ZERO or via init_on_alloc, provided that
* __GFP_SKIP_ZERO is not set). This flag is intended for optimization: setting
* memory tags at the same time as zeroing memory has minimal additional
* performance impact.
* %__GFP_ZEROTAGS zeroes memory tags at allocation time. Setting memory tags at
* the same time as zeroing memory (e.g., with __GFP_ZERO) has minimal
* additional performance impact. However, __GFP_ZEROTAGS also zeroes the tags
* even if memory is not getting zeroed at allocation time (e.g.,
* with init_on_free).
*
* %__GFP_SKIP_KASAN makes KASAN skip unpoisoning on page allocation.
* Used for userspace and vmalloc pages; the latter are unpoisoned by
* kasan_unpoison_vmalloc instead. For userspace pages, results in
* poisoning being skipped as well, see should_skip_kasan_poison for
* details. Only effective in HW_TAGS mode.
* kasan_unpoison_vmalloc instead. If passed to vmalloc, kasan_unpoison_vmalloc
* is skipped too. For userspace pages, results in poisoning being skipped as
* well, see should_skip_kasan_poison for details. Only effective in HW_TAGS mode.
*/
#define __GFP_NOWARN ((__force gfp_t)___GFP_NOWARN)
#define __GFP_COMP ((__force gfp_t)___GFP_COMP)