linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Bixuan Cui <cuibixuan@huawei.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
	<willy@infradead.org>, Mel Gorman <mgorman@techsingularity.net>
Subject: Re: [PATCH -next v2] mm/mmap_lock: fix warning when CONFIG_TRACING is not defined
Date: Mon, 31 May 2021 15:02:31 -0700	[thread overview]
Message-ID: <20210531150231.2e7bfdb063db06dfdfb81a26@linux-foundation.org> (raw)
In-Reply-To: <20210531033426.74031-1-cuibixuan@huawei.com>

On Mon, 31 May 2021 11:34:26 +0800 Bixuan Cui <cuibixuan@huawei.com> wrote:

> Fix the warning: [-Wunused-function]
> mm/mmap_lock.c:157:20: warning: ‘get_mm_memcg_path’ defined but not used
>  static const char *get_mm_memcg_path(struct mm_struct *mm)
>                     ^~~~~~~~~~~~~~~~~
> 
> Move get_mm_memcg_path() into #ifdef CONFIG_TRACING.

Thanks, I queued this as a fix against Mel's "mm/mmap_lock: remove dead
code for !CONFIG_TRACING configurations".


>  mm/mmap_lock.c | 60 ++++++++++++++++++++++++++------------------------
>  1 file changed, 31 insertions(+), 29 deletions(-)
> 
> diff --git a/mm/mmap_lock.c b/mm/mmap_lock.c
> index 03ee85c696ef..29e99af73144 100644
> --- a/mm/mmap_lock.c
> +++ b/mm/mmap_lock.c
> @@ -142,6 +142,37 @@ static inline void put_memcg_path_buf(void)
>  	rcu_read_unlock();
>  }
>  
> +#define TRACE_MMAP_LOCK_EVENT(type, mm, ...)                                   \
> +	do {                                                                   \
> +		const char *memcg_path;                                        \
> +		preempt_disable();                                             \
> +		memcg_path = get_mm_memcg_path(mm);                            \
> +		trace_mmap_lock_##type(mm,                                     \
> +				       memcg_path != NULL ? memcg_path : "",   \
> +				       ##__VA_ARGS__);                         \
> +		if (likely(memcg_path != NULL))                                \
> +			put_memcg_path_buf();                                  \
> +		preempt_enable();                                              \
> +	} while (0)
> +
> +#else /* !CONFIG_MEMCG */
> +
> +int trace_mmap_lock_reg(void)
> +{
> +	return 0;
> +}
> +
> +void trace_mmap_lock_unreg(void)
> +{
> +}
> +
> +#define TRACE_MMAP_LOCK_EVENT(type, mm, ...)                                   \
> +	trace_mmap_lock_##type(mm, "", ##__VA_ARGS__)
> +
> +#endif /* CONFIG_MEMCG */
> +
> +#ifdef CONFIG_TRACING
> +#ifdef CONFIG_MEMCG
>  /*
>   * Write the given mm_struct's memcg path to a percpu buffer, and return a
>   * pointer to it. If the path cannot be determined, or no buffer was available
> @@ -175,37 +206,8 @@ static const char *get_mm_memcg_path(struct mm_struct *mm)
>  out:
>  	return buf;
>  }
> -
> -#define TRACE_MMAP_LOCK_EVENT(type, mm, ...)                                   \
> -	do {                                                                   \
> -		const char *memcg_path;                                        \
> -		preempt_disable();                                             \
> -		memcg_path = get_mm_memcg_path(mm);                            \
> -		trace_mmap_lock_##type(mm,                                     \
> -				       memcg_path != NULL ? memcg_path : "",   \
> -				       ##__VA_ARGS__);                         \
> -		if (likely(memcg_path != NULL))                                \
> -			put_memcg_path_buf();                                  \
> -		preempt_enable();                                              \
> -	} while (0)
> -
> -#else /* !CONFIG_MEMCG */
> -
> -int trace_mmap_lock_reg(void)
> -{
> -	return 0;
> -}
> -
> -void trace_mmap_lock_unreg(void)
> -{
> -}
> -
> -#define TRACE_MMAP_LOCK_EVENT(type, mm, ...)                                   \
> -	trace_mmap_lock_##type(mm, "", ##__VA_ARGS__)
> -
>  #endif /* CONFIG_MEMCG */
>  
> -#ifdef CONFIG_TRACING
>  /*
>   * Trace calls must be in a separate file, as otherwise there's a circular
>   * dependency between linux/mmap_lock.h and trace/events/mmap_lock.h.
> -- 
> 2.17.1


      reply	other threads:[~2021-05-31 22:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31  3:34 Bixuan Cui
2021-05-31 22:02 ` Andrew Morton [this message]

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=20210531150231.2e7bfdb063db06dfdfb81a26@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=cuibixuan@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=willy@infradead.org \
    /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