From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Srujan D. Kotikela" <ksrujandas@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Handle for events?
Date: Wed, 29 Sep 2010 10:16:10 -0700 [thread overview]
Message-ID: <4CA3745A.10900@goop.org> (raw)
In-Reply-To: <AANLkTim2isZwXL=+xmHN5E66RZv+rtG+iSWGQb63XHyp@mail.gmail.com>
On 09/29/2010 09:34 AM, Srujan D. Kotikela wrote:
> Sorry,
>
> But from what I read I may not get notifications on /dev/xen/evtchn if
> my xen-evtchn module is not functioning. However if it is statically
> compiled it wont be found as a module. I can confirm it's working by
> checking if there are directories in my /proc/xen
>
> correct me if I am wrong.
/proc/xen is irrelevant to xen-evtchn; you would not expect to see any
changes in /proc/xen as a result of xen-evtchn being present or absent.
>
> I am calling notify() and I am getting a return value 0 but no
> notification mesages in /dev/xen/evtchn
You should look carefully at the existing examples of how to use that
device to see where you're going wrong.
J
next prev parent reply other threads:[~2010-09-29 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 4:46 Handle for events? Srujan D. Kotikela
2010-09-29 16:08 ` Jeremy Fitzhardinge
2010-09-29 16:27 ` Srujan D. Kotikela
2010-09-29 16:29 ` Jeremy Fitzhardinge
2010-09-29 16:34 ` Srujan D. Kotikela
2010-09-29 17:16 ` Jeremy Fitzhardinge [this message]
[not found] ` <AANLkTimqZS_5+rjO5uv9ZBnTKM9feAnupe9KbhZkrug5@mail.gmail.com>
2010-10-08 16:11 ` Srujan D. Kotikela
[not found] ` <4CB4A18F.3040203@goop.org>
2010-10-27 3:19 ` Srujan D. Kotikela
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=4CA3745A.10900@goop.org \
--to=jeremy@goop.org \
--cc=ksrujandas@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 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.