linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kys@linuxonhyperv.com
Cc: kbuild-all@01.org, x86@kernel.org, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
	olaf@aepfle.de, apw@canonical.com, jasowang@redhat.com,
	tglx@linutronix.de, hpa@zytor.com, sthemmin@microsoft.com,
	Michael.H.Kelley@microsoft.com, vkuznets@redhat.com,
	"K. Y. Srinivasan" <kys@microsoft.com>
Subject: Re: [PATCH V2 1/5] X86: Hyper-V: Enlighten APIC access
Date: Sat, 5 May 2018 07:36:23 +0800	[thread overview]
Message-ID: <201805050748.XqBLNZ7f%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180504060823.3345-1-kys@linuxonhyperv.com>

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

Hi Srinivasan,

I love your patch! Yet something to improve:

[auto build test ERROR on v4.17-rc3]
[also build test ERROR on next-20180504]
[cannot apply to tip/x86/core]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/kys-linuxonhyperv-com/X86-Hyper-V-APIC-enlightenments/20180505-045627
config: x86_64-randconfig-a0-05050447 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   arch/x86/hyperv/hv_apic.c: In function 'hv_apic_read':
>> arch/x86/hyperv/hv_apic.c:66:10: error: implicit declaration of function 'native_apic_mem_read'; did you mean 'hv_apic_icr_read'? [-Werror=implicit-function-declaration]
      return native_apic_mem_read(reg);
             ^~~~~~~~~~~~~~~~~~~~
             hv_apic_icr_read
   arch/x86/hyperv/hv_apic.c: In function 'hv_apic_write':
>> arch/x86/hyperv/hv_apic.c:80:3: error: implicit declaration of function 'native_apic_mem_write'; did you mean 'hv_apic_icr_write'? [-Werror=implicit-function-declaration]
      native_apic_mem_write(reg, val);
      ^~~~~~~~~~~~~~~~~~~~~
      hv_apic_icr_write
   arch/x86/hyperv/hv_apic.c: In function 'hv_apic_init':
>> arch/x86/hyperv/hv_apic.c:93:3: error: implicit declaration of function 'apic_set_eoi_write'; did you mean 'hv_apic_eoi_write'? [-Werror=implicit-function-declaration]
      apic_set_eoi_write(hv_apic_eoi_write);
      ^~~~~~~~~~~~~~~~~~
      hv_apic_eoi_write
   arch/x86/hyperv/hv_apic.c:94:3: error: 'apic' undeclared (first use in this function); did you mean 'pid'?
      apic->read      = hv_apic_read;
      ^~~~
      pid
   arch/x86/hyperv/hv_apic.c:94:3: note: each undeclared identifier is reported only once for each function it appears in
   cc1: some warnings being treated as errors

vim +66 arch/x86/hyperv/hv_apic.c

    52	
    53	static u32 hv_apic_read(u32 reg)
    54	{
    55		u32 reg_val, hi;
    56	
    57		switch (reg) {
    58		case APIC_EOI:
    59			rdmsr(HV_X64_MSR_EOI, reg_val, hi);
    60			return reg_val;
    61		case APIC_TASKPRI:
    62			rdmsr(HV_X64_MSR_TPR, reg_val, hi);
    63			return reg_val;
    64	
    65		default:
  > 66			return native_apic_mem_read(reg);
    67		}
    68	}
    69	
    70	static void hv_apic_write(u32 reg, u32 val)
    71	{
    72		switch (reg) {
    73		case APIC_EOI:
    74			wrmsr(HV_X64_MSR_EOI, val, 0);
    75			break;
    76		case APIC_TASKPRI:
    77			wrmsr(HV_X64_MSR_TPR, val, 0);
    78			break;
    79		default:
  > 80			native_apic_mem_write(reg, val);
    81		}
    82	}
    83	
    84	static void hv_apic_eoi_write(u32 reg, u32 val)
    85	{
    86		wrmsr(HV_X64_MSR_EOI, val, 0);
    87	}
    88	
    89	void __init hv_apic_init(void)
    90	{
    91		if (ms_hyperv.hints & HV_X64_APIC_ACCESS_RECOMMENDED) {
    92			pr_info("Hyper-V: Using MSR based APIC access\n");
  > 93			apic_set_eoi_write(hv_apic_eoi_write);
    94			apic->read      = hv_apic_read;
    95			apic->write     = hv_apic_write;
    96			apic->icr_write = hv_apic_icr_write;
    97			apic->icr_read  = hv_apic_icr_read;
    98		}
    99	}
   100	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

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

  parent reply	other threads:[~2018-05-04 23:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04  6:06 [PATCH V2 0/5] X86: Hyper-V: APIC enlightenments kys
2018-05-04  6:08 ` [PATCH V2 1/5] X86: Hyper-V: Enlighten APIC access kys
2018-05-04  6:08   ` [PATCH V2 2/5] X86: Hyper-V: Enable IPI enlightenments kys
2018-05-05  0:06     ` kbuild test robot
2018-05-09 17:06     ` Michael Kelley (EOSG)
2018-05-04  6:08   ` [PATCH V2 3/5] X86: Hyper-V: Enhanced IPI enlightenment kys
2018-05-09 17:07     ` Michael Kelley (EOSG)
2018-05-04  6:08   ` [PATCH V2 4/5] X86: Hyper-V: Consolidate code for converting cpumask to vpset kys
2018-05-09 17:07     ` Michael Kelley (EOSG)
2018-05-04  6:08   ` [PATCH V2 5/5] X86: Hyper-V: Consolidate the allocation of the hypercall input page kys
2018-05-09 17:08     ` Michael Kelley (EOSG)
2018-05-04 23:36   ` kbuild test robot [this message]
2018-05-09 17:05   ` [PATCH V2 1/5] X86: Hyper-V: Enlighten APIC access Michael Kelley (EOSG)
2018-05-16 17:21 ` [PATCH V2 0/5] X86: Hyper-V: APIC enlightenments KY Srinivasan
2018-05-16 20:14   ` Thomas Gleixner

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=201805050748.XqBLNZ7f%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=Michael.H.Kelley@microsoft.com \
    --cc=apw@canonical.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=jasowang@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=kys@linuxonhyperv.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@aepfle.de \
    --cc=sthemmin@microsoft.com \
    --cc=tglx@linutronix.de \
    --cc=vkuznets@redhat.com \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).