From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Qemu (host) <-> host userspace signaling? Date: Mon, 01 Jun 2009 20:40:40 +0300 Message-ID: <4A241298.3030201@redhat.com> References: <4A23886C.7020809@redhat.com> <4A240CBB.1090700@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: pav , kvm@vger.kernel.org To: Gregory Haskins Return-path: Received: from mx2.redhat.com ([66.187.237.31]:48783 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751658AbZFARkg (ORCPT ); Mon, 1 Jun 2009 13:40:36 -0400 In-Reply-To: <4A240CBB.1090700@gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: 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.