Re: [Qemu-devel] Do we need CONFIG_AIO?

[Stefano Stabellini <stefano.stabellini@eu.citrix.com>]

Anthony Liguori wrote:

> Stefano Stabellini wrote:
>> Christoph Hellwig wrote:
>>
>>   
>>> Currently all aio code in the raw-posix block driver depends on a
>>> CONFIG_AIO symbol that gets set based on the availability of the
>>> pthreads library.  Beeing able to rely on unconditional aio support
>>> means we could remove the whole code for plain bdrv_read/bdrv_write
>>> in raw-posix.c which is about 300 lines of code and a duplicated code
>>> path.  Is there any Posix-ish platform qemu supports that does not
>>> have pthreads support?
>>>
>>>     
>> MiniOS.
>> I would appreciate if you keep that flag.
>>   
> 
> Threads are not going to be able to remain an optional dependency 
> forever.  I would be willing to merge something to remove CONFIG_AIO 
> although I expect that there will be some fall out.  Some people are 
> using --disable-aio today for either historic reasons or because there 
> are weird bugs with AIO enabled.
> 

Obviously I would prefer if threads remained optional too, but let's
just focus on AIO for the moment: as Todd pointed out OpenBSD doesn't
currently provide AIO and also some small libc, like newlib, do not have
AIO either.