From: Wei Liu <wei.liu2@citrix.com>
To: Big Strong <fangtuo90@gmail.com>
Cc: Tamas Lengyel <tamas.k.lengyel@gmail.com>,
Wei Liu <wei.liu2@citrix.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: xc_altp2m_set_vcpu_enable_notify fail
Date: Fri, 6 May 2016 12:10:11 +0100 [thread overview]
Message-ID: <20160506111011.GH2111@citrix.com> (raw)
In-Reply-To: <CAFnE1f12rcLo0BcyB8ypX1iWFd1+Lx41vgj60HyBwkM_m9QN3g@mail.gmail.com>
On Wed, May 04, 2016 at 08:59:35PM +0800, Big Strong wrote:
[...]
>
>
> The code always stops at the xc_altp2m_set_vcpu_enable_notify, which is
> used to assign the new page as #VE info page. As I can't debug the Xen
> source code, I don't why xc_altp2m_set_vcpu_enable_notify always return -1.
> Any ideas?
libxc functions always return -1 when it fails. You need the specific
errno to know what went wrong.
I think it wouldn't be too hard to figure out which error code the
hypervisor returns and dig into the source code.
I don't have enough knowledge in altp2m. I'm afraid you need to either
dig into hypervisor code and read Intel manuals or wait for people who
are more familiar with the code to chime in.
Do you have any difficulty debugging Xen? We might be able to give some
pointers on how to do that.
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-06 11:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 8:36 xc_altp2m_set_vcpu_enable_notify fail Big Strong
2016-05-02 10:47 ` Wei Liu
2016-05-02 11:42 ` Big Strong
2016-05-04 10:43 ` Wei Liu
2016-05-04 10:48 ` Wei Liu
2016-05-04 12:59 ` Big Strong
2016-05-06 11:10 ` Wei Liu [this message]
2016-05-07 7:34 ` Big Strong
[not found] ` <CABfawhkfYqX6t2QFDfE=SF+xjBzqGtn7kvA0hfkDv841CarYBQ@mail.gmail.com>
2016-05-07 14:47 ` Tamas K Lengyel
2016-05-09 7:37 ` Big Strong
2016-05-09 8:59 ` Wei Liu
2016-05-09 15:30 ` Big Strong
2016-05-10 10:07 ` Wei Liu
2016-05-10 16:29 ` Big Strong
2016-05-11 3:37 ` Big Strong
2016-05-11 7:56 ` Big Strong
2016-05-11 15:37 ` Big Strong
2016-05-11 16:26 ` Sahita, Ravi
2016-05-12 13:00 ` Big Strong
2016-05-12 15:17 ` Wei Liu
2016-05-12 15:53 ` Tamas K Lengyel
2016-05-12 15:59 ` Sahita, Ravi
2016-05-16 9:06 ` Big Strong
2016-05-16 15:05 ` Big Strong
2016-05-17 12:05 ` Big Strong
2016-05-18 2:43 ` Big Strong
2016-05-18 4:56 ` Tamas K Lengyel
2016-05-18 9:48 ` Wei Liu
2016-05-18 13:14 ` Tamas K Lengyel
2016-05-18 13:22 ` Wei Liu
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=20160506111011.GH2111@citrix.com \
--to=wei.liu2@citrix.com \
--cc=fangtuo90@gmail.com \
--cc=tamas.k.lengyel@gmail.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 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.