From: David Vrabel <david.vrabel@citrix.com>
To: "amin.fallahi@gmail.com" <amin.fallahi@gmail.com>,
xen-devel@lists.xen.org
Subject: Re: Understanding Xen event channel bit operation
Date: Mon, 26 Oct 2015 10:50:29 +0000 [thread overview]
Message-ID: <562E0575.2020802@citrix.com> (raw)
In-Reply-To: <CAF-KA8-gHai2A1Mzxpd_vnSHqmzWV11qYKsCa9Kxc=kGRwsqbw@mail.gmail.com>
On 25/10/15 09:25, amin.fallahi@gmail.com wrote:
> Hi everybody
> I need to understand when these pending and mask bits are set and
> cleared. It seems pending bits are set by evtchn_set_pending method in
> event_channel.c but I don't understand where pending bit is cleared by
> the guest and where mask bit is set and reset?
The mask and pending bits are in memory shared with the guest and the
guest (mostly) modifies these bits by writing directly to the shared memory.
You need to look at the guest kernel (e.g.,
drivers/xen/events/events_base.c in Linux).
David
prev parent reply other threads:[~2015-10-26 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 9:25 Understanding Xen event channel bit operation amin.fallahi
2015-10-26 10:50 ` David Vrabel [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=562E0575.2020802@citrix.com \
--to=david.vrabel@citrix.com \
--cc=amin.fallahi@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 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).