From: kernel test robot <lkp@intel.com>
To: mhkelley58@gmail.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, linux-kernel@vger.kernel.org,
linux-hyperv@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, david@redhat.com
Subject: Re: [PATCH v2 2/2] hv_balloon: Enable hot-add for memblock sizes > 128 MiB
Date: Fri, 3 May 2024 04:49:20 +0800 [thread overview]
Message-ID: <202405030421.x7E4hUI7-lkp@intel.com> (raw)
In-Reply-To: <20240501151458.2807-2-mhklinux@outlook.com>
Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.9-rc6 next-20240502]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/mhkelley58-gmail-com/hv_balloon-Enable-hot-add-for-memblock-sizes-128-MiB/20240501-232643
base: linus/master
patch link: https://lore.kernel.org/r/20240501151458.2807-2-mhklinux%40outlook.com
patch subject: [PATCH v2 2/2] hv_balloon: Enable hot-add for memblock sizes > 128 MiB
config: i386-randconfig-011-20240502 (https://download.01.org/0day-ci/archive/20240503/202405030421.x7E4hUI7-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240503/202405030421.x7E4hUI7-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/202405030421.x7E4hUI7-lkp@intel.com/
All errors (new ones prefixed by >>):
ld: drivers/hv/hv_balloon.o: in function `init_balloon_drv':
>> drivers/hv/hv_balloon.c:2147:(.init.text+0x4): undefined reference to `memory_block_size_bytes'
vim +2147 drivers/hv/hv_balloon.c
2136
2137 static int __init init_balloon_drv(void)
2138 {
2139 /*
2140 * Hot-add must operate in chunks that are of size
2141 * equal to the memory block size because that's
2142 * what the core add_memory() interface requires.
2143 * The Hyper-V interface requires that the memory block
2144 * size be a power of 2, which is guaranteed by the
2145 * check in memory_dev_init().
2146 */
> 2147 ha_pages_in_chunk = memory_block_size_bytes() / PAGE_SIZE;
2148
2149 return vmbus_driver_register(&balloon_drv);
2150 }
2151
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-05-02 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 15:14 [PATCH v2 1/2] hv_balloon: Use kernel macros to simplify open coded sequences mhkelley58
2024-05-01 15:14 ` [PATCH v2 2/2] hv_balloon: Enable hot-add for memblock sizes > 128 MiB mhkelley58
2024-05-02 7:17 ` David Hildenbrand
2024-05-02 22:40 ` Michael Kelley
2024-05-02 17:29 ` kernel test robot
2024-05-02 20:49 ` kernel test robot [this message]
2024-05-02 7:06 ` [PATCH v2 1/2] hv_balloon: Use kernel macros to simplify open coded sequences David Hildenbrand
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=202405030421.x7E4hUI7-lkp@intel.com \
--to=lkp@intel.com \
--cc=david@redhat.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhkelley58@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wei.liu@kernel.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