From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dario Faggioli <dario.faggioli@citrix.com>
Subject: Re: [PATCH RFC 1/2] tools/libxc: Improved xc_{topology,
 numa}info functions.
Date: Wed, 12 Mar 2014 09:34:07 +0100
Message-ID: <1394613247.31942.45.camel@Abyss>
References: <1393499497-9162-1-git-send-email-andrew.cooper3@citrix.com>
	<1393499497-9162-2-git-send-email-andrew.cooper3@citrix.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6038001513677179011=="
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <1393499497-9162-2-git-send-email-andrew.cooper3@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>, Ian Campbell <Ian.Campbell@citrix.com>, Xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

--===============6038001513677179011==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="=-7/q/0kmGAHqYjlRYJMj5"

--=-7/q/0kmGAHqYjlRYJMj5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, 2014-02-27 at 11:11 +0000, Andrew Cooper wrote:
> These two new functions provide a substantially easier-to-use API, where =
libxc
> itself takes care of all the appropriate bounce buffering.
>=20
So, because of the stalled discussion on patch 2 of this series, this
patch was hardly considered, I guess, is that so?

Personally, I think this is an improvement in its own right, and I'd
like to have it, independently from the CPUID stuff. Are you up,
perhaps, for submitting it as a separate patch?

One thing I'm not sure is why you're introducing new *_bounced variants,
rather than going ahead and modifying xc_topologyinfo() and
xc_numainfo()  directly. libxc is not an API we committed to keep
stable, is it?

Thanks and Regards,
Dario

--=20
<<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)


--=-7/q/0kmGAHqYjlRYJMj5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEABECAAYFAlMgHAwACgkQk4XaBE3IOsRjTACfZv0VxcUsvkddApgEVyBXvZ/6
p40Ani6wqy+fra7JSxs9HPSCnseztLd3
=1+l8
-----END PGP SIGNATURE-----

--=-7/q/0kmGAHqYjlRYJMj5--


--===============6038001513677179011==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

--===============6038001513677179011==--