From: Dario Faggioli <dario.faggioli@citrix.com>
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>
Subject: Re: [PATCH RFC 1/2] tools/libxc: Improved xc_{topology, numa}info functions.
Date: Wed, 12 Mar 2014 09:34:07 +0100 [thread overview]
Message-ID: <1394613247.31942.45.camel@Abyss> (raw)
In-Reply-To: <1393499497-9162-2-git-send-email-andrew.cooper3@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1028 bytes --]
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.
>
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
--
<<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: 198 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-03-12 8:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 11:11 [PATCH RFC 0/2] Support for hwloc Andrew Cooper
2014-02-27 11:11 ` [PATCH RFC 1/2] tools/libxc: Improved xc_{topology, numa}info functions Andrew Cooper
2014-03-12 8:34 ` Dario Faggioli [this message]
2014-03-12 10:41 ` Andrew Cooper
2014-03-12 11:00 ` Dario Faggioli
2014-03-14 14:41 ` Ian Campbell
2014-02-27 11:11 ` [PATCH RFC 2/2] SYSCTL subop to execute cpuid on a specified pcpu Andrew Cooper
2014-02-27 11:11 ` [PATCH RFC 2/2] xen/x86: Introduce XEN_SYSCTL_cpuid hypercall Andrew Cooper
2014-02-27 11:58 ` Jan Beulich
2014-02-27 12:11 ` Andrew Cooper
2014-02-27 12:26 ` Jan Beulich
2014-02-27 15:57 ` Andrew Cooper
2014-03-14 14:45 ` 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=1394613247.31942.45.camel@Abyss \
--to=dario.faggioli@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).