From: Yang Hongyang <yanghy@cn.fujitsu.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Eric Chanudet <eric.chanudet@citrix.com>,
xen-devel@lists.xensource.com,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: libxenlight and xl: missing features
Date: Fri, 14 May 2010 11:55:56 +0800 [thread overview]
Message-ID: <4BECC9CC.9080209@cn.fujitsu.com> (raw)
In-Reply-To: <d3bcc344-1b25-424c-ade7-1f9a4cc11e18@default>
Hi Dan,
On 05/13/2010 09:47 PM, Dan Magenheimer wrote:
> As I have not yet found the time to add the tmem-* commands
> to xl, and since others are actively reimplementing all of
> the xm commands, I would be grateful if someone would
> add in the tmem commands to xl as well. If there are any
> difficulties or questions, I would be happy to help.
Yu and Me will try to do that. It may take some time for
us to accomplish those tmem-* commands and may ask for your
help when met difficulties.
>
> Thanks in advance,
> Dan
>
>> -----Original Message-----
>> From: Stefano Stabellini [mailto:stefano.stabellini@eu.citrix.com]
>> Sent: Friday, April 23, 2010 5:06 AM
>> To: Dan Magenheimer
>> Cc: Stefano Stabellini; xen-devel@lists.xensource.com
>> Subject: RE: [Xen-devel] libxenlight and xl: missing features
>>
>> On Thu, 22 Apr 2010, Dan Magenheimer wrote:
>>> I'll try to do the tmem-* commands after Xen Summit.
>>
>> Thanks, that would be appreciated :)
>>
>
>
--
Regards
Yang Hongyang
next prev parent reply other threads:[~2010-05-14 3:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 16:44 libxenlight and xl: missing features Stefano Stabellini
2010-04-22 19:36 ` Dan Magenheimer
2010-04-23 11:06 ` Stefano Stabellini
2010-05-13 13:47 ` Dan Magenheimer
2010-05-14 3:55 ` Yang Hongyang [this message]
2010-04-30 2:26 ` Yu Zhiguo
2010-04-30 6:38 ` Stefano Stabellini
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=4BECC9CC.9080209@cn.fujitsu.com \
--to=yanghy@cn.fujitsu.com \
--cc=dan.magenheimer@oracle.com \
--cc=eric.chanudet@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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.