From: Big Strong <fangtuo90@gmail.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Tamas K Lengyel <tamas.k.lengyel@gmail.com>,
"Sahita, Ravi" <ravi.sahita@intel.com>,
Ian Campbell <ian.campbell@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: xc_altp2m_set_vcpu_enable_notify fail
Date: Mon, 9 May 2016 23:30:34 +0800 [thread overview]
Message-ID: <CAFnE1f3ga2H6exJS0uhxQ7vgNv2E41qWQm3C2JBgkBTCiOyXDg@mail.gmail.com> (raw)
In-Reply-To: <20160509085949.GP2111@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1360 bytes --]
>
> You need to have appropriate log level set.
>
> Try adding loglvl=all guest_loglvl=all to your xen command line and
> reboot.
>
> Wei.
>
I've enabled all the log level just as you said, but no outputs happen at
HVMOP_altp2m_vcpu_enable_notify section of do_altp2m_op function, so does
that means the function are not called at all?
case HVMOP_altp2m_vcpu_enable_notify:
> {
> struct vcpu *curr = current;
> p2m_type_t p2mt;
> if ( a.u.enable_notify.pad || a.domain != DOMID_SELF ||
> a.u.enable_notify.vcpu_id != curr->vcpu_id )
> {
> rc = -EINVAL;
>
> * gdprintk(XENLOG_INFO, "enable_notify args error pad:%d domain:%d vcpu:%d
> curr->vcpu:%d\n",** a.u.enable_notify.pad, a.domain,
> a.u.enable_notify.vcpu_id, curr->vcpu_id);*
> }
> if ( (gfn_x(vcpu_altp2m(curr).veinfo_gfn) != INVALID_GFN) ||
> (mfn_x(get_gfn_query_unlocked(curr->domain,
> a.u.enable_notify.gfn, &p2mt)) == INVALID_MFN) )
> {
> return -EINVAL;
> * gdprintk(XENLOG_INFO, "veinfo page is invalid\n");*
> }
> vcpu_altp2m(curr).veinfo_gfn = _gfn(a.u.enable_notify.gfn);
> altp2m_vcpu_update_vmfunc_ve(curr);
> *gdprintk(XENLOG_INFO, "veinfo page set successfully\n");*
> break;
> }
[-- Attachment #1.2: Type: text/html, Size: 3302 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:[~2016-05-09 15:30 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
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 [this message]
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=CAFnE1f3ga2H6exJS0uhxQ7vgNv2E41qWQm3C2JBgkBTCiOyXDg@mail.gmail.com \
--to=fangtuo90@gmail.com \
--cc=ian.campbell@citrix.com \
--cc=ravi.sahita@intel.com \
--cc=tamas.k.lengyel@gmail.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).