From: Hongkaixing <hongkaixing@huawei.com>
To: 'Olaf Hering' <olaf@aepfle.de>
Cc: bicky.shi@huawei.com, xiaowei.yang@huawei.com,
xen-devel@lists.xensource.com, yanqiangjun@huawei.com,
hanweidong@huawei.com
Subject: Re: [PATCH] xenpaging:close domU's event channel and free port
Date: Wed, 15 Feb 2012 10:33:25 +0800 [thread overview]
Message-ID: <003101cceb8a$318b9ff0$94a2dfd0$@com> (raw)
In-Reply-To: <20120214211905.GA23069@aepfle.de>
> -----Original Message-----
> From: Olaf Hering [mailto:olaf@aepfle.de]
> Sent: Wednesday, February 15, 2012 5:19 AM
> To: Hongkaixing
> Cc: xen-devel@lists.xensource.com; yanqiangjun@huawei.com; bicky.shi@huawei.com; xiaowei.yang@huawei.com;
> hanweidong@huawei.com
> Subject: Re: [PATCH] xenpaging:close domU's event channel and free port
>
> On Tue, Feb 14, Olaf Hering wrote:
>
> > xc: error: Error initialising shared page (28 = No space left on device): Internal error
>
> After reading the code more carefully I now see that mem_event_enable()
> calls alloc_unbound_xen_event_channel() and stores it into
> med->xen_port. As Tim suggested, your patch should use this value
> instead of relying on the shared_page pointer.
Thanks for your advices.
And In your another mail, you have mentioned the problem like this:
xc: detail: xenpaging init
xc: detail: watching '/local/domain/1/memory/target-tot_pages'
xc: error: Error initialising shared page (28 = No space left on device): Internal error
Yes, I am sure it is the error we have met before!
>
> Olaf
prev parent reply other threads:[~2012-02-15 2:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 8:53 [PATCH] xenpaging:close domU's event channel and free port hongkaixing
2012-02-10 16:22 ` Tim Deegan
2012-02-10 16:32 ` Andrew Cooper
2012-02-10 16:40 ` Olaf Hering
2012-02-13 5:47 ` Hongkaixing
2012-02-13 12:11 ` Ian Campbell
2012-02-15 2:24 ` Hongkaixing
2012-02-15 9:27 ` Ian Campbell
2012-02-17 6:21 ` Hongkaixing
2012-02-17 8:20 ` Ian Campbell
2012-02-17 10:28 ` Hongkaixing
2012-02-14 20:59 ` Olaf Hering
2012-02-14 21:19 ` Olaf Hering
2012-02-15 2:33 ` Hongkaixing [this message]
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='003101cceb8a$318b9ff0$94a2dfd0$@com' \
--to=hongkaixing@huawei.com \
--cc=bicky.shi@huawei.com \
--cc=hanweidong@huawei.com \
--cc=olaf@aepfle.de \
--cc=xen-devel@lists.xensource.com \
--cc=xiaowei.yang@huawei.com \
--cc=yanqiangjun@huawei.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).