All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Fuad Tabba <tabba@google.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH v4 06/14] KVM: guest_memfd: Handle final folio_put() of guestmem pages
Date: Sun, 15 Dec 2024 03:14:53 +0800	[thread overview]
Message-ID: <202412150337.y5jw6832-lkp@intel.com> (raw)
In-Reply-To: <20241213164811.2006197-7-tabba@google.com>

Hi Fuad,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:

[auto build test ERROR on fac04efc5c793dccbd07e2d59af9f90b7fc0dca4]

url:    https://github.com/intel-lab-lkp/linux/commits/Fuad-Tabba/mm-Consolidate-freeing-of-typed-folios-on-final-folio_put/20241214-005109
base:   fac04efc5c793dccbd07e2d59af9f90b7fc0dca4
patch link:    https://lore.kernel.org/r/20241213164811.2006197-7-tabba%40google.com
patch subject: [RFC PATCH v4 06/14] KVM: guest_memfd: Handle final folio_put() of guestmem pages
config: i386-buildonly-randconfig-005-20241215 (https://download.01.org/0day-ci/archive/20241215/202412150337.y5jw6832-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241215/202412150337.y5jw6832-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/202412150337.y5jw6832-lkp@intel.com/

All errors (new ones prefixed by >>):

   ld: mm/swap.o: in function `kvm_slot_gmem_register_callback':
>> include/linux/kvm_host.h:2621: multiple definition of `kvm_slot_gmem_register_callback'; arch/x86/events/intel/core.o:include/linux/kvm_host.h:2621: first defined here


vim +2621 include/linux/kvm_host.h

  2566	
  2567	#ifdef CONFIG_KVM_GMEM_MAPPABLE
  2568	bool kvm_gmem_is_mappable(struct kvm *kvm, gfn_t gfn, gfn_t end);
  2569	int kvm_gmem_set_mappable(struct kvm *kvm, gfn_t start, gfn_t end);
  2570	int kvm_gmem_clear_mappable(struct kvm *kvm, gfn_t start, gfn_t end);
  2571	int kvm_slot_gmem_set_mappable(struct kvm_memory_slot *slot, gfn_t start,
  2572				       gfn_t end);
  2573	int kvm_slot_gmem_clear_mappable(struct kvm_memory_slot *slot, gfn_t start,
  2574					 gfn_t end);
  2575	bool kvm_slot_gmem_is_mappable(struct kvm_memory_slot *slot, gfn_t gfn);
  2576	bool kvm_slot_gmem_is_guest_mappable(struct kvm_memory_slot *slot, gfn_t gfn);
  2577	int kvm_slot_gmem_register_callback(struct kvm_memory_slot *slot, gfn_t gfn);
  2578	void kvm_gmem_handle_folio_put(struct folio *folio);
  2579	#else
  2580	static inline bool kvm_gmem_is_mappable(struct kvm *kvm, gfn_t gfn, gfn_t end)
  2581	{
  2582		WARN_ON_ONCE(1);
  2583		return false;
  2584	}
  2585	static inline int kvm_gmem_set_mappable(struct kvm *kvm, gfn_t start, gfn_t end)
  2586	{
  2587		WARN_ON_ONCE(1);
  2588		return -EINVAL;
  2589	}
  2590	static inline int kvm_gmem_clear_mappable(struct kvm *kvm, gfn_t start,
  2591						  gfn_t end)
  2592	{
  2593		WARN_ON_ONCE(1);
  2594		return -EINVAL;
  2595	}
  2596	static inline int kvm_slot_gmem_set_mappable(struct kvm_memory_slot *slot,
  2597						     gfn_t start, gfn_t end)
  2598	{
  2599		WARN_ON_ONCE(1);
  2600		return -EINVAL;
  2601	}
  2602	static inline int kvm_slot_gmem_clear_mappable(struct kvm_memory_slot *slot,
  2603						       gfn_t start, gfn_t end)
  2604	{
  2605		WARN_ON_ONCE(1);
  2606		return -EINVAL;
  2607	}
  2608	static inline bool kvm_slot_gmem_is_mappable(struct kvm_memory_slot *slot,
  2609						     gfn_t gfn)
  2610	{
  2611		WARN_ON_ONCE(1);
  2612		return false;
  2613	}
  2614	static inline bool kvm_slot_gmem_is_guest_mappable(struct kvm_memory_slot *slot,
  2615							   gfn_t gfn)
  2616	{
  2617		WARN_ON_ONCE(1);
  2618		return false;
  2619	}
  2620	int kvm_slot_gmem_register_callback(struct kvm_memory_slot *slot, gfn_t gfn)
> 2621	{
  2622		WARN_ON_ONCE(1);
  2623		return -EINVAL;
  2624	}
  2625	static inline void kvm_gmem_handle_folio_put(struct folio *folio)
  2626	{
  2627		WARN_ON_ONCE(1);
  2628	}
  2629	#endif /* CONFIG_KVM_GMEM_MAPPABLE */
  2630	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2024-12-14 19:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13 16:47 [RFC PATCH v4 00/14] KVM: Restricted mapping of guest_memfd at the host and arm64 support Fuad Tabba
2024-12-13 16:47 ` [RFC PATCH v4 01/14] mm: Consolidate freeing of typed folios on final folio_put() Fuad Tabba
2024-12-14 19:48   ` kernel test robot
2024-12-13 16:47 ` [RFC PATCH v4 02/14] KVM: guest_memfd: Make guest mem use guest mem inodes instead of anonymous inodes Fuad Tabba
2024-12-13 16:47 ` [RFC PATCH v4 03/14] KVM: guest_memfd: Introduce kvm_gmem_get_pfn_locked(), which retains the folio lock Fuad Tabba
2024-12-13 16:48 ` [RFC PATCH v4 04/14] KVM: guest_memfd: Track mappability within a struct kvm_gmem_private Fuad Tabba
2024-12-13 16:48 ` [RFC PATCH v4 05/14] KVM: guest_memfd: Folio mappability states and functions that manage their transition Fuad Tabba
2024-12-13 16:48 ` [RFC PATCH v4 06/14] KVM: guest_memfd: Handle final folio_put() of guestmem pages Fuad Tabba
2024-12-14 18:53   ` kernel test robot
2024-12-14 19:14   ` kernel test robot [this message]
2024-12-13 16:48 ` [RFC PATCH v4 07/14] KVM: guest_memfd: Allow host to mmap guest_memfd() pages when shared Fuad Tabba
2024-12-27  4:21   ` Alexey Kardashevskiy
2025-01-09 10:17     ` Fuad Tabba
2024-12-13 16:48 ` [RFC PATCH v4 08/14] KVM: guest_memfd: Add guest_memfd support to kvm_(read|/write)_guest_page() Fuad Tabba
2024-12-13 16:48 ` [RFC PATCH v4 09/14] KVM: guest_memfd: Add KVM capability to check if guest_memfd is host mappable Fuad Tabba
2024-12-13 16:48 ` [RFC PATCH v4 10/14] KVM: guest_memfd: Add a guest_memfd() flag to initialize it as mappable Fuad Tabba
2024-12-13 16:48 ` [RFC PATCH v4 11/14] KVM: guest_memfd: selftests: guest_memfd mmap() test when mapping is allowed Fuad Tabba
2024-12-13 16:48 ` [RFC PATCH v4 12/14] KVM: arm64: Skip VMA checks for slots without userspace address Fuad Tabba
2024-12-13 16:48 ` [RFC PATCH v4 13/14] KVM: arm64: Handle guest_memfd()-backed guest page faults Fuad Tabba
2025-01-16 14:48   ` Patrick Roy
2025-01-16 15:16     ` Fuad Tabba
2024-12-13 16:48 ` [RFC PATCH v4 14/14] KVM: arm64: Enable guest_memfd private memory when pKVM is enabled Fuad Tabba
2025-01-09 16:34 ` [RFC PATCH v4 00/14] KVM: Restricted mapping of guest_memfd at the host and arm64 support Fuad Tabba
2025-01-16  0:35   ` Ackerley Tng
2025-01-16  9:19     ` Fuad Tabba
2025-01-20  9:26       ` Vlastimil Babka
2025-01-20  9:36         ` David Hildenbrand
2025-01-16 14:48 ` Patrick Roy
2025-01-16 15:02   ` Fuad Tabba

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=202412150337.y5jw6832-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tabba@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.