From: Zhigang Wang <zhigang.x.wang@oracle.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Juergen Gross <jgross@suse.com>, Wei Liu <wei.liu2@citrix.com>,
stefano.stabellini@eu.citrix.com,
Andrew Cooper <andrew.cooper3@citrix.com>,
ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] tools: remove unused wrappers for python
Date: Tue, 06 Oct 2015 11:30:32 -0400 [thread overview]
Message-ID: <5613E918.4020509@oracle.com> (raw)
In-Reply-To: <1444145211.5302.221.camel@citrix.com>
On 10/06/2015 11:26 AM, Ian Campbell wrote:
> On Tue, 2015-10-06 at 17:21 +0200, Juergen Gross wrote:
>> On 10/06/2015 05:11 PM, Ian Campbell wrote:
>>> On Tue, 2015-10-06 at 16:51 +0200, Juergen Gross wrote:
>>>> On 10/06/2015 03:40 PM, Ian Campbell wrote:
>>>>> On Tue, 2015-10-06 at 12:39 +0100, Wei Liu wrote:
>>>>>
>>>>>> And for the record, if my google-fu doesn't fail me, it's
>>>>>> possible to
>>>>>> load shared library into python interpreter using "dl" module in
>>>>>> 2.7
>>>>>> and
>>>>>> "ctypes" module in 3.x.
>>>>>
>>>>> Possible, but not especially convenient since you need to convert
>>>>> the C
>>>>> prototype manually, plus the result is not necessarily very
>>>>> "pythonic".
>>>>>
>>>>> I could totally see why people would prefer these bindings (or an
>>>>> argument
>>>>> for us providing a ctypes based wrapper).
>>>>
>>>> How often is such a debugging interface being used? Please consider
>>>> the amount of code (my patch removed nearly 3000 lines of code!) and
>>>> the availability of the xl wrapper.
>>>
>>> My understanding was that this was used by the "xen-bugtool" stuff in
>>> XenServer, so for actual functionality (gathering debug info) and not
>>> debugging (I supposed that the reference to being used for debugging was
>>> due to the name of the tool).
>>
>> And this functionality isn't available via the xl bindings?
>
> I don't know, we'll have to wait for those who are using it to chime in.
>
> Ian.
IanC: I remember you said xl bindings has some design issue and should not
be used. Is it still the case today?
Zhigang
next prev parent reply other threads:[~2015-10-06 15:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 10:46 [PATCH] tools: remove unused wrappers for python Juergen Gross
2015-10-06 11:18 ` Wei Liu
2015-10-06 11:33 ` Juergen Gross
2015-10-06 11:39 ` Wei Liu
2015-10-06 13:40 ` Ian Campbell
2015-10-06 14:51 ` Juergen Gross
2015-10-06 15:11 ` Ian Campbell
2015-10-06 15:21 ` Juergen Gross
2015-10-06 15:26 ` Ian Campbell
2015-10-06 15:30 ` Zhigang Wang [this message]
2015-10-06 15:45 ` Ian Campbell
2015-10-06 16:14 ` Juergen Gross
2015-10-06 16:24 ` Ian Campbell
2015-10-08 1:10 ` Konrad Rzeszutek Wilk
2015-10-08 4:16 ` Juergen Gross
2015-10-08 14:30 ` Ian Campbell
2015-10-06 15:38 ` Andrew Cooper
2015-10-06 16:31 ` Wei Liu
2015-10-06 16:38 ` Ian Campbell
2015-10-06 16:42 ` Wei Liu
2015-10-06 15:24 ` Zhigang Wang
2015-10-08 14:38 ` Ian Campbell
2015-10-08 15:09 ` Zhigang Wang
2015-10-08 15:27 ` Ian Campbell
2015-10-08 16:32 ` Zhigang Wang
2015-10-08 16:58 ` Wei Liu
2015-10-09 4:42 ` Juergen Gross
2015-10-09 9:43 ` Ian Campbell
2015-10-09 10:16 ` Juergen Gross
2015-10-09 13:29 ` Andrew Cooper
2015-10-07 2:58 ` Marek Marczykowski-Górecki
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=5613E918.4020509@oracle.com \
--to=zhigang.x.wang@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jgross@suse.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 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).