From: Dongli Zhang <dongli.zhang@oracle.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Cc: jgross@suse.com, joao.m.martins@oracle.com
Subject: Re: [Xen-devel] [PATCH v6 1/1] xen/time: do not decrease steal time after live migration on xen
Date: Fri, 3 Nov 2017 07:50:31 +0800 [thread overview]
Message-ID: <d0c3eb70-5e49-27fb-8aae-3db266eb15a9@oracle.com> (raw)
In-Reply-To: <95598986-2888-2784-8737-0aaa6991c728@oracle.com>
Hi Boris,
On 11/03/2017 04:28 AM, Boris Ostrovsky wrote:
> On 11/01/2017 09:19 PM, Dongli Zhang wrote:
>> Hi Boris,
>>
>> I have received from lkp@intel.com that the prior version of patch hit issue
>> during compilation with aarch64-linux-gnu-gcc. I think this patch reviewed by
>> you would hit the same compiling issue on arm64 (there is no issue with x86_64).
>>
>> -------------------------------------------------------------
>>
>> 1st issue:
>>
>> Without including header <linux/slab.h> into driver/xen/time.c, compilation on
>> x86_64 works well (without any warning or error) but arm64 would hit the
>> following error:
>>
>> drivers/xen/time.c: In function ‘xen_manage_runstate_time’:
>> drivers/xen/time.c:94:20: error: implicit declaration of function
>> ‘kmalloc_array’ [-Werror=implicit-function-declaration]
>> runstate_delta = kmalloc_array(num_possible_cpus(),
>> ^
>>
>> drivers/xen/time.c:131:3: error: implicit declaration of function ‘kfree’
>> [-Werror=implicit-function-declaration]
>> kfree(runstate_delta);
>> ^
>> cc1: some warnings being treated as errors
>>
>> About the 1st issue, should I submit a new patch including <linux/slab.h> or
>> just a incremental based on previous patch merged into your own branch
>> /tree?
>>
>> -------------------------------------------------------------
>>
>> 2nd issue:
>>
>> aarch64-linux-gnu-gcc expects a cast for kmalloc_array(). Is this really
>> necessary as I did find people casting the return type of
>> kmalloc/kcalloc/kmalloc_array in linux source code (e.g.,
>> drivers/block/virtio_blk.c). Can we just ignore this warning?
>>
>> drivers/xen/time.c:94:18: warning: assignment makes pointer from integer without
>> a cast [-Wint-conversion]
>> runstate_delta = kmalloc_array(num_possible_cpus(),
>> ^
>> -------------------------------------------------------------
>
> That's because you need to declare kmalloc_array(), otherwise the
> compiler by default assumes that it returns an int. So including
> linux/slab.h should take care of both warnings.
>
> I can add it while committing.
Please help add it while committing. Thank you very much for your help!
>
>
> -boris
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
>
Dongli Zhang
next prev parent reply other threads:[~2017-11-02 23:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 1:46 Dongli Zhang
2017-11-01 19:19 ` Boris Ostrovsky
2017-11-02 1:19 ` Dongli Zhang
2017-11-02 20:28 ` Boris Ostrovsky
2017-11-02 23:50 ` Dongli Zhang [this message]
2017-11-08 21:17 ` Boris Ostrovsky
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=d0c3eb70-5e49-27fb-8aae-3db266eb15a9@oracle.com \
--to=dongli.zhang@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=joao.m.martins@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®