All of lore.kernel.org
 help / color / mirror / Atom feed
From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Can I xc_await_suspend() for a suspend event caused by another application?
Date: Fri, 24 Jul 2015 15:08:12 +0300	[thread overview]
Message-ID: <55B22AAC.5080808@bitdefender.com> (raw)

Hello,

I've noticed that the xc_suspend_evtchn_init() functions in xenguest.h
connect the client application to a guest suspend event channel, and
that it's possible to subscribe to these events, in theory even if you
never signal the channel (i.e. even if you don't issue a suspend request).

But all the in-tree examples I've read seem to first signal the channel
and then wait on the same channel for the confirmation that the guest is
suspending.

Can the event channel be used solely to inform a monitoring application
that _another_ application (for example, xl) has requested a suspend?

To give you some context, I'm interested in being able to make the
difference between the case when a guest is going into suspend mode (and
is still running), and the case when a guest is history (which I'm now
doing via @releaseDomain xenstore events). Basically, the difference
between a regular guest shutdown and what happens on "xl save" (as early
as possible, while the guest is still running).


Thanks,
Razvan

             reply	other threads:[~2015-07-24 12:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24 12:08 Razvan Cojocaru [this message]
2015-08-10  9:28 ` Can I xc_await_suspend() for a suspend event caused by another application? Razvan Cojocaru
2015-08-10  9:52   ` Andrew Cooper
2015-08-10 10:03     ` Razvan Cojocaru

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=55B22AAC.5080808@bitdefender.com \
    --to=rcojocaru@bitdefender.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.