From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lrwgz-0003SJ-H5 for qemu-devel@nongnu.org; Thu, 09 Apr 2009 12:01:29 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lrwgu-0003Qb-Mb for qemu-devel@nongnu.org; Thu, 09 Apr 2009 12:01:28 -0400 Received: from [199.232.76.173] (port=44405 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lrwgt-0003QM-UW for qemu-devel@nongnu.org; Thu, 09 Apr 2009 12:01:24 -0400 Received: from mail2.shareable.org ([80.68.89.115]:50694) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Lrwgt-0004UF-4P for qemu-devel@nongnu.org; Thu, 09 Apr 2009 12:01:23 -0400 Date: Thu, 9 Apr 2009 17:01:19 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] [PATCH 1/6] Allow multiple monitor devices (v2) Message-ID: <20090409160119.GB14196@shareable.org> References: <49DDF807.1050707@us.ibm.com> <49DDFAD5.7060808@redhat.com> <49DDFC5C.4080504@us.ibm.com> <49DE0042.9050103@redhat.com> <49DE0271.8090103@us.ibm.com> <49DE05F2.5060304@redhat.com> <49DE0673.3070501@us.ibm.com> <49DE081D.1030702@redhat.com> <49DE0CF2.3060307@us.ibm.com> <49DE1029.3030909@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49DE1029.3030909@redhat.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: libvir-list@redhat.com, Anthony Liguori , Jan Kiszka , Hollis Blanchard Avi Kivity wrote: > >I think the thing that is missing is that the 'wait' command does not > >have to be part of the non-human mode. In non-human mode, you are > >always doing an implicit wait. > > I think 'wait' is unusable for humans. If I want qemu to tell me > something happened, it's enough to enable notifications. There's no > need to tell it to wait every time something happens. That's poll(2), > there's no poll(1). For some purposes I'd prefer 'wait' on a separate monitor. For the same reason that we sometimes redirect the output of background shell commands to a file :-) Solution: 'wait -background' for those async notifications. Or simply 'notify -background event-type', no need for a wait command if you give that option. Or conversely 'notify -channel 1 event-type' to direct the events to channel 1, and 'wait -channel 1' to show events on that channel. -- Jamie