On Wed, 3 Apr 2013 10:05:40 -0500
mdroth wrote:
> On Wed, Mar 27, 2013 at 09:17:30AM -0400, Luiz Capitulino wrote:
> > On Wed, 27 Mar 2013 10:10:42 +0100
> > Stefan Hajnoczi wrote:
> >
> > > There are several places where QEMU accidentally relies on the O_NONBLOCK
> > > state
> > > of passed f
On Wed, 3 Apr 2013 11:24:38 -0400
Luiz Capitulino wrote:
> On Wed, 3 Apr 2013 10:05:40 -0500
> mdroth wrote:
>
> > On Wed, Mar 27, 2013 at 09:17:30AM -0400, Luiz Capitulino wrote:
> > > On Wed, 27 Mar 2013 10:10:42 +0100
> > > Stefan Hajnoczi wrote:
> > >
> > > > There are several places wher
On Wed, Mar 27, 2013 at 09:17:30AM -0400, Luiz Capitulino wrote:
> On Wed, 27 Mar 2013 10:10:42 +0100
> Stefan Hajnoczi wrote:
>
> > There are several places where QEMU accidentally relies on the O_NONBLOCK
> > state
> > of passed file descriptors. Exposing O_NONBLOCK state makes it part of the
On Wed, 27 Mar 2013 10:10:42 +0100
Stefan Hajnoczi wrote:
> There are several places where QEMU accidentally relies on the O_NONBLOCK
> state
> of passed file descriptors. Exposing O_NONBLOCK state makes it part of the
> QMP
> API whenever getfd or fdset_add_fd are used!
>
> Whether or not QE
On 03/27/2013 03:10 AM, Stefan Hajnoczi wrote:
> There are several places where QEMU accidentally relies on the O_NONBLOCK
> state
> of passed file descriptors. Exposing O_NONBLOCK state makes it part of the
> QMP
> API whenever getfd or fdset_add_fd are used!
>
> Whether or not QEMU will use O
There are several places where QEMU accidentally relies on the O_NONBLOCK state
of passed file descriptors. Exposing O_NONBLOCK state makes it part of the QMP
API whenever getfd or fdset_add_fd are used!
Whether or not QEMU will use O_NONBLOCK is an implementation detail and should
be hidden from
