Re: [Qemu-devel] [RFC qemu 0/4] A PV solution for live migration optimization

On Wed, Mar 09, 2016 at 02:38:52PM -0500, Rik van Riel wrote: > On Wed, 2016-03-09 at 20:04 +0300, Roman Kagan wrote: > > On Wed, Mar 09, 2016 at 05:41:39PM +0200, Michael S. Tsirkin wrote: > > > On Wed, Mar 09, 2016 at 05:28:54PM +0300, Roman Kagan wrote: > > > > For (1) I've been trying to make

Re: [Qemu-devel] [PATCH] usb: fix unbounded stack warning for xhci_dma_write_u32s

On Do, 2016-03-10 at 15:56 +0800, Peter Xu wrote: > On Thu, Mar 10, 2016 at 08:34:13AM +0100, Gerd Hoffmann wrote: > > On Do, 2016-03-10 at 10:11 +0800, Peter Xu wrote: > > > Signed-off-by: Peter Xu > > > --- > > > hw/usb/hcd-xhci.c | 6 -- > > > 1 file changed, 4

Re: [Qemu-devel] [PATCH v3 3/5] replay: introduce new checkpoint for icount warp

> From: Paolo Bonzini [mailto:pbonz...@redhat.com] > On 01/03/2016 12:07, Pavel Dovgalyuk wrote: > > qemu_clock_warp function is called to update virtual clock when CPU > > is sleeping. This function includes replay checkpoint to make execution > > deterministic in icount mode. > > Record/replay

Re: [Qemu-devel] [PATCH] hw/9pfs: Add CephFS support in VirtFS

On Wed, 9 Mar 2016 13:09:58 -0700 Eric Blake wrote: > On 03/09/2016 12:02 PM, Greg Kurz wrote: > > On Wed, 2 Mar 2016 23:41:43 +0800 > > Jevon Qiao wrote: > > > > >> +} > >> + > >> +static int cephfs_readdir_r(FsContext *ctx, V9fsFidOpenState *fs, >

Re: [Qemu-devel] [PATCH RFC 0/2] Versioning ARM virt machine types

On 24 February 2016 at 02:09, Andrew Jones wrote: > I believe our downstream versioning has driven some changes to libvirt > already, so I think it's a good time to bring the how to best version > mach-virt discussions to all the respective upstreams, despite it > currently,

Re: [Qemu-devel] [PATCH 5/8] virtio-blk: fix "disabled data plane" mode

On 03/10/2016 02:51 AM, Fam Zheng wrote: [...] > The aio_poll() inside "blk_set_aio_context(s->conf->conf.blk, s->ctx)" looks > suspicious: > >main thread iothread > >

Re: [Qemu-devel] [PATCH v1] migration: skip sending ram pages released by virtio-balloon driver.

On 3/7/2016 10:35 PM, Eric Blake wrote: > On 03/04/2016 02:02 AM, Jitendra Kolhe wrote: >> While measuring live migration performance for qemu/kvm guest, it >> was observed that the qemu doesn’t maintain any intelligence for the >> guest ram pages which are release by the guest balloon driver and

Re: [Qemu-devel] [PATCH v1 21/21] error: ensure errno detail is printed with error_abort

"Daniel P. Berrange" writes: > When _abort is passed in, the error reporting code > will print the current error message and then abort() the > process. Unfortunately at the time it aborts, we've not > yet appended the errno detail. This makes debugging certain > problems

Re: [Qemu-devel] [PATCHv10 10/11] qapi-schema, qemu-options & slirp: Adding Qemu options for IPv6 addresses

On 08.03.2016 11:34, Samuel Thibault wrote: > From: Yann Bordenave > > This patch adds parameters to manage some new options in the qemu -net > command. > Slirp IPv6 address, network prefix, and DNS IPv6 address can be given in > argument to the qemu command. > Defaults

Re: [Qemu-devel] why restrict pull reqs to signed tags?

David Woodhouse writes: > On Wed, 2016-03-09 at 15:41 +0100, Laszlo Ersek wrote: >> According to your description, QEMU uses git improperly, so does >> libvirt, and the KVM (kernel) queue too. > > Let's see... > > Imagine I'm working on a new feature, and I submit a

Re: [Qemu-devel] [RFC qemu 0/4] A PV solution for live migration optimization

> > Could provide more information on how to use virtio-serial to exchange > data? Thread , Wiki or code are all OK. > > I have not find some useful information yet. > > See this commit in the Linux sources: > > 108fc82596e3b66b819df9d28c1ebbc9ab5de14c > > that adds a way to send guest trace

Re: [Qemu-devel] why restrict pull reqs to signed tags?

On Wed, 2016-03-09 at 15:41 +0100, Laszlo Ersek wrote: > According to your description, QEMU uses git improperly, so does > libvirt, and the KVM (kernel) queue too. Let's see... Imagine I'm working on a new feature, and I submit a carefully tested sequence of commits in a pull request. Someone

<    1   2   3