Re: [Qemu-devel] [PATCH 09/43] ppc: made printf always compile in debug output

2017-04-01 Thread David Gibson
On Sat, Apr 01, 2017 at 04:44:36PM +0300, Danil Antonov wrote: > >From 236c82fee189c22b88313fda71816e486edab8a6 Mon Sep 17 00:00:00 2001 > From: Danil Antonov > Date: Wed, 29 Mar 2017 12:23:58 +0300 > Subject: [PATCH 09/43] ppc: made printf always compile in debug output > > Wrapped printf calls

[Qemu-devel] [PATCHv2 for-2.9] pseries: Enforce homogeneous threads-per-core

2017-04-01 Thread David Gibson
For reasons that may be useful in future, CPU core objects, as used on the pseries machine type have their own nr-threads property, potentially allowing cores with different numbers of threads in the same system. If the user/management uses the values specified in query-hotpluggable-cpus as they'r

Re: [Qemu-devel] [PATCH v3 5/8] ppc/pnv: create the ICP and ICS objects under the machine

2017-04-01 Thread David Gibson
On Thu, Mar 30, 2017 at 10:15:11AM +0200, Cédric Le Goater wrote: > On 03/30/2017 03:55 AM, David Gibson wrote: > > On Wed, Mar 29, 2017 at 10:13:59AM +0200, Cédric Le Goater wrote: > >> On 03/29/2017 07:18 AM, David Gibson wrote: > >>> On Tue, Mar 28, 2017 at 09:32:29AM +0200, Cédric Le Goater wro

Re: [Qemu-devel] [PATCH for-2.9] pseries: Enforce homogeneous threads-per-core

2017-04-01 Thread David Gibson
On Fri, Mar 31, 2017 at 11:04:55AM +0530, Bharata B Rao wrote: > On Fri, Mar 31, 2017 at 10:21 AM, David Gibson > wrote: > > > For reasons that may be useful in future, CPU core objects, as used on the > > pseries machine type have their own nr-threads property, potentially > > allowing cores wit

Re: [Qemu-devel] [PATCH] disas/cris.c: Avoid unintentional sign extension

2017-04-01 Thread no-reply
Hi, This series seems to have some coding style problems. See output below for more information: Message-id: 1490970671-20560-1-git-send-email-peter.mayd...@linaro.org Subject: [Qemu-devel] [PATCH] disas/cris.c: Avoid unintentional sign extension Type: series === TEST SCRIPT BEGIN === #!/bin/bas

[Qemu-devel] [Bug 1031920] Re: Linux user gdbserver does not respond to remote `Ctrl-C' interrupts

2017-04-01 Thread Launchpad Bug Tracker
[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/1031920 Title: Linux user

[Qemu-devel] [Bug 1026176] Re: unable to boot squashfs through mtd device

2017-04-01 Thread Launchpad Bug Tracker
[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/1026176 Title: unable to b

Re: [Qemu-devel] [PATCH 14/43] usb: made printf always compile in debug output

2017-04-01 Thread Samuel Thibault
Danil Antonov, on sam. 01 avril 2017 16:48:58 +0300, wrote: > From 02b1e378eea154c0169a3d16b64ae27c64919c2c Mon Sep 17 00:00:00 2001 > From: Danil Antonov <[1]g.danil.a...@gmail.com> > Date: Wed, 29 Mar 2017 12:28:51 +0300 > Subject: [PATCH 14/43] usb: made printf always compile in debug output >

Re: [Qemu-devel] [PATCH 02/43] arm: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
Thanks for review. I'll update and resend these pathces (probably next week). 2017-04-01 17:51 GMT+03:00 Eric Blake : > On 04/01/2017 08:32 AM, Danil Antonov wrote: > >>From 1671b92e5a4a59d5e38ce754d1d0dde2401c8236 Mon Sep 17 00:00:00 2001 > > From: Danil Antonov > > Date: Wed, 29 Mar 2017 02:09

Re: [Qemu-devel] [PATCH 02/43] arm: made printf always compile in debug output

2017-04-01 Thread Eric Blake
On 04/01/2017 08:32 AM, Danil Antonov wrote: >>From 1671b92e5a4a59d5e38ce754d1d0dde2401c8236 Mon Sep 17 00:00:00 2001 > From: Danil Antonov > Date: Wed, 29 Mar 2017 02:09:33 +0300 > Subject: [PATCH 02/43] arm: made printf always compile in debug output > > Wrapped printf calls inside debug macros

[Qemu-devel] [PATCH v3 6/6] vmdk: Update metadata for multiple clusters

2017-04-01 Thread Ashijeet Acharya
Include a next pointer in VmdkMetaData struct to point to the previous allocated L2 table. Modify vmdk_L2update to start updating metadata for allocation of multiple clusters at once. Signed-off-by: Ashijeet Acharya --- block/vmdk.c | 136 -

[Qemu-devel] [PATCH v3 5/6] vmdk: Set maximum bytes allocated in one cycle

2017-04-01 Thread Ashijeet Acharya
Set the maximum bytes allowed to get allocated at once to be not more than the extent size boundary to handle writes at two separate extents appropriately. Signed-off-by: Ashijeet Acharya --- block/vmdk.c | 13 +++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/block/vm

[Qemu-devel] [PATCH v3 1/6] vmdk: Move vmdk_find_offset_in_cluster() to the top

2017-04-01 Thread Ashijeet Acharya
Move the existing vmdk_find_offset_in_cluster() function to the top of the driver. Also, introduce a new helper function size_to_clusters() which returns the number of clusters for a given size in bytes. Here, we leave the last cluster as we need to perform COW for that one. Signed-off-by: Ashijee

[Qemu-devel] [PATCH v3 3/6] vmdk: New functions to assist allocating multiple clusters

2017-04-01 Thread Ashijeet Acharya
Move the cluster tables loading code out of the existing get_cluster_offset() function to avoid code duplication and implement it in separate get_cluster_table() and vmdk_L2load() functions. Introduce two new helper functions handle_alloc() and vmdk_alloc_cluster_offset(). handle_alloc() helps to

[Qemu-devel] [PATCH v3 0/6] Optiomize VMDK I/O by allocating multiple clusters

2017-04-01 Thread Ashijeet Acharya
Previously posted series patches: v1 - http://lists.nongnu.org/archive/html/qemu-devel/2017-03/msg02044.html v2 - http://lists.nongnu.org/archive/html/qemu-devel/2017-03/msg05080.html This series helps to optimize the I/O performance of VMDK driver. Patch 1 helps us to move vmdk_find_offset_in_cl

[Qemu-devel] [PATCH v3 2/6] vmdk: Rename get_whole_cluster() to vmdk_perform_cow()

2017-04-01 Thread Ashijeet Acharya
Rename the existing function get_whole_cluster() to vmdk_perform_cow() as its sole purpose is to perform COW for the first and the last allocated clusters if needed. Signed-off-by: Ashijeet Acharya --- block/vmdk.c | 23 ++- 1 file changed, 14 insertions(+), 9 deletions(-) d

[Qemu-devel] [PATCH v3 4/6] vmdk: Rename get_cluster_offset() to vmdk_get_cluster_offset()

2017-04-01 Thread Ashijeet Acharya
Rename the existing get_cluster_offset() function to vmdk_get_cluster_offset() and have it make use of the new get_cluster_table() to load the cluster tables. Also, it is no longer used to allocate new clusters and hence perform COW. Make the necessary renames at all the occurrences of get_cluster_

Re: [Qemu-devel] [PATCH for-2.9] nbd: fix memory leak on socket_connect failed

2017-04-01 Thread Eric Blake
On 03/31/2017 07:15 PM, yaolujing wrote: > From: y00357587 > > When TCP connection fails between nbd server and client, > the local var, sioc, memory leak. > > This patch fixes the memory leak. > > Signed-off-by: y00357587 > --- > block/nbd.c | 1 + > 1 file changed, 1 insertion(+) Reviewed-

Re: [Qemu-devel] [PATCH 01/43] acpi: made printf always compile in debug output

2017-04-01 Thread Eric Blake
On 04/01/2017 08:32 AM, Danil Antonov wrote: >>From 8127ae68568b3c6876a5ee58a74e5ef0439f548a Mon Sep 17 00:00:00 2001 > From: Danil Antonov > Date: Wed, 29 Mar 2017 01:59:37 +0300 > Subject: [PATCH 01/43] acpi: made printf always compile in debug output > > Wrapped printf calls inside debug macro

[Qemu-devel] [PATCH 42/43] pci-bridge: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From bd32eaf17d401067d46891facfa37fe2a315cd2a Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:44:02 +0300 Subject: [PATCH 42/43] pci-bridge: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure th

[Qemu-devel] [PATCH 38/43] empty_slot: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From f91f364efb44edd51e865872eeb1bc2293d42930 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:42:32 +0300 Subject: [PATCH 38/43] empty_slot: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure th

[Qemu-devel] [PATCH 43/43] ssi: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 0bf08ebad3ccfe3e07920f53a304478e1e3b5813 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:44:25 +0300 Subject: [PATCH 43/43] ssi: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that prin

[Qemu-devel] [PATCH 41/43] nvram: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From f0ac5a35af1c521bb8f87720ec7f82a9452e38a4 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:43:45 +0300 Subject: [PATCH 41/43] nvram: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that pr

[Qemu-devel] [PATCH 40/43] mips: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From fafbd66ef7cd5e2295a5c14e24a6ec1520ca79f4 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:43:28 +0300 Subject: [PATCH 40/43] mips: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that pri

[Qemu-devel] [PATCH 37/43] audio: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From ef4e9e576ae80c227d06721284bd49b699e71c71 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:41:59 +0300 Subject: [PATCH 37/43] audio: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that pr

[Qemu-devel] [PATCH 36/43] gpi: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From adb8f4b937b80629881ea23310a8d75ac4671b2a Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:41:38 +0300 Subject: [PATCH 36/43] gpi: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that prin

[Qemu-devel] [PATCH 34/43] isa: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 2b9e98a4f5a7235bfef9dac5d0c94e5ecaeb1981 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:40:57 +0300 Subject: [PATCH 34/43] isa: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that prin

[Qemu-devel] [PATCH 30/43] block: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 63139dc0a7e3b5c8caa1ecf6fbe900372fddeba0 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:39:12 +0300 Subject: [PATCH 30/43] block: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that pr

[Qemu-devel] [PATCH 33/43] i2c: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 0372d38e66070fefc5f65573dc7fe7bce4cbb9fd Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:40:31 +0300 Subject: [PATCH 33/43] i2c: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that prin

[Qemu-devel] [PATCH 32/43] char: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 9147a39cc2dabe76e7c1b38e801069390d5a3321 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:40:02 +0300 Subject: [PATCH 32/43] char: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that pri

[Qemu-devel] [PATCH 31/43] display: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 40bba9c5cdb7060dd01d1c7d81140779e45a489d Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:39:40 +0300 Subject: [PATCH 31/43] display: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that

[Qemu-devel] [PATCH 28/43] sparc64: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 825d7eda5d2900ef7eda37eeebf2b50ea445d50b Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:38:23 +0300 Subject: [PATCH 28/43] sparc64: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that

[Qemu-devel] [PATCH 27/43] vfio: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From c986c5a54a394feadfd885d41848f28d11fec40f Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:37:26 +0300 Subject: [PATCH 27/43] vfio: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that pri

[Qemu-devel] [PATCH 26/43] unicore32: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 32ac7bdabbf1935a8a30f606aa3263461117e7d0 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:36:57 +0300 Subject: [PATCH 26/43] unicore32: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure tha

[Qemu-devel] [PATCH 24/43] migration: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From e5719e802fcd1d1b426d687524ed46f10d044941 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:35:10 +0300 Subject: [PATCH 24/43] migration: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure tha

[Qemu-devel] [PATCH 25/43] kvm-all: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From f818d3ef7db8cc5b99656fd1059c0d7d07dea571 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:35:36 +0300 Subject: [PATCH 25/43] kvm-all: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that

[Qemu-devel] [PATCH 22/43] virtio: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 2e5d92b2d1955b3e85f1e93ad98469d00c47a658 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:33:29 +0300 Subject: [PATCH 22/43] virtio: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that p

[Qemu-devel] [PATCH 23/43] page-cahe: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From fc02b5cacabab0d1fc547167954abb7447bfef21 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:34:38 +0300 Subject: [PATCH 23/43] page-cahe: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure tha

[Qemu-devel] [PATCH 21/43] s390: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From cbc3425092b6ee94d365f8714a39af5a583a Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:33:01 +0300 Subject: [PATCH 21/43] s390: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that pri

[Qemu-devel] [PATCH 20/43] i386: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From a132733828991a950855138982d4a60858e92b04 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:32:16 +0300 Subject: [PATCH 20/43] i386: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that pri

[Qemu-devel] [PATCH 19/43] input: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 2ff917db477911239c613f3b8f3605b12d669bfe Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:31:47 +0300 Subject: [PATCH 19/43] input: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that pr

[Qemu-devel] [PATCH 17/43] net: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From d01cd76d0b20ee8fa67c07da64b0e2301e510247 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:30:42 +0300 Subject: [PATCH 17/43] net: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that prin

[Qemu-devel] [PATCH 18/43] pci-host: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From b5c0463a6d755be8bfcf4402390e877abcf606c6 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:31:07 +0300 Subject: [PATCH 18/43] pci-host: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that

[Qemu-devel] [PATCH 16/43] intc: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 3985e3226a996f019649b6b7a4d6e3e64f81ea8d Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:30:06 +0300 Subject: [PATCH 16/43] intc: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that pri

[Qemu-devel] [PATCH 15/43] timer: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 49700fb48d06fd29d13013b7d159017af5b7 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:29:29 +0300 Subject: [PATCH 15/43] timer: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that pr

[Qemu-devel] [PATCH 14/43] usb: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 02b1e378eea154c0169a3d16b64ae27c64919c2c Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:28:51 +0300 Subject: [PATCH 14/43] usb: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that prin

[Qemu-devel] [PATCH 13/43] pci: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 7ff1463852763cbe7b8260147aa0c19bf91c8cbb Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:27:57 +0300 Subject: [PATCH 13/43] pci: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that prin

[Qemu-devel] [PATCH 12/43] sd: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 78c7cc133ba566b13afe6e9924e174b6d081e393 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:27:24 +0300 Subject: [PATCH 12/43] sd: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that print

[Qemu-devel] [PATCH 11/43] scsi: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 48b18f304de1761128e8cccbb517ddad4346c824 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:26:43 +0300 Subject: [PATCH 11/43] scsi: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that pri

[Qemu-devel] [PATCH 10/43] s390x: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From ea9cd8f02bd98548435f561e62f4f9b672318bcb Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:26:05 +0300 Subject: [PATCH 10/43] s390x: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that pr

[Qemu-devel] [PATCH 09/43] ppc: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 236c82fee189c22b88313fda71816e486edab8a6 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 12:23:58 +0300 Subject: [PATCH 09/43] ppc: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that prin

[Qemu-devel] [PATCH 08/43] kvm: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 7aed02e5ee9662d4ff8e7857594fdf7b3b52c9e4 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 02:16:54 +0300 Subject: [PATCH 08/43] kvm: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that prin

[Qemu-devel] [PATCH 07/43] ldst_helper: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From a827e069c46b272ab952dfde370c1954decdf3dd Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 02:15:48 +0300 Subject: [PATCH 07/43] ldst_helper: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure t

[Qemu-devel] [PATCH 07/43] ldst_helper: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From a827e069c46b272ab952dfde370c1954decdf3dd Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 02:15:48 +0300 Subject: [PATCH 07/43] ldst_helper: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure t

[Qemu-devel] [PATCH 06/43] unicore32: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From e7a576c46bcdaeb49c1c4fdbb59d38944df340ae Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 02:14:49 +0300 Subject: [PATCH 06/43] unicore32: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure tha

[Qemu-devel] [PATCH 05/43] xen-mapcache: made printf always compile in debug

2017-04-01 Thread Danil Antonov
>From 0e4a8a20c9c05e547d42be1b9ef868d12e7b43a9 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 02:14:06 +0300 Subject: [PATCH 05/43] xen-mapcache: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure

[Qemu-devel] [PATCH 04/43] xen-hvm: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 05d558842b0a10ee3f0606eb54068b6ba03906a3 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 02:13:13 +0300 Subject: [PATCH 04/43] xen-hvm: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that

[Qemu-devel] [PATCH 02/43] arm: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 1671b92e5a4a59d5e38ce754d1d0dde2401c8236 Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 02:09:33 +0300 Subject: [PATCH 02/43] arm: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that prin

[Qemu-devel] [PATCH 03/43] xen-common: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 0e3f1f202ebbf14259dee89e523c1fbc6f08d4ed Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 02:12:31 +0300 Subject: [PATCH 03/43] xen-common: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure th

[Qemu-devel] [PATCH 01/43] acpi: made printf always compile in debug output

2017-04-01 Thread Danil Antonov
>From 8127ae68568b3c6876a5ee58a74e5ef0439f548a Mon Sep 17 00:00:00 2001 From: Danil Antonov Date: Wed, 29 Mar 2017 01:59:37 +0300 Subject: [PATCH 01/43] acpi: made printf always compile in debug output Wrapped printf calls inside debug macros (DPRINTF) in `if` statement. This will ensure that pri

Re: [Qemu-devel] [PATCH v2 3/7] vmdk: Factor out metadata loading code out of get_cluster_offset()

2017-04-01 Thread Ashijeet Acharya
On Fri, Mar 31, 2017 at 11:33 AM, Fam Zheng wrote: > On Sat, 03/25 16:48, Ashijeet Acharya wrote: >> Move the cluster tables loading code out of the existing >> get_cluster_offset() function and implement it in separate > > Now it's renamed to vmdk_perform_cow() in previous patch, the commit messa

[Qemu-devel] [PATCH 4/4] slirp: add a fake NC-SI backend

2017-04-01 Thread Cédric Le Goater
NC-SI (Network Controller Sideband Interface) enables a BMC to manage a set of NICs on a system. This model takes the simplest approach and reverses the NC-SI packets to pretend a NIC is present and exercise the Linux driver. The NCSI header file comes from mainline Linux and was untabified. Sig

[Qemu-devel] [PATCH 3/4] aspeed: add a FTGMAC100 nic

2017-04-01 Thread Cédric Le Goater
There is a second NIC but we do not use it for the moment. We use the 'aspeed' property to tune the definition of the end of ring buffer bit for the Aspeed SoCs. Signed-off-by: Cédric Le Goater --- hw/arm/aspeed_soc.c | 21 + include/hw/arm/aspeed_soc.h | 2 ++ 2 fil

[Qemu-devel] [PATCH 2/4] net/ftgmac100: add a 'aspeed' property

2017-04-01 Thread Cédric Le Goater
The Aspeed SoCs have a different definition of the end of the ring buffer bit. Add a property to specify which set of bits should be used by the NIC. Signed-off-by: Cédric Le Goater --- hw/net/ftgmac100.c | 19 --- include/hw/net/ftgmac100.h | 4 2 files changed, 20

[Qemu-devel] [PATCH 1/4] net: add FTGMAC100 support

2017-04-01 Thread Cédric Le Goater
The FTGMAC100 device is an Ethernet controller with DMA function that can be found on Aspeed SoCs (which include NCSI). It is fully compliant with IEEE 802.3 specification for 10/100 Mbps Ethernet and IEEE 802.3z specification for 1000 Mbps Ethernet and includes Reduced Media Independent Interface

[Qemu-devel] [PATCH 0/4] FTGMAC100 nic model for the Aspeed SoCs

2017-04-01 Thread Cédric Le Goater
Hi, The Aspeed SoCs AST2400 and AST2500 have two FTGMAC100 ethernet controllers. This serie proposes a model for this device and a way to customize the bit definitions which are slightly different from the Faraday definitions. The last patch adds a fake NC-SI (Network Controller Sideband Interfac

[Qemu-devel] [RFC PATCH qemu v3 4/4] spapr/iommu: Enable in-kernel TCE acceleration via VFIO KVM device

2017-04-01 Thread Alexey Kardashevskiy
This uses new kernel KVM_CAP_SPAPR_TCE_VFIO capability to enable in-kernel acceleration of TCE update requests which will go via the VFIO KVM device. Signed-off-by: Alexey Kardashevskiy --- target/ppc/kvm_ppc.h | 6 ++ hw/ppc/spapr_iommu.c | 4 target/ppc/kvm.c | 7 ++- 3 files

[Qemu-devel] [RFC PATCH qemu v3 1/4] memory/iommu: QOM'fy IOMMU MemoryRegion

2017-04-01 Thread Alexey Kardashevskiy
This defines new QOM object - IOMMUMemoryRegion - with MemoryRegion as a parent. This moves IOMMU-related fields from MR to IOMMU MR. However to avoid dymanic QOM casting in fast path (address_space_translate, etc), this adds an @is_iommu boolean flag to MR and provides new helper to do simple cas

[Qemu-devel] [RFC PATCH qemu v3 2/4] vfio-pci: Reorder group-to-container attaching

2017-04-01 Thread Alexey Kardashevskiy
At the moment VFIO PCI device initialization works as follows: vfio_realize vfio_get_group vfio_connect_container register memory listeners (1) update QEMU groups lists vfio_kvm_device_add_group Then (example f

[Qemu-devel] [RFC PATCH qemu v3 3/4] vfio/spapr: Add a notifier for PPC64 HV/PR KVM about new group attached to LIOBN

2017-04-01 Thread Alexey Kardashevskiy
This implements a notification for a new IOMMU group attached to sPAPR's logical IO bus (LIOBN) to enable in-kernel TCE acceleration. Signed-off-by: Alexey Kardashevskiy --- include/hw/ppc/spapr.h| 1 + include/hw/vfio/vfio-common.h | 2 ++ hw/ppc/spapr_iommu.c | 5 + hw/

[Qemu-devel] [RFC PATCH qemu v3 0/4] vfio-pci, spapr: Allow in-kernel acceleration

2017-04-01 Thread Alexey Kardashevskiy
This is my current working tree to support kernel's "powerpc/kvm/vfio: Enable in-kernel acceleration". Changes: v3: * fixed multiple architectures with respect to IOMMU MR * removed sPAPRIOMMUMemoryRegion v2: * QOM'fy of IOMMUMemoryRegion * fix comments from v1 review Please comment. Thanks.

Re: [Qemu-devel] [RFC QEMU PATCH v2 01/10] nvdimm xen: disable label support on Xen

2017-04-01 Thread Konrad Rzeszutek Wilk
On Mon, Mar 20, 2017 at 08:12:40AM +0800, Haozhong Zhang wrote: > If xen_enabled(), memory_region_get_ram_ptr() always returns NULL and > nvdimm_realize() cannot get the correct pointer to the label area. This > commit disables the label support for Xen accelerator to workaround > this issue. > >

Re: [Qemu-devel] [PATCH] main-loop: Acquire main_context lock around os_host_main_loop_wait.

2017-04-01 Thread Richard W.M. Jones
On Fri, Mar 31, 2017 at 09:51:33PM +0100, Richard W.M. Jones wrote: > When running virt-rescue the serial console hangs from time to time. > Virt-rescue runs an ordinary Linux kernel "appliance", but there is > only a single idle process running inside, so the qemu main loop is > largely idle. Wit

[Qemu-devel] [Bug 1678466] [NEW] using x-vga=on with vfio-pci leads to segfault

2017-04-01 Thread sh-dvl
Public bug reported: bug occures at least with qemu 2.8.0 and 2.8.1 in 64bit-system stripped cmd for minimal config: qemu-system-i386 -m 2048 -M q35 -enable-kvm -nodefaults -nodefconfig -device ioh3420,bus=pcie.0,addr=0x9,multifunction=on,port=1,chassis=1,id=root.1 -device vfio-pci,host=01:00.

[Qemu-devel] [PATCH v4] Allow setting NUMA distance for different NUMA nodes

2017-04-01 Thread He Chen
Current, QEMU does not provide a clear command to set vNUMA distance for guest although we already have `-numa` command to set vNUMA nodes. vNUMA distance makes sense in certain scenario. But now, if we create a guest that has 4 vNUMA nodes, when we check NUMA info via `numactl -H`, we will see:

Re: [Qemu-devel] [PATCH] char: kick main loop after adding a watch

2017-04-01 Thread Paolo Bonzini
On 31/03/2017 19:31, Richard W.M. Jones wrote: > On Fri, Mar 31, 2017 at 06:53:56PM +0200, Paolo Bonzini wrote: >> glib is expecting QEMU to use g_main_context_acquire around accesses to >> GMainContext. However QEMU is not doing that, instead it is taking its >> own mutex. So we should add g

[Qemu-devel] [PATCH v2 4/4] hmp: info migrate_parameters format tunes

2017-04-01 Thread Peter Xu
Do the same (one per line) to the parameter list. CC: "Dr. David Alan Gilbert" Reviewed-by: "Dr. David Alan Gilbert" Signed-off-by: Peter Xu --- hmp.c | 22 ++ 1 file changed, 10 insertions(+), 12 deletions(-) diff --git a/hmp.c b/hmp.c index 95eef8c..b33e39e 100644 --- a/

[Qemu-devel] [PATCH v2 3/4] hmp: info migrate_capability format tunes

2017-04-01 Thread Peter Xu
Dump the info in a single line is hard to read. Do it one per line. Also, the first "capabilities:" didn't help much. Let's remove it. CC: "Dr. David Alan Gilbert" Reviewed-by: "Dr. David Alan Gilbert" Signed-off-by: Peter Xu --- hmp.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)

[Qemu-devel] [PATCH v2 1/4] migration: set current_active_state once

2017-04-01 Thread Peter Xu
We set it right above this one. No need to set it twice. CC: Juan Quintela CC: Dr. David Alan Gilbert Reviewed-by: Dr. David Alan Gilbert Signed-off-by: Peter Xu --- migration/migration.c | 1 - 1 file changed, 1 deletion(-) diff --git a/migration/migration.c b/migration/migration.c index 54

[Qemu-devel] [PATCH v2 0/4] several migrations related patches

2017-04-01 Thread Peter Xu
v2: - fix comment for threshold_size [Dave] - drop patch 5 - add Dave's r-b for each patch Mostly small touch-ups, the last one looks like a cpu throttle bug on time slice calculation (or I missed anything?). Anyway, please review, thanks. Peter Xu (4): migration: set current_active_state once

[Qemu-devel] [PATCH v2 2/4] migration: rename max_size to threshold_size

2017-04-01 Thread Peter Xu
In migration codes (especially in migration_thread()), max_size is used in many place for the threshold value that we will start to do the final flush and jump to the next stage to dump the whole rest things to destination. However its name is confusing to first readers. Let's rename it to "thresho

Re: [Qemu-devel] [PATCH 5/5] cpu: throttle: fix throttle time slice

2017-04-01 Thread Peter Xu
On Fri, Mar 31, 2017 at 06:38:50PM +0200, Paolo Bonzini wrote: > > > On 27/03/2017 09:21, Peter Xu wrote: > > @@ -641,8 +640,7 @@ static void cpu_throttle_thread(CPUState *cpu, > > run_on_cpu_data opaque) > > } > > > > pct = (double)cpu_throttle_get_percentage()/100; > > -throttl

Re: [Qemu-devel] [PATCH 2/5] migration: rename max_size to threshold_size

2017-04-01 Thread Peter Xu
On Fri, Mar 31, 2017 at 07:59:19PM +0100, Dr. David Alan Gilbert wrote: > * Peter Xu (pet...@redhat.com) wrote: > > In migration codes (especially in migration_thread()), max_size is used > > in many place for the threshold value that we will start to do the final > > flush and jump to the next sta

Re: [Qemu-devel] [PATCH 30/51] ram: Move src_page_req* to RAMState

2017-04-01 Thread Peter Xu
On Fri, Mar 31, 2017 at 04:25:56PM +0100, Dr. David Alan Gilbert wrote: > * Peter Xu (pet...@redhat.com) wrote: > > On Thu, Mar 23, 2017 at 09:45:23PM +0100, Juan Quintela wrote: > > > This are the last postcopy fields still at MigrationState. Once there > > > > s/This/These/ > > > > > Move Migr