On Fri, Nov 28, 2014 at 01:19:59PM +0100, Kevin Wolf wrote:
> Am 28.11.2014 um 12:49 hat Stefan Hajnoczi geschrieben:
> > On Wed, Nov 26, 2014 at 03:46:42PM +0100, Kevin Wolf wrote:
> > > +while (data.n > 0) {
> > > +main_loop_wait(false);
> > > +}
> >
> > Why is this false (non-bl
Am 28.11.2014 um 12:49 hat Stefan Hajnoczi geschrieben:
> On Wed, Nov 26, 2014 at 03:46:42PM +0100, Kevin Wolf wrote:
> > +while (data.n > 0) {
> > +main_loop_wait(false);
> > +}
>
> Why is this false (non-blocking)? This is why you get the main loop
> spun warning message.
>
> U
On Wed, Nov 26, 2014 at 03:46:42PM +0100, Kevin Wolf wrote:
> +while (data.n > 0) {
> +main_loop_wait(false);
> +}
Why is this false (non-blocking)? This is why you get the main loop
spun warning message.
Using true (blocking) seems like the right thing. data.n changes as
part o
This adds a qemu-img command that allows doing some simple benchmarks
for the block layer without involving guest devices and a real VM.
For the start, this implements only a test of sequential reads.
Signed-off-by: Kevin Wolf
---
qemu-img-cmds.hx | 6 ++
qemu-img.c | 174 ++
