From: sepanta s <sapanta992@gmail.com>
To: "xen-devel@lists.xen.org" <Xen-devel@lists.xen.org>
Subject: xen-access write protect Error
Date: Sat, 10 Sep 2016 15:16:32 +0430 [thread overview]
Message-ID: <CABaiLQ8a41kMjfnYLag1OQgmyXFE3J0tQsLwom5SGmWPkBkkBg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 530 bytes --]
Hi,
I am using xen-access to write protect a lot of gfns of the machine, and
listen to each gfn which is going to be written. For each gfn that is
accessed for write operation I create a thread to copy its content after a
short period of time.
I have got the following event as I create a thread for each gfn which is
being written by the user:
error: Could not obtain handle on privileged command interface : Too many
open files
What could cause this as my xen-access program crashes and Segmentation
fault (core dumped) occurs.
[-- Attachment #1.2: Type: text/html, Size: 618 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-09-10 10:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-10 10:46 sepanta s [this message]
2016-09-12 9:42 ` xen-access write protect Error Razvan Cojocaru
2016-09-14 9:02 ` sepanta s
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=CABaiLQ8a41kMjfnYLag1OQgmyXFE3J0tQsLwom5SGmWPkBkkBg@mail.gmail.com \
--to=sapanta992@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.