Ryan Harper wrote: >> So what happens if !defined(CONFIG_AIO)? By my reading of the code, >> aio_drv will be NULL and this will SEGV. > > raw_aio_read/write/cancel aren't included in the bdrv structure unless > CONFIG_AIO is defined. Rather in bdrv_register, the aio emulation > functions are used instead.
How about providing a aio interface implementation which simply uses read/write syscalls (thereby not being really async obviously)? Then use that as fallback instead of aio emulation? And also drop CONFIG_AIO then? cheers, Gerd -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
