qemu/qemu.git, branch stable-0.11

qcow2: Bring synchronous read/write back to life

2009-12-03T10:29:25+00:00

When the synchronous read and write functions were dropped, they were replaced by generic emulation functions. Unfortunately, these emulation functions don't provide the same semantics as the original functions did. The original bdrv_read would mean that we read some data synchronously and that we won't be interrupted during this read. The latter assumption is no longer true with the emulation function which needs to use qemu_aio_poll and therefore allows the callback of any other concurrent AIO request to be run during the read. Which in turn means that (meta)data read earlier could have changed and be invalid now. qcow2 is not prepared to work in this way and it's just scary how many places there are where other requests could run. I'm not sure yet where exactly it breaks, but you'll see breakage with virtio on qcow2 with a backing file. Providing synchronous functions again fixes the problem for me. Patchworks-ID: 35437 Signed-off-by: Kevin Wolf Signed-off-by: Anthony Liguori (cherry picked from commit ef845c3bf421290153154635dc18eaa677cecb43) Signed-off-by: Kevin Wolf Signed-off-by: Aurelien Jarno

Update version and changelog for 0.11.1 release

2009-12-02T20:27:02+00:00

Signed-off-by: Aurelien Jarno

fix I2C slave addressing

2009-12-02T16:24:48+00:00

With the recent device handling changes the I2C slave addressing code was broken. With current code, if a slave with the correct address is not found on the bus the last scanned slave on the bus will be addressed. This is wrong. Please find attached a patch to fix it. Signed-off-by: Juha Riihimäki Acked-by: Riku Voipio Signed-off-by: Aurelien Jarno

Revert "vga: do not resize the screen on hw_invalidate"

2009-11-27T17:46:04+00:00

This causes ctrl+alt+u or ctrl+alt+f to not work when windows hasn't been resized first. Other graphic emulators do resize the screen on hw_invalidate. This reverts commit 0bd8246bfec1dfb2eb959f52db535572c0260f4c.

slirp: fix use-after-free

2009-11-20T23:34:59+00:00

460fec67ee introduced a use-after free in slirp. Cc: Jan Kiszka Signed-off-by: Mark McLoughlin Signed-off-by: Aurelien Jarno

Fix sparc.ld

2009-11-19T00:22:47+00:00

Makes 91b40c5be84a478e98c0416325844a7f66d0efae unnecessary. Acked-by: Kirill A. Shutemov Signed-off-by: Blue Swirl

ELF codedump build failures

2009-11-18T14:30:23+00:00

Rename ELF coredump types to avoid conflict with the corresponding host types. Signed-off-by: Laurent Desnogues

kvm: Move KVM mp_state accessors to i386-specific code

2009-11-17T06:52:16+00:00

Unbreaks PowerPC and S390 KVM builds. Signed-off-by: Hollis Blanchard Signed-off-by: Anthony Liguori

this patch fixes a typo where armv4l was incorrectly spelled arm4l,

2009-11-17T06:30:09+00:00

preventing the correct handling of --cpu=armv4l. Laurent Signed-off-by: Laurent Desnogues Signed-off-by: Andrzej Zaborowski

net: disable draining tap queue in one go

2009-11-10T17:17:57+00:00

If qemu_send_packet_async() returns zero, it means the packet has been queued and the sent callback will be invoked once it has been flushed. This is only possible where the NIC's receive() handler returns zero and promises to notify the networking core that room is available in its queue again. In the case where the receive handler does not have this capability (and its queue fills up) it returns -1 and the networking core does not queue up the packet. This condition is indicated by a -1 return from qemu_send_packet_async(). Currently, tap handles this condition simply by dropping the packet. It should do its best to avoid getting into this situation by checking such NIC's have room for a packet before copying the packet from the tap interface. tap_send() used to achieve this by only reading a single packet before returning to the mainloop. That way, tap_can_send() is called before reading each packet. tap_send() was changed to completely drain the tap interface queue without taking into account the situation where the NIC returns an error and the packet is not queued. Let's start fixing this by reverting to the previous behaviour of reading one packet at a time. Reported-by: Scott Tsai Tested-by: Sven Rudolph Signed-off-by: Mark McLoughlin Signed-off-by: Aurelien Jarno