search for: qiochannelfil

...; > > > Please look at include/io/channel.h. QEMU is event-driven and tends to > > use asynchronous I/O instead of spawning threads. The include/io/ APIs > > allow you to do asynchronous I/O in the event loop. > > That is true, except for I/O to/from plain files - the QIOChannelFile > impl doesn't do anything special (yet) to make that work correctly in > non-blocking mode. Of course that could be fixed... Yep, I don't know how I can use the QIOChannelFile for async IO. AFAICS it's just a wrapper for normal readv/writev. Who is responsible to do these IO w...

...; > > > Please look at include/io/channel.h. QEMU is event-driven and tends to > > use asynchronous I/O instead of spawning threads. The include/io/ APIs > > allow you to do asynchronous I/O in the event loop. > > That is true, except for I/O to/from plain files - the QIOChannelFile > impl doesn't do anything special (yet) to make that work correctly in > non-blocking mode. Of course that could be fixed... Yep, I don't know how I can use the QIOChannelFile for async IO. AFAICS it's just a wrapper for normal readv/writev. Who is responsible to do these IO w...

...ease look at include/io/channel.h. QEMU is event-driven and tends to > > > use asynchronous I/O instead of spawning threads. The include/io/ APIs > > > allow you to do asynchronous I/O in the event loop. > > > > That is true, except for I/O to/from plain files - the QIOChannelFile > > impl doesn't do anything special (yet) to make that work correctly in > > non-blocking mode. Of course that could be fixed... > > Yep, I don't know how I can use the QIOChannelFile for async IO. > AFAICS it's just a wrapper for normal readv/writev. Who is &gt...

On Thu, Jul 28, 2016 at 02:39:53PM +0900, Namhyung Kim wrote: > On Thu, Jul 28, 2016 at 03:02:54AM +0300, Michael S. Tsirkin wrote: > > On Thu, Jul 28, 2016 at 12:08:30AM +0900, Namhyung Kim wrote: > > > +static ssize_t virtio_pstore_do_write(VirtIOPstore *s, struct iovec *out_sg, > > > + unsigned int out_num, > > > +

On Thu, Jul 28, 2016 at 02:39:53PM +0900, Namhyung Kim wrote: > On Thu, Jul 28, 2016 at 03:02:54AM +0300, Michael S. Tsirkin wrote: > > On Thu, Jul 28, 2016 at 12:08:30AM +0900, Namhyung Kim wrote: > > > +static ssize_t virtio_pstore_do_write(VirtIOPstore *s, struct iovec *out_sg, > > > + unsigned int out_num, > > > +

...d a thread to do the work. > > Please look at include/io/channel.h. QEMU is event-driven and tends to > use asynchronous I/O instead of spawning threads. The include/io/ APIs > allow you to do asynchronous I/O in the event loop. That is true, except for I/O to/from plain files - the QIOChannelFile impl doesn't do anything special (yet) to make that work correctly in non-blocking mode. Of course that could be fixed... Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.or...

Hello, This is another iteration of the virtio-pstore work. I've addressed all comments from Daniel Berrange on the qemu side. * changes in v4) - use qio_channel_file_new_path() (Daniel) - rename to delete_old_pstore_file (Daniel) - convert G_REMOVE_SOURCE to FALSE (Daniel) * changes in v3) - use QIOChannel API (Stefan, Daniel) - add bound check for malcious guests

Hello, This is another iteration of the virtio-pstore work. I've addressed all comments from Daniel Berrange on the qemu side. * changes in v4) - use qio_channel_file_new_path() (Daniel) - rename to delete_old_pstore_file (Daniel) - convert G_REMOVE_SOURCE to FALSE (Daniel) * changes in v3) - use QIOChannel API (Stefan, Daniel) - add bound check for malcious guests