From: "Denis V. Lunev" <den@openvz.org>
To: Paolo Bonzini <pbonzini@redhat.com>,
kbuild test robot <fengguang.wu@intel.com>,
Andrey Smetanin <asmetanin@virtuozzo.com>
Cc: <kbuild-all@01.org>, 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:57:39 +0300 [thread overview]
Message-ID: <55FC1853.6090308@openvz.org> (raw)
In-Reply-To: <55FC17B4.9060702@redhat.com>
On 09/18/2015 04:55 PM, Paolo Bonzini wrote:
>
> On 18/09/2015 15:51, Denis V. Lunev wrote:
>>> 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.
> I think it wants you to do
>
> - return div_u64(cputime_to_nsecs(utime + stime), 100);
> + return div_u64(cputime_to_nsecs(utime) +
> + cputime_to_nsecs(stime), 100);
>
> Paolo
ok, I'll check but warning points here
> 186 task_cputime_adjusted(current, &utime, &stime);
and says about parameters 2 and 3. There is no parameter 3
in div_u64 call :)
next prev parent reply other threads:[~2015-09-18 13:57 UTC|newest]
Thread overview: 14+ 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
2015-09-18 13:55 ` Paolo Bonzini
2015-09-18 13:57 ` Denis V. Lunev [this message]
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
2016-01-05 16:25 ` [PATCH] Do not drop 'nocast' modifier when taking the address Luc Van Oostenryck
2016-02-02 20:25 ` Christopher Li
2016-02-03 3:43 ` Luc Van Oostenryck
2016-02-03 4:09 ` Christopher Li
2016-02-03 9:15 ` Luc Van Oostenryck
2016-02-22 18:41 ` Christopher Li
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=55FC1853.6090308@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 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.