All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH V2 10/10] x86/Hyper-V: Workaround Hyper-V unballoon msg bug
Date: Thu, 09 Jan 2020 06:23:11 +0800	[thread overview]
Message-ID: <202001090612.M2ynTQuq%lkp@intel.com> (raw)
In-Reply-To: <20200107130950.2983-11-Tianyu.Lan@microsoft.com>

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

Hi,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on linus/master]
[also build test ERROR on v5.5-rc5 next-20200106]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/lantianyu1986-gmail-com/x86-Hyper-V-Add-Dynamic-memory-hot-remove-function/20200108-055844
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git ae6088216ce4b99b3a4aaaccd2eb2dd40d473d42
config: i386-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.5.0-3) 7.5.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   drivers/hv/hv_balloon.c: In function 'hot_remove_req':
   drivers/hv/hv_balloon.c:1481:3: error: implicit declaration of function 'hv_mem_hot_remove'; did you mean 'device_link_remove'? [-Werror=implicit-function-declaration]
      hv_mem_hot_remove(numa_node, page_count);
      ^~~~~~~~~~~~~~~~~
      device_link_remove
   drivers/hv/hv_balloon.c: In function 'balloon_down':
>> drivers/hv/hv_balloon.c:1842:5: error: implicit declaration of function 'process_hot_add'; did you mean '__check_hot_add'? [-Werror=implicit-function-declaration]
        process_hot_add(range_array[i].finfo.start_page,
        ^~~~~~~~~~~~~~~
        __check_hot_add
   cc1: some warnings being treated as errors

vim +1842 drivers/hv/hv_balloon.c

  1821	
  1822	static void balloon_down(union dm_msg_info *msg_info)
  1823	{
  1824		struct dm_unballoon_request *req = msg_info->unballoon_state.request;
  1825		union dm_mem_page_range *range_array = req->range_array;
  1826		struct hv_dynmem_device *dm = &dm_device;
  1827		unsigned int prev_pages_ballooned = dm->num_pages_ballooned;
  1828		int range_count = req->range_count;
  1829		struct dm_unballoon_response resp;
  1830		int i;
  1831	
  1832		for (i = 0; i < range_count; i++) {
  1833			/*
  1834			 * Hyper-V has a bug that send unballoon msg instead
  1835			 * of hot add msg even if there is no balloon msg sent
  1836			 * before. Treat all unballoon msgs as hot add msgs
  1837			 * if hot add capability is enabled.
  1838			 */
  1839			if (IS_ENABLED(CONFIG_MEMORY_HOTPLUG) && do_hot_add) {
  1840				dm->host_specified_ha_region = false;
  1841				dm->num_pages_added +=
> 1842					process_hot_add(range_array[i].finfo.start_page,
  1843					range_array[i].finfo.page_cnt, 0, 0);
  1844			} else {
  1845				free_balloon_pages(dm, &range_array[i]);
  1846				complete(&dm_device.config_event);
  1847			}
  1848		}
  1849	
  1850		if (!do_hot_add)
  1851			pr_debug("Freed %u ballooned pages.\n",
  1852				prev_pages_ballooned - dm->num_pages_ballooned);
  1853	
  1854		if (req->more_pages == 1)
  1855			return;
  1856	
  1857		memset(&resp, 0, sizeof(struct dm_unballoon_response));
  1858		resp.hdr.type = DM_UNBALLOON_RESPONSE;
  1859		resp.hdr.trans_id = atomic_inc_return(&trans_id);
  1860		resp.hdr.size = sizeof(struct dm_unballoon_response);
  1861	
  1862		vmbus_sendpacket(dm_device.dev->channel, &resp,
  1863					sizeof(struct dm_unballoon_response),
  1864					(unsigned long)NULL,
  1865					VM_PKT_DATA_INBAND, 0);
  1866	
  1867		dm->state = DM_INITIALIZED;
  1868	}
  1869	

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 70225 bytes --]

      reply	other threads:[~2020-01-08 22:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-07 13:09 [RFC PATCH V2 00/10] x86/Hyper-V: Add Dynamic memory hot-remove function lantianyu1986
2020-01-07 13:09 ` [RFC PATCH V2 1/10] mm/resource: Move child to new resource when release mem region lantianyu1986
2020-01-20 18:34   ` Michael Kelley
2020-01-20 19:20   ` Michael Kelley
2020-01-07 13:09 ` [RFC PATCH V2 2/10] mm: expose is_mem_section_removable() symbol lantianyu1986
2020-01-07 13:36   ` Michal Hocko
2020-01-10 13:41     ` David Hildenbrand
2020-01-13 14:49       ` [EXTERNAL] " Tianyu Lan
2020-01-13 15:01         ` David Hildenbrand
2020-01-14  9:50         ` Michal Hocko
2020-01-17 16:35           ` Tianyu Lan
2020-01-20 14:14             ` Michal Hocko
2020-01-07 13:09 ` [RFC PATCH V2 3/10] x86/Hyper-V/Balloon: Replace hot-add and balloon up works with a common work lantianyu1986
2020-01-20 19:12   ` Michael Kelley
2020-01-07 13:09 ` [RFC PATCH V2 4/10] x86/Hyper-V/Balloon: Convert spin lock ha_lock to mutex lantianyu1986
2020-01-07 13:09 ` [RFC PATCH V2 5/10] x86/Hyper-V/Balloon: Avoid releasing ha_lock when traverse ha_region_list lantianyu1986
2020-01-07 13:09 ` [RFC PATCH V2 6/10] x86/Hyper-V/Balloon: Enable mem hot-remove capability lantianyu1986
2020-01-07 13:09 ` [RFC PATCH V2 7/10] x86/Hyper-V/Balloon: Handle mem hot-remove request lantianyu1986
2020-01-08  9:54   ` kbuild test robot
2020-01-08 12:03   ` kbuild test robot
2020-01-07 13:09 ` [RFC PATCH V2 8/10] x86/Hyper-V/Balloon: Handle request with non-aligned page number lantianyu1986
2020-01-07 13:09 ` [RFC PATCH V2 9/10] x86/Hyper-V/Balloon: Hot add mem in the gaps of hot add region lantianyu1986
2020-01-07 13:09 ` [RFC PATCH V2 10/10] x86/Hyper-V: Workaround Hyper-V unballoon msg bug lantianyu1986
2020-01-08 22:23   ` kbuild test robot [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=202001090612.M2ynTQuq%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.