public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@openvz.org>
To: kbuild test robot <fengguang.wu@intel.com>,
	Andrey Smetanin <asmetanin@virtuozzo.com>
Cc: <kbuild-all@01.org>, Paolo Bonzini <pbonzini@redhat.com>,
	Roman Kagan <rkagan@virtuozzo.com>, <kvm@vger.kernel.org>
Subject: Re: [kvm:queue 27/38] arch/x86/kvm/hyperv.c:186:41: sparse: incorrect type in argument 2 (different modifiers)
Date: Fri, 18 Sep 2015 16:51:48 +0300	[thread overview]
Message-ID: <55FC16F4.7060407@openvz.org> (raw)
In-Reply-To: <201509182109.6ccgXDVp%fengguang.wu@intel.com>

On 09/18/2015 04:39 PM, kbuild test robot wrote:
> tree:   https://git.kernel.org/pub/scm/virt/kvm/kvm.git queue
> head:   ed393e4134de0dd02d8ba98ca8ce3ae65d1eb567
> commit: 46f4c309534b10ca1026273abe38955d3cff4023 [27/38] kvm/x86: Hyper-V HV_X64_MSR_VP_RUNTIME support
> reproduce:
>    # apt-get install sparse
>    git checkout 46f4c309534b10ca1026273abe38955d3cff4023
>    make ARCH=x86_64 allmodconfig
>    make C=1 CF=-D__CHECK_ENDIAN__
>
>
> sparse warnings: (new ones prefixed by >>)
>
>>> arch/x86/kvm/hyperv.c:186:41: sparse: incorrect type in argument 2 (different modifiers)
>     arch/x86/kvm/hyperv.c:186:41:    expected unsigned long [nocast] [usertype] *ut
>     arch/x86/kvm/hyperv.c:186:41:    got unsigned long *<noident>
>>> arch/x86/kvm/hyperv.c:186:41: sparse: implicit cast to nocast type
>>> arch/x86/kvm/hyperv.c:186:49: sparse: incorrect type in argument 3 (different modifiers)
>     arch/x86/kvm/hyperv.c:186:49:    expected unsigned long [nocast] [usertype] *st
>     arch/x86/kvm/hyperv.c:186:49:    got unsigned long *<noident>
>     arch/x86/kvm/hyperv.c:186:49: sparse: implicit cast to nocast type
>
> vim +186 arch/x86/kvm/hyperv.c
>
>     170				kvm_make_request(KVM_REQ_HV_RESET, vcpu);
>     171			}
>     172			break;
>     173		default:
>     174			vcpu_unimpl(vcpu, "Hyper-V uhandled wrmsr: 0x%x data 0x%llx\n",
>     175				    msr, data);
>     176			return 1;
>     177		}
>     178		return 0;
>     179	}
>     180	
>     181	/* Calculate cpu time spent by current task in 100ns units */
>     182	static u64 current_task_runtime_100ns(void)
>     183	{
>     184		cputime_t utime, stime;
>     185	
>   > 186		task_cputime_adjusted(current, &utime, &stime);
>     187		return div_u64(cputime_to_nsecs(utime + stime), 100);
>     188	}
>     189	
>     190	static int kvm_hv_set_msr(struct kvm_vcpu *vcpu, u32 msr, u64 data, bool host)
>     191	{
>     192		struct kvm_vcpu_hv *hv = &vcpu->arch.hyperv;
>     193	
>     194		switch (msr) {
>
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
can not get an idea what is this warning about...
For me it looks pretty lame.

Den

  reply	other threads:[~2015-09-18 13:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18 13:39 [kvm:queue 27/38] arch/x86/kvm/hyperv.c:186:41: sparse: incorrect type in argument 2 (different modifiers) kbuild test robot
2015-09-18 13:51 ` Denis V. Lunev [this message]
2015-09-18 13:55   ` Paolo Bonzini
2015-09-18 13:57     ` Denis V. Lunev
2015-09-18 14:40     ` Roman Kagan
2015-09-18 14:41       ` Paolo Bonzini
2015-09-18 15:06         ` [kbuild-all] " Fengguang Wu
2016-01-05 13:51           ` Luc Van Oostenryck

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=55FC16F4.7060407@openvz.org \
    --to=den@openvz.org \
    --cc=asmetanin@virtuozzo.com \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkagan@virtuozzo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox