From: Avi Kivity <avi@redhat.com>
To: Gregory Haskins <gregory.haskins@gmail.com>
Cc: pav <pav@aster.pl>, kvm@vger.kernel.org
Subject: Re: Qemu (host) <-> host userspace signaling?
Date: Mon, 01 Jun 2009 20:40:40 +0300 [thread overview]
Message-ID: <4A241298.3030201@redhat.com> (raw)
In-Reply-To: <4A240CBB.1090700@gmail.com>
Gregory Haskins wrote:
> Avi Kivity wrote:
>
>> pav wrote:
>>
>>> I understand I could use a unix socket and qemu_chr_open() and
>>> friends for this, but isn't a full-blown socket a bit of an overkill
>>> for a simple "kick" interface?
>>>
>>>
>> Not at all. Send a byte to have the other side wake up.
>>
> FWIW: you could also use an eventfd here.
>
To share the eventfd with someone else you need a unix domain socket
anyway. Once you do that setup, however, it works out quite nicely
(esp. if it's connected to iosignalfd).
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
prev parent reply other threads:[~2009-06-01 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-31 17:38 Qemu (host) <-> host userspace signaling? pav
2009-06-01 7:51 ` Avi Kivity
2009-06-01 17:15 ` Gregory Haskins
2009-06-01 17:40 ` Avi Kivity [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=4A241298.3030201@redhat.com \
--to=avi@redhat.com \
--cc=gregory.haskins@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=pav@aster.pl \
/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.