From: kernel test robot <lkp@intel.com>
To: Patrick Roy <roypat@amazon.co.uk>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH v2 01/10] kvm: gmem: Add option to remove gmem from direct map
Date: Sat, 14 Sep 2024 01:43:11 +0800 [thread overview]
Message-ID: <202409140159.nGVKH1ST-lkp@intel.com> (raw)
In-Reply-To: <20240910163038.1298452-2-roypat@amazon.co.uk>
Hi Patrick,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on 332d2c1d713e232e163386c35a3ba0c1b90df83f]
url: https://github.com/intel-lab-lkp/linux/commits/Patrick-Roy/kvm-gmem-Add-option-to-remove-gmem-from-direct-map/20240911-003258
base: 332d2c1d713e232e163386c35a3ba0c1b90df83f
patch link: https://lore.kernel.org/r/20240910163038.1298452-2-roypat%40amazon.co.uk
patch subject: [RFC PATCH v2 01/10] kvm: gmem: Add option to remove gmem from direct map
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20240914/202409140159.nGVKH1ST-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240914/202409140159.nGVKH1ST-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/202409140159.nGVKH1ST-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/x86/kvm/../../../virt/kvm/guest_memfd.c:71:2: error: call to undeclared function 'flush_tlb_kernel_range'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
71 | flush_tlb_kernel_range(start, start + folio_size(folio));
| ^
1 error generated.
vim +/flush_tlb_kernel_range +71 arch/x86/kvm/../../../virt/kvm/guest_memfd.c
57
58 static int kvm_gmem_folio_set_private(struct folio *folio)
59 {
60 unsigned long start, npages, i;
61 int r;
62
63 start = (unsigned long) folio_address(folio);
64 npages = folio_nr_pages(folio);
65
66 for (i = 0; i < npages; ++i) {
67 r = set_direct_map_invalid_noflush(folio_page(folio, i));
68 if (r)
69 goto out_remap;
70 }
> 71 flush_tlb_kernel_range(start, start + folio_size(folio));
72 folio_set_private(folio);
73 return 0;
74 out_remap:
75 for (; i > 0; i--) {
76 struct page *page = folio_page(folio, i - 1);
77
78 if (WARN_ON_ONCE(set_direct_map_default_noflush(page))) {
79 /*
80 * Random holes in the direct map are bad, let's mark
81 * these pages as corrupted memory so that the kernel
82 * avoids ever touching them again.
83 */
84 folio_set_hwpoison(folio);
85 r = -EHWPOISON;
86 }
87 }
88 return r;
89 }
90
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-13 17:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 16:30 [RFC PATCH v2 00/10] Unmapping guest_memfd from Direct Map Patrick Roy
2024-09-10 16:30 ` [RFC PATCH v2 01/10] kvm: gmem: Add option to remove gmem from direct map Patrick Roy
2024-09-13 17:43 ` kernel test robot [this message]
2024-09-18 5:48 ` Mike Rapoport
2024-09-10 16:30 ` [RFC PATCH v2 02/10] kvm: gmem: Add KVM_GMEM_GET_PFN_SHARED Patrick Roy
2024-09-13 18:47 ` kernel test robot
2024-09-10 16:30 ` [RFC PATCH v2 03/10] kvm: gmem: Add KVM_GMEM_GET_PFN_LOCKED Patrick Roy
2024-09-10 16:30 ` [RFC PATCH v2 04/10] kvm: Allow reading/writing gmem using kvm_{read,write}_guest Patrick Roy
2024-09-10 16:30 ` [RFC PATCH v2 05/10] kvm: gmem: Refcount internal accesses to gmem Patrick Roy
2024-09-10 16:30 ` [RFC PATCH v2 06/10] kvm: gmem: add tracepoints for gmem share/unshare Patrick Roy
2024-10-04 22:50 ` Steven Rostedt
2024-09-10 16:30 ` [RFC PATCH v2 07/10] kvm: pfncache: invalidate when memory attributes change Patrick Roy
2024-09-13 18:04 ` kernel test robot
2024-09-10 16:30 ` [RFC PATCH v2 08/10] kvm: pfncache: Support caching gmem pfns Patrick Roy
2024-09-10 16:30 ` [RFC PATCH v2 09/10] kvm: pfncache: hook up to gmem invalidation Patrick Roy
2024-09-10 16:30 ` [RFC PATCH v2 10/10] kvm: x86: support walking guest page tables in gmem Patrick Roy
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=202409140159.nGVKH1ST-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=roypat@amazon.co.uk \
/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.