qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 2/3] Always use nonblocking mode for qemu_chr_op


From: Daniel P. Berrange
Subject: Re: [Qemu-devel] [PATCH 2/3] Always use nonblocking mode for qemu_chr_open_fd.
Date: Thu, 24 Jul 2008 09:35:53 +0100
User-agent: Mutt/1.4.1i

On Wed, Jul 23, 2008 at 11:31:42AM -0500, Anthony Liguori wrote:
> Gerd Hoffmann wrote:
> >Anthony Liguori wrote:
> >  
> >>Gerd Hoffmann wrote:
> >>    
> >>>Comments on this one?
> >>>      
> >>Checking every 100ms for every pty device really makes me cringe.
> >>    
> >
> >Only when unconnected, and the interval can be changed.
> >And I'm certainly open for better ideas ...
> >  
> 
> I don't have one.  In xenconsoled, once a pty disconnected, it creates a 
> new pty specifically because I don't think there's any sane way to 
> detect reconnection.

The only guarenteed reliable way I know of is using epoll(), but as I
mentioned before that's Linux specific, so not immediately useful unless
we're willing to drop in an alternate epoll() based main loop for Linux
only, and say other OS have to use PTYs in blocking mode.

Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|




reply via email to

[Prev in Thread] Current Thread [Next in Thread]