[Top][All Lists]

[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: Wed, 23 Jul 2008 16:31:33 +0100
User-agent: Mutt/1.4.1i

On Wed, Jul 23, 2008 at 10:24:58AM -0500, Anthony Liguori wrote:
> Gerd Hoffmann wrote:
> >  
> >>Which means we need our own code for ptys and can't use the generic fd
> >>functions.  I'll go trying cooking up a patch ...
> >
> >Comments on this one?
> >  
> Checking every 100ms for every pty device really makes me cringe.
> Why is libvirt using ptys in the first place?  Why not use unix 
> sockets?  They don't have these problems with state tracking.

The application using libvirt chooses to use PTYs - we're merely
exposing the capability. The virt-console program for interacting
with serial ports uses PTYs because its a configuration that historically
works with both Xen and KVM. It could equally use UNIX sockets, but it'd
still be desirable for PTYs to work better

|: 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]