Re: [Qemu-devel] [PATCH for-2.12] monitor: bind dispatch bh to iohandler context

On Thu, Apr 05, 2018 at 01:34:31PM +0100, Stefan Hajnoczi wrote: > On Wed, Apr 04, 2018 at 10:07:34AM -0500, Eric Blake wrote: > > On 04/04/2018 09:22 AM, Stefan Hajnoczi wrote: > > > On Tue, Apr 03, 2018 at 01:01:15PM +0800, Peter Xu wrote: > > >> Eric Auger reported the problem days ago that OOB

Re: [Qemu-devel] [PATCH for-2.12] monitor: bind dispatch bh to iohandler context

On Wed, Apr 04, 2018 at 03:22:20PM +0100, Stefan Hajnoczi wrote: > On Tue, Apr 03, 2018 at 01:01:15PM +0800, Peter Xu wrote: > > Eric Auger reported the problem days ago that OOB broke ARM when running > > with libvirt: > > > > http://lists.gnu.org/archive/html/qemu-devel/2018-03/msg06231.html

[Qemu-devel] [Bug 1416246] Re: create guest fail when compile qemu with parameter "--disable-gtk"

[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1416246 Title: create

Re: [Qemu-devel] [PATCH v2 for-2.12] tap: set vhostfd passed from qemu cli to non-blocking

On Fri, Apr 06, 2018 at 01:51:25PM -0500, Brijesh Singh wrote: > A guest boot hangs while probing the network interface when > iommu_platform=on is used. > > The following qemu cli hangs without this patch: > > # $QEMU \ > -netdev tap,fd=3,id=hostnet0,vhost=on,vhostfd=4 3<>/dev/tap67 >

Re: [Qemu-devel] [PATCH v3 00/10] migration: improve and cleanup compression

Hi Paolo, Michael, Stefan and others, Could anyone merge this patchset if it is okay to you guys? On 03/30/2018 03:51 PM, guangrong.x...@gmail.com wrote: From: Xiao Guangrong Changelog in v3: Following changes are from Peter's review: 1) use comp_param[i].file and

[Qemu-devel] [PATCH v2] iotests: fix wait_until_completed()

If there are more than one events, wait_until_completed() might return the 2nd event even if the 1st event is JOB_COMPLETED, since the for loop will continue to run even if completed is set to True. It never happened before, but it can be triggered when OOB is enabled due to the RESUME startup

Re: [Qemu-devel] [PATCH v8 14/23] monitor: separate QMP parser and dispatcher

On Wed, Apr 04, 2018 at 03:58:56PM +0200, Marc-André Lureau wrote: > Hi Peter > > On Wed, Mar 28, 2018 at 6:02 AM, Peter Xu wrote: > > On Mon, Mar 26, 2018 at 11:46:13AM +0200, Marc-André Lureau wrote: > >> Hi > >> > >> On Mon, Mar 26, 2018 at 11:08 AM, Peter Xu

[Qemu-devel] [PATCH v3 2/2] Add QTest testcase for the Intel Hexadecimal Object File Loader.

'test.hex' file is a bare metal ARM software stored in Hexadecimal Object Format. When it's loaded by QEMU, it will print "Hello world!\n" on console. `pre_store` array in 'hexloader-test.c' file, stores the binary format of 'test.hex' file, which is used to verify correctness. Signed-off-by: Su

[Qemu-devel] [PATCH v3 1/2] Implement .hex file loader

This patch adds Intel Hexadecimal Object File format support to the loader. The file format specification is available here: http://www.piclist.com/techref/fileext/hex/intel.htm The file format is mainly intended for embedded systems and microcontrollers, such as Arduino, ARM, STM32, etc.

[Qemu-devel] [PATCH v3 0/2] Implement Hex file loader and add test case

These series of patchs implement Intel Hexadecimal File loader and add QTest testcase to verify the correctness of Loader. v1: Basic version. v2: Replace `do{}while(cond);` block with `for(;;)` block. v3: Add two new files information in MAINTAINERS. Su Hang (2): Implement .hex file loader

[Qemu-devel] [PATCH v3 RFC 0/2] Implement Hex file loader and add test case

These series of patchs implement Intel Hexadecimal File loader and add QTest testcase to verify the correctness of Loader. v1: Basic version. v2: Replace `do{}while(cond);` block with `for(;;)` block. v3: Add two new files information in MAINTAINERS. Su Hang (2): Implement .hex file loader

[Qemu-devel] [PATCH v3 2/2] Add QTest testcase for the Intel Hexadecimal Object File Loader.

'test.hex' file is a bare metal ARM software stored in Hexadecimal Object Format. When it's loaded by QEMU, it will print "Hello world!\n" on console. `pre_store` array in 'hexloader-test.c' file, stores the binary format of 'test.hex' file, which is used to verify correctness. Signed-off-by: Su

[Qemu-devel] [PATCH v3 1/2] Implement .hex file loader

This patch adds Intel Hexadecimal Object File format support to the loader. The file format specification is available here: http://www.piclist.com/techref/fileext/hex/intel.htm The file format is mainly intended for embedded systems and microcontrollers, such as Arduino, ARM, STM32, etc.

Re: [Qemu-devel] [Qemu-arm] [PATCH v2 2/2] arm_gicv3_kvm: kvm_dist_get/put: skip the registers banked by GICR

On 2018/4/6 17:36, Peter Maydell wrote: > On 5 April 2018 at 15:22, Peter Maydell wrote: >> > On 29 March 2018 at 11:54, Peter Maydell wrote: >>> >> On 23 March 2018 at 12:08, Peter Maydell >>> >> wrote: >>>

[Qemu-devel] [PATCH v2 2/2] vfio-ccw: introduce vfio_ccw_get_device()

A recent patch fixed leaks of the dynamically allocated vcdev->vdev.name field in vfio_ccw_realize(), but we now have three freeing sites for it. This is unfortunate and seems to indicate something is wrong with its life cycle. The root issue is that vcdev->vdev.name is set before

[Qemu-devel] [PATCH v2 0/2] vfio-ccw: fix memory leak + cleanup

This series fixes two leaks in vfio_ccw_realize(). The v2 is basically the same as the initial series, split in two patches: a trivial bugfix suitable for 2.12 and stable, and a follow-up with more cleanup for 2.13. -- Greg --- Greg Kurz (2): vfio-ccw: fix memory leaks in

[Qemu-devel] [PATCH v2 1/2] vfio-ccw: fix memory leaks in vfio_ccw_realize()

If the subchannel is already attached or if vfio_get_device() fails, the code jumps to the 'out_device_err' label and doesn't free the string it has just allocated. The code should be reworked so that vcdev->vdev.name only gets set when the device has been attached, and freed when it is about to

[Qemu-devel] [PATCH 5/5] migration: disable RDMA WRITR after postcopy started.

RDMA write operations are performed with no notification to the destination qemu, then the destination qemu can not wakeup. So disable RDMA WRITE after postcopy started. Signed-off-by: Lidong Chen --- migration/qemu-file.c | 3 ++- migration/rdma.c | 12

[Qemu-devel] [PATCH 4/5] migration: fix qemu carsh when RDMA live migration

After postcopy, the destination qemu work in the dedicated thread, so only invoke yield_until_fd_readable before postcopy migration. Signed-off-by: Lidong Chen --- migration/rdma.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/migration/rdma.c

[Qemu-devel] [PATCH 2/5] migration: add the interface to set get_return_path

The default get_return_path function of iochannel does not work for RDMA live migration. So add the interface to set get_return_path. Signed-off-by: Lidong Chen --- migration/qemu-file-channel.c | 12 migration/qemu-file.c | 10 --

[Qemu-devel] [PATCH 1/5] migration: create a dedicated connection for rdma return path

If start a RDMA migration with postcopy enabled, the source qemu establish a dedicated connection for return path. Signed-off-by: Lidong Chen --- migration/rdma.c | 94 ++-- 1 file changed, 91 insertions(+), 3

[Qemu-devel] [PATCH 0/5] Enable postcopy RDMA live migration

Current Qemu RDMA communication does not support send and receive data at the same time, so when RDMA live migration with postcopy enabled, the source qemu return path thread get qemu file error. Those patch add the postcopy support for RDMA live migration. Lidong Chen (5): migration: create a

[Qemu-devel] [PATCH 3/5] migration: implement the get_return_path for RDMA iochannel

the default get_return_path function does not work for RDMA live migration, the patch implement the get_return_path for RDMA iochannel. Signed-off-by: Lidong Chen --- migration/rdma.c | 38 ++ 1 file changed, 38 insertions(+) diff