linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Zi Yan <ziy@nvidia.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	"Huang, Ying" <ying.huang@intel.com>
Subject: Re: [akpm-mm:mm-unstable 9/30] mm/memory-tiers.c:64:6: error: redefinition of 'folio_has_cpupid'
Date: Tue, 23 Jul 2024 12:35:23 -0400	[thread overview]
Message-ID: <92316F08-AF73-46E6-B82D-E40970CB6E94@nvidia.com> (raw)
In-Reply-To: <202407240024.Lhu1XDok-lkp@intel.com>

[-- Attachment #1: Type: text/plain, Size: 2378 bytes --]

On 23 Jul 2024, at 12:32, kernel test robot wrote:

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
> head:   cecb3db438d76f7c1005fd52689809696a330474
> commit: c57ceb62609b36d1a01e8bdd894d032379999b75 [9/30] memory tiering: introduce folio_has_cpupid() check
> config: sparc-allmodconfig (https://download.01.org/0day-ci/archive/20240724/202407240024.Lhu1XDok-lkp@intel.com/config)
> compiler: sparc64-linux-gcc (GCC) 14.1.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240724/202407240024.Lhu1XDok-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202407240024.Lhu1XDok-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
>>> mm/memory-tiers.c:64:6: error: redefinition of 'folio_has_cpupid'
>       64 | bool folio_has_cpupid(struct folio *folio)
>          |      ^~~~~~~~~~~~~~~~
>    In file included from mm/internal.h:11,
>                     from mm/memory-tiers.c:11:
>    include/linux/mm.h:1796:20: note: previous definition of 'folio_has_cpupid' with type 'bool(struct folio *)' {aka '_Bool(struct folio *)'}
>     1796 | static inline bool folio_has_cpupid(struct folio *folio)
>          |                    ^~~~~~~~~~~~~~~~
>
>
> vim +/folio_has_cpupid +64 mm/memory-tiers.c
>
>     53	
>     54	/**
>     55	 * folio_has_cpupid - check if a folio has cpupid information
>     56	 * @folio: folio to check
>     57	 *
>     58	 * folio's _last_cpupid field is repurposed by memory tiering. In memory
>     59	 * tiering mode, cpupid of slow memory folio (not toptier memory) is used to
>     60	 * record page access time.
>     61	 *
>     62	 * Return: the folio _last_cpupid is used as cpupid
>     63	 */
>   > 64	bool folio_has_cpupid(struct folio *folio)
>     65	{
>     66		return !(sysctl_numa_balancing_mode & NUMA_BALANCING_MEMORY_TIERING) ||
>     67		       node_is_toptier(folio_nid(folio));
>     68	}
>     69	

The error has been reported by Lorenzo Stoakes at: https://lore.kernel.org/linux-mm/6effd690-3cf2-46bc-8061-2d19922ad4fa@lucifer.local/.
I will fix it in the next version.

Best Regards,
Yan, Zi

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]

  reply	other threads:[~2024-07-23 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23 16:32 kernel test robot
2024-07-23 16:35 ` Zi Yan [this message]
2024-07-23 21:45   ` Andrew Morton
2024-07-23 21:51     ` Zi Yan

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=92316F08-AF73-46E6-B82D-E40970CB6E94@nvidia.com \
    --to=ziy@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ying.huang@intel.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