From: Wei Liu <Wei.Liu2@citrix.com>
To: 马磊 <aware.why@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
wei.liu2@citrix.com
Subject: Re: [BUG]: when using `xl restore`，xc_evtchn_alloc_unbound will raise this error
Date: Wed, 26 Dec 2012 19:33:12 +0000 [thread overview]
Message-ID: <20121226193312.GA28152@iceland> (raw)
In-Reply-To: <CA+ePHTAumsKKXNmcYEsY9OV5J3pyy7kygAktFEtjP84O9_ub0g@mail.gmail.com>
On Wed, Dec 26, 2012 at 02:45:46PM +0000, 马磊 wrote:
> I said `xl restore`, not `xm restore`, and the relevant code is in src/tools/libxl.
> It seems that yours aren't the same version as mine
I didn't say xm restore either. I was referring to the generic
save/restore functionality, though in fact I did use xl. And the
function I told you is in Xen hypervisor source code, not part of any
tool stack.
Whichever tools stack you use, it will eventually issue hypercall to Xen
via libxc. I don't use the same version as yours since I always plays
with xen staging unstable. However I don't think allocation code
has potential difference between 4.1.2 and staging unstable.
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-12-26 19:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-26 10:03 [BUG]: when using `xl restore`，xc_evtchn_alloc_unbound will raise this error 马磊
2012-12-26 10:19 ` 马磊
2012-12-26 13:41 ` Wei Liu
2012-12-26 14:45 ` 马磊
2012-12-26 19:33 ` Wei Liu [this message]
2012-12-27 2:12 ` 马磊
2012-12-27 12:41 ` Wei Liu
2012-12-28 3:13 ` 马磊
2012-12-28 10:46 ` Wei Liu
2012-12-31 3:10 ` 马磊
2012-12-31 12:03 ` Wei Liu
2013-01-04 3:23 ` 马磊
2013-01-04 6:27 ` 马磊
2013-01-04 9:20 ` Ian Campbell
2013-01-04 11:34 ` 马磊
2013-01-04 11:42 ` Ian Campbell
2013-01-05 4:03 ` 马磊
2013-01-05 6:44 ` 马磊
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=20121226193312.GA28152@iceland \
--to=wei.liu2@citrix.com \
--cc=aware.why@gmail.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 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).