From: Yang Hongyang <yanghy@cn.fujitsu.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: wei.liu2@citrix.com, eddie.dong@intel.com, wency@cn.fujitsu.com,
Andrew Cooper <andrew.cooper3@citrix.com>,
yunhong.jiang@intel.com, ian.jackson@eu.citrix.com,
xen-devel@lists.xen.org, rshriram@cs.ubc.ca
Subject: Re: [PATCH Remus v2 02/10] tools/libxc: introduce setup() and cleanup() on save
Date: Tue, 12 May 2015 15:04:36 +0800 [thread overview]
Message-ID: <5551A604.4060103@cn.fujitsu.com> (raw)
In-Reply-To: <1431344973.8263.35.camel@citrix.com>
On 05/11/2015 07:49 PM, Ian Campbell wrote:
> On Mon, 2015-05-11 at 12:47 +0100, Ian Campbell wrote:
>>>>> Actually this is another trick that I need to deal with those
>>>>> hypercall macros.
>>>>> DECLARE_HYPERCALL_BUFFER_SHADOW will define a user pointer "dirty_bitmap"
>>>>> and a shadow buffer, although xc_hypercall_buffer_free_pages takes
>>>>> "dirty_bitmap" as an augument, but it is also a MACRO, without
>>>>> "if ( dirty_bitmap )", the compiler will report "dirty_bitmap" unused
>>>>> error...
>>>>
>>>> Ah, in which case you would be better using
>>>> xc__hypercall_buffer_free_pages() and not creating the local shadow in
>>>> the first place.
>>>
>>> I thought we'd better use those MACROs which described in the comments...
>>> If it is OK to use xc__hypercall_buffer_free_pages(), I will fix it in
>>> the next version.
>>
>> If anything I think I'd prefer for the if to move inside the
>> xc_hypercall_buffer_free_pages macro.
>
> Or if you want to use the "raw" xc__hypercall_buffer variant you should
> be consistent and do the same on allocation.
I think I will add a patch that move the if inside the
xc_hypercall_buffer_free_pages macro.
>
> Ian.
>
>
> .
>
--
Thanks,
Yang.
next prev parent reply other threads:[~2015-05-12 7:04 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 9:33 [PATCH Remus v2 00/10] Remus support for Migration-v2 Yang Hongyang
2015-05-08 9:33 ` [PATCH Remus v2 01/10] tools/libxc: adjust the memory allocation for migration Yang Hongyang
2015-05-08 9:51 ` Andrew Cooper
2015-05-11 11:50 ` Ian Campbell
2015-05-12 6:43 ` Hongyang Yang
2015-05-08 9:33 ` [PATCH Remus v2 02/10] tools/libxc: introduce setup() and cleanup() on save Yang Hongyang
2015-05-08 9:45 ` Andrew Cooper
2015-05-08 9:59 ` Hongyang Yang
2015-05-08 10:08 ` Andrew Cooper
2015-05-11 1:20 ` Hongyang Yang
2015-05-11 11:47 ` Ian Campbell
2015-05-11 11:49 ` Ian Campbell
2015-05-12 7:04 ` Yang Hongyang [this message]
2015-05-08 9:33 ` [PATCH Remus v2 03/10] tools/libxc: rename send_some_pages to send_dirty_pages Yang Hongyang
2015-05-08 10:11 ` Andrew Cooper
2015-05-11 1:21 ` Hongyang Yang
2015-05-08 9:33 ` [PATCH Remus v2 04/10] tools/libxc: introduce DECLARE_HYPERCALL_BUFFER_USER_POINTER Yang Hongyang
2015-05-08 10:16 ` Andrew Cooper
2015-05-11 1:22 ` Hongyang Yang
2015-05-11 11:53 ` Ian Campbell
2015-05-12 7:18 ` Yang Hongyang
2015-05-12 8:19 ` Ian Campbell
2015-05-12 9:24 ` Yang Hongyang
2015-05-12 9:43 ` Ian Campbell
2015-05-12 9:48 ` Yang Hongyang
2015-05-08 9:33 ` [PATCH Remus v2 05/10] tools/libxc: reuse send_dirty_pages() in send_all_pages() Yang Hongyang
2015-05-08 10:17 ` Andrew Cooper
2015-05-08 9:33 ` [PATCH Remus v2 06/10] tools/libxc: introduce process_record() Yang Hongyang
2015-05-08 9:33 ` [PATCH Remus v2 07/10] tools/libxc: split read/handle qemu info Yang Hongyang
2015-05-08 9:33 ` [PATCH Remus v2 08/10] tools/libxc: implement Remus checkpointed save Yang Hongyang
2015-05-08 9:33 ` [PATCH Remus v2 09/10] tools/libxc: implement Remus checkpointed restore Yang Hongyang
2015-05-08 9:33 ` [PATCH Remus v2 10/10] tools/libxc: X86_PV_INFO can be sent multiple times under Remus Yang Hongyang
2015-05-08 18:12 ` [PATCH Remus v2 00/10] Remus support for Migration-v2 Andrew Cooper
2015-05-11 6:28 ` Hongyang Yang
2015-05-11 9:00 ` Andrew Cooper
2015-05-11 10:48 ` Hongyang Yang
2015-05-11 11:01 ` Andrew Cooper
2015-05-12 8:12 ` Yang Hongyang
2015-05-12 9:40 ` Andrew Cooper
2015-05-12 10:02 ` Yang Hongyang
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=5551A604.4060103@cn.fujitsu.com \
--to=yanghy@cn.fujitsu.com \
--cc=andrew.cooper3@citrix.com \
--cc=eddie.dong@intel.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=rshriram@cs.ubc.ca \
--cc=wei.liu2@citrix.com \
--cc=wency@cn.fujitsu.com \
--cc=xen-devel@lists.xen.org \
--cc=yunhong.jiang@intel.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.