mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Suren Baghdasaryan <surenb@google.com>, akpm@linux-foundation.org
Cc: kent.overstreet@linux.dev, hch@infradead.org,
	pasha.tatashin@soleen.com, souravpanda@google.com,
	keescook@chromium.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2 2/2] alloc_tag: outline and export free_reserved_page()
Date: Wed, 17 Jul 2024 21:35:56 +0200	[thread overview]
Message-ID: <16286915-1350-4e6b-a0f6-deec02b7fa92@suse.cz> (raw)
In-Reply-To: <20240717181239.2510054-2-surenb@google.com>

On 7/17/24 8:12 PM, Suren Baghdasaryan wrote:
> Outline and export free_reserved_page() because modules use it and it
> in turn uses page_ext_{get|put} which should not be exported. The same
> result could be obtained by outlining {get|put}_page_tag_ref() but that
> would have higher performance impact as these functions are used in
> more performance critical paths.
> 
> Fixes: dcfe378c81f7 ("lib: introduce support for page allocation tagging")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202407080044.DWMC9N9I-lkp@intel.com/
> Suggested-by: Christoph Hellwig <hch@infradead.org>
> Suggested-by: Vlastimil Babka <vbabka@suse.cz>
> Signed-off-by: Suren Baghdasaryan <surenb@google.com>

Acked-by: Vlastimil Babka <vbabka@suse.cz>

Are these two patches now stable@ material as 6.10 build is broken on ppc64
with alloc taging enabled?

> ---
> Changes since v1 [1]
> - Outlined and exported free_reserved_page() in place of {get|put}_page_tag_ref,
> per Vlastimil Babka
> 
> [1] https://lore.kernel.org/all/20240717011631.2150066-2-surenb@google.com/
> 
>  include/linux/mm.h | 16 +---------------
>  mm/page_alloc.c    | 17 +++++++++++++++++
>  2 files changed, 18 insertions(+), 15 deletions(-)
> 
> diff --git a/include/linux/mm.h b/include/linux/mm.h
> index eb7c96d24ac0..b58bad248eef 100644
> --- a/include/linux/mm.h
> +++ b/include/linux/mm.h
> @@ -3177,21 +3177,7 @@ extern void reserve_bootmem_region(phys_addr_t start,
>  				   phys_addr_t end, int nid);
>  
>  /* Free the reserved page into the buddy system, so it gets managed. */
> -static inline void free_reserved_page(struct page *page)
> -{
> -	if (mem_alloc_profiling_enabled()) {
> -		union codetag_ref *ref = get_page_tag_ref(page);
> -
> -		if (ref) {
> -			set_codetag_empty(ref);
> -			put_page_tag_ref(ref);
> -		}
> -	}
> -	ClearPageReserved(page);
> -	init_page_count(page);
> -	__free_page(page);
> -	adjust_managed_page_count(page, 1);
> -}
> +void free_reserved_page(struct page *page);
>  #define free_highmem_page(page) free_reserved_page(page)
>  
>  static inline void mark_page_reserved(struct page *page)
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 9ecf99190ea2..7d2fa9f5e750 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -5805,6 +5805,23 @@ unsigned long free_reserved_area(void *start, void *end, int poison, const char
>  	return pages;
>  }
>  
> +void free_reserved_page(struct page *page)
> +{
> +	if (mem_alloc_profiling_enabled()) {
> +		union codetag_ref *ref = get_page_tag_ref(page);
> +
> +		if (ref) {
> +			set_codetag_empty(ref);
> +			put_page_tag_ref(ref);
> +		}
> +	}
> +	ClearPageReserved(page);
> +	init_page_count(page);
> +	__free_page(page);
> +	adjust_managed_page_count(page, 1);
> +}
> +EXPORT_SYMBOL(free_reserved_page);
> +
>  static int page_alloc_cpu_dead(unsigned int cpu)
>  {
>  	struct zone *zone;


  reply	other threads:[~2024-07-17 19:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-17 18:12 [PATCH v2 1/2] alloc_tag: export mem_alloc_profiling_key used by modules Suren Baghdasaryan
2024-07-17 18:12 ` [PATCH v2 2/2] alloc_tag: outline and export free_reserved_page() Suren Baghdasaryan
2024-07-17 19:35   ` Vlastimil Babka [this message]
2024-07-17 20:04     ` Suren Baghdasaryan
2024-07-17 20:19       ` Vlastimil Babka
2024-07-17 21:20         ` Suren Baghdasaryan
2024-07-17 21:30           ` Suren Baghdasaryan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16286915-1350-4e6b-a0f6-deec02b7fa92@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=keescook@chromium.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=souravpanda@google.com \
    --cc=surenb@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®