From: Dario Faggioli <dario.faggioli@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com,
ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH for-xen-4.5] libxl: Allow copying smaller bitmap into a larger one
Date: Tue, 25 Nov 2014 10:42:58 +0100 [thread overview]
Message-ID: <1416908578.7176.10.camel@Abyss> (raw)
In-Reply-To: <54735343.1020208@oracle.com>
[-- Attachment #1.1: Type: text/plain, Size: 1237 bytes --]
On Mon, 2014-11-24 at 10:48 -0500, Boris Ostrovsky wrote:
> On 11/24/2014 05:47 AM, Wei Liu wrote:
> >>
> >> The partial copy function should explicitly zero-out all remaining bits.
>
> I actually thought that partial copy function should do just that ---
> copy bits that it has and leave others unchanged. The caller, if desires
> so, should have cleared the mask prior to the call. (This is for the
> case when destination is larger than source, of course).
>
Agreed.
Anyway, AFAIU Wei's proposal, he's saying that this new _copy_partial()
function can be an internal one, i.e., not part of the public API, or
am I wrong, Wei?
If yes, I agree with that.
This leaves the question of whether we should change the behavior of the
publicly exposed libxl_bitmap_copy(), which I'm still not sure about,
but I guess, if we keep this internal, we can defer thinking to that to
some other period not in between RCs?
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-11-25 9:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 21:27 [PATCH for-xen-4.5] libxl: Allow copying smaller bitmap into a larger one Boris Ostrovsky
2014-11-21 11:12 ` Wei Liu
2014-11-21 14:43 ` Boris Ostrovsky
2014-11-21 11:26 ` Dario Faggioli
2014-11-21 14:47 ` Boris Ostrovsky
2014-11-24 10:41 ` Wei Liu
2014-11-24 10:47 ` Wei Liu
2014-11-24 15:48 ` Boris Ostrovsky
2014-11-25 9:42 ` Dario Faggioli [this message]
2014-11-25 9:48 ` Wei Liu
2014-11-25 10:39 ` Wei Liu
2014-11-25 11:15 ` Wei Liu
2014-11-25 11:41 ` Dario Faggioli
2014-11-25 14:57 ` Boris Ostrovsky
2014-11-25 15:54 ` Konrad Rzeszutek Wilk
2014-11-28 12:10 ` Ian Campbell
2014-11-26 12:51 ` Ian Campbell
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=1416908578.7176.10.camel@Abyss \
--to=dario.faggioli@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 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.