Re: [Qemu-devel] [PATCH 2/2] migration: calculate downtime on dst side

* Alexey Perevalov (a.pereva...@samsung.com) wrote: > This patch provides downtime calculation per vCPU, > as a summary and as a overlapped value for all vCPUs. > > This approach just keeps tree with page fault addr as a key, > and t1-t2 interval of pagefault time and page copy time, with >

[Qemu-devel] [PATCH v2 06/21] pflash_cfi01: Remove user_creatable flag

TYPE_CFI_PFLASH01 devices need to be mapped by pflash_cfi01_register() (or equivalent) and can't be used with -device. Remove user_creatable from the device class. Cc: Kevin Wolf Cc: Max Reitz Cc: qemu-bl...@nongnu.org Cc: Laszlo Ersek

[Qemu-devel] [PATCH v2 20/21] xen-sysdev: Remove user_creatable flag

TYPE_XENSYSDEV is only used internally by xen_be_init(), and is not supposed to be plugged/unplugged dynamically. Remove the user_creatable flag from the device class. Cc: Juergen Gross , Cc: Peter Maydell , Cc: Thomas Huth Cc:

Re: [Qemu-devel] [RFC PATCH 0/2] Calcuate downtime for postcopy live migration

* Alexey Perevalov (a.pereva...@samsung.com) wrote: > Hi David, > > I already asked you about downtime calculation for postcopy live migration. > As I remember you said it's worth not to calculate it per vCPU or maybe I > understood you incorrectly. I decided to proof it could be useful. Thanks

[Qemu-devel] [PATCH v2 15/21] esp: Remove user_creatable flag

esp devices aren't going to work with -device, as they need IRQs to be connected and mmio to be mapped (this is done by esp_init()). Remove the user_creatable flag from the device class. Cc: Paolo Bonzini Signed-off-by: Eduardo Habkost --- Changes v1 ->

[Qemu-devel] [PATCH v2 12/21] isabus-bridge: Remove user_creatable flag

isabus-bridge needs to be created by isa_bus_new(), and won't work with -device, as it won't create the TYPE_ISA_BUS bus itself. Remove the user_creatable flag from the device class. Cc: Marcel Apfelbaum Cc: "Michael S. Tsirkin" Signed-off-by: Eduardo Habkost

[Qemu-devel] [PATCH v2 14/21] fw_cfg: Remove user_creatable flag

fw_cfg won't work with -device, as: * fw_cfg_init1() won't get called for the device; * The device won't appear at /machine/fw_cfg, and won't work with the -fw_cfg command-line option. Remove the user_creatable flag from the device class. Cc: "Michael S. Tsirkin" Cc: Laszlo

[Qemu-devel] [PATCH v2 11/21] allwinner-ahci: Remove user_creatable flag

allwinner-ahci needs its IRQ to be connected and mmio to be mapped (this is done by the alwinner-a10 device realize method), and won't work with -device. Remove the user_creatable flag from the device class. Cc: John Snow Cc: qemu-bl...@nongnu.org Cc: Beniamino Galvani

[Qemu-devel] [ANNOUNCE] QEMU 2.9.0-rc3 is now available

Hello, On behalf of the QEMU Team, I'd like to announce the availability of the fourth release candidate for the QEMU 2.9 release. This release is meant for testing purposes and should not be used in a production environment. http://download.qemu-project.org/qemu-2.9.0-rc3.tar.xz

Re: [Qemu-devel] [RFC 19/19] virtio-mmio: Remove user_creatable flag

On Mon, Apr 03, 2017 at 05:50:13PM +0200, Laszlo Ersek wrote: > On 04/01/17 02:46, Eduardo Habkost wrote: > > virtio-mmio needs to be wired and mapped by other device or board > > code, and won't work with -device. Remove the user_creatable flag > > from the device class. > > > > Cc: Peter

[Qemu-devel] [PATCH v2 03/21] xen-backend: Remove FIXME comment about user_creatable flag

xen-backend can be plugged/unplugged dynamically when using the Xen accelerator, so keep the user_creatable flag on the device class and remove the FIXME comment. Cc: Juergen Gross , Cc: Peter Maydell , Cc: Thomas Huth Cc:

[Qemu-devel] [PATCH v2 16/21] generic-sdhci: Remove user_creatable flag

generic-sdhci needs to be wired by other devices' code, so it can't be used with -device. Remove the user_creatable flag from the device class. Cc: Peter Maydell Cc: "Edgar E. Iglesias" Cc: David Gibson Cc:

[Qemu-devel] [PATCH] Put all trace.o into libqemuutil.a

Put all trace.o into libqemuutil.a Currently all trace.o are linked into qemu-system, qemu-img, qemu-nbd, qemu-io etc., even the corresponding components are not included. Put all trace.o into libqemuutil.a that the linker would only pull in .o files containing symbols that are actually

[Qemu-devel] [PATCH v2 00/21] qdev/sysbus: Set user_creatable=false by default on sysbus

Changes v1 -> v2 * Rewrote series name and cover letter completely to not pretend we're fixing the q35 lack-of-sysbus-whitelist bug, and explain the motivation for the series. * Previous series name was: "sysbus: Don't allow -device/device_add by default" * Rewrote

[Qemu-devel] [PATCH v2 05/21] fdc: Remove user_creatable flag from sysbus-fdc & SUNW, fdtwo

sysbus-fdc and SUNW,fdtwo devices need IRQs to be wired and mmio to be mapped, and can't be used with -device. Unset user_creatable on their device classes. Cc: John Snow Cc: Kevin Wolf Cc: Max Reitz Cc: qemu-bl...@nongnu.org Cc: Thomas

[Qemu-devel] [PATCH v2 17/21] hpet: Remove user_creatable flag

hpet needs to be mapped and wired by the board code and won't work with -device. Remove the user_creatable flag from the device class. Cc: "Michael S. Tsirkin" Cc: Paolo Bonzini Signed-off-by: Eduardo Habkost --- Changes v1 -> v2: *

[Qemu-devel] [PATCH v2 21/21] s390-pcibus: No need to set user_creatable=false explicitly

TYPE_S390_PCI_HOST_BRIDGE is a subclass of TYPE_PCI_HOST_BRIDGE, which is a subclass of TYPE_SYS_BUS_DEVICE. TYPE_SYS_BUS_DEVICE already sets user_creatable=false, so we don't require an explicit user_creatable=false assignment in s390_pcihost_class_init(). Cc: Alexander Graf Cc:

[Qemu-devel] [PATCH v2 01/21] qdev: Replace cannot_instantiate_with_device_add_yet with !user_creatable

cannot_instantiate_with_device_add_yet was introduced by commit 837d37167dc446af8a91189108b363c04609e296 to replace no_user. It was supposed to be a temporary measure. When it was introduced, we had 54 cannot_instantiate_with_device_add_yet=true lines in the code. Today (3 years later) this

[Qemu-devel] [PATCH v2 09/21] kvmvapic: Remove user_creatable flag

The kvmvapic device is only usable when created by apic_common_realize(), not using -device. Remove the user_creatable flag from the device class. Cc: Igor Mammedov Cc: Paolo Bonzini Cc: Richard Henderson Cc: Eduardo Habkost

[Qemu-devel] [PATCH v2 08/21] ioapic: Remove user_creatable flag

An ioapic device is already created by the q35 initialization code, and using "-device ioapic" or "-device kvm-ioapic" will always fail with "Only 1 ioapics allowed". Remove the user_creatable flag from the ioapic device classes. Cc: Igor Mammedov Cc: "Michael S. Tsirkin"

Re: [Qemu-devel] How to provide build/CI environment for NetBSD host

On 4 April 2017 at 22:22, Ryo ONODERA wrote: > I saw "Warning of unsupported host systems" > in http://wiki.qemu-project.org/ChangeLog/2.9 wiki page. > > I would like to contribute to qemu's NetBSD host support. > > I can provide NetBSD/amd64(x86_64) 7-stable build >

[Qemu-devel] [PATCH v2 10/21] sysbus-ahci: Remove user_creatable flag

The sysbus-ahci devices are supposed to be created and wired by code from other devices, like calxeda_init() and xlnx_zynqmp_realize(), and won't work with -device. Remove the user_creatable flag from the device class. Cc: John Snow Cc: qemu-bl...@nongnu.org Cc: Rob Herring

[Qemu-devel] [PATCH v2 18/21] sysbus-ohci: Remove user_creatable flag

sysbus-ohci needs to be mapped and wired by device or board code, and won't work with -device. Remove the user_creatable flag from the device class. Cc: Gerd Hoffmann Signed-off-by: Eduardo Habkost --- Changes v1 -> v2: * Commit message rewrite only ---

[Qemu-devel] How to provide build/CI environment for NetBSD host

Hi, I saw "Warning of unsupported host systems" in http://wiki.qemu-project.org/ChangeLog/2.9 wiki page. I would like to contribute to qemu's NetBSD host support. I can provide NetBSD/amd64(x86_64) 7-stable build environment as build/CI machine to the qemu project if nobody provides it to the

Re: [Qemu-devel] [PATCH 45/51] ram: Use page number instead of an address for the bitmap operations

"Dr. David Alan Gilbert" wrote: > * Juan Quintela (quint...@redhat.com) wrote: >> We use an unsigned long for the page number. Notice that our bitmaps >> already got that for the index, so we have that limit. >> >> Signed-off-by: Juan Quintela >> ---

Re: [Qemu-devel] [PATCH 46/51] ram: Remember last_page instead of last_offset

"Dr. David Alan Gilbert" wrote: > * Juan Quintela (quint...@redhat.com) wrote: >> Signed-off-by: Juan Quintela >> --- >> migration/ram.c | 14 +++--- >> 1 file changed, 7 insertions(+), 7 deletions(-) >> >> diff --git a/migration/ram.c

Re: [Qemu-devel] [PATCH v3 0/1] slirp: add SOCKS5 support

Hi, This series seems to have some coding style problems. See output below for more information: Subject: [Qemu-devel] [PATCH v3 0/1] slirp: add SOCKS5 support Type: series Message-id: 20170403235636.5647-1-laur...@vivier.eu === TEST SCRIPT BEGIN === #!/bin/bash BASE=base n=1 total=$(git log

[Qemu-devel] [PATCH v2 13/21] unimplemented-device: Remove user_creatable flag

unimplemented-device needs to be created and mapped using create_unimplemented_device() (or equivalent code), and won't work with -device. Remove the user_creatable flag from the device class. Cc: Peter Maydell Reviewed-by: Philippe Mathieu-Daudé

[Qemu-devel] [PATCH v2 04/21] iommu: Remove FIXME comment about user_creatable=true

amd-iommu and intel-iommu are really meant to be used with -device, so they need user_creatable=true. Remove the FIXME comment. Cc: Marcel Apfelbaum Cc: "Michael S. Tsirkin" Signed-off-by: Eduardo Habkost --- Changes v1 -> v2: * (none)

Re: [Qemu-devel] [RfC PATCH 0/4] make display updates thread safe.

Hi, > -unsigned long align = 1 << (TARGET_PAGE_BITS + BITS_PER_LEVEL); > +unsigned long align = 1UL << (TARGET_PAGE_BITS + BITS_PER_LEVEL); > There were 2 issues here: without the UL suffix on align I was getting > incorrect first/last addresses since the high bits of align weren't >

Re: [Qemu-devel] [RfC PATCH 0/4] make display updates thread safe.

On Mo, 2017-04-03 at 19:02 +0200, Paolo Bonzini wrote: > > On 03/04/2017 14:03, Gerd Hoffmann wrote: > > We might clear some more bits, but these are > > outsize the visible area so they should cause visible corruption (and if > > the visible area changes the display code needs to do a full

[Qemu-devel] [PATCH v1 1/5] cadence_gem: Read the correct queue descriptor

Read the correct descriptor instead of hardcoding the first (q=0). Signed-off-by: Alistair Francis --- hw/net/cadence_gem.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hw/net/cadence_gem.c b/hw/net/cadence_gem.c index d4de8ad..17c229d

[Qemu-devel] [PATCH v1 0/5] Improve the Cadence GEM multi-queue support

Improve the Cadence GEM multi-queue support. This fixes a few bugs which were hanging around from the initial implementation. Alistair Francis (5): cadence_gem: Read the correct queue descriptor cadence_gem: Correct the multi-queue can rx logic cadence_gem: Only trigger interrupts if the

Re: [Qemu-devel] how to create threads like dataplane in qemu

On Sat, 04/01 11:54, PERSIST wrote: > Hello! > I want to create a specific thread for each process in VM so that virtio > block requests from each process can be sumbitted in the thread related to > the process. > I tried to implement it by referring to dataplane,but I can not understand >

Re: [Qemu-devel] [PATCH v3 1/1] block: pass the right options for BlockDriver.bdrv_open()

* Max Reitz [2017-03-29 23:07:22 +0200]: > On 29.03.2017 03:16, Dong Jia Shi wrote: > > raw_open() expects the caller always passing in the right actual > > @options parameter. But when trying to applying snapshot on a RBD > > image, bdrv_snapshot_goto() calls raw_open() (by

Re: [Qemu-devel] How to provide build/CI environment for NetBSD host

Hi, From: Peter Maydell , Date: Tue, 4 Apr 2017 23:30:42 +0100 > On 4 April 2017 at 23:28, Ryo ONODERA wrote: >> I use qemu from master branch (with some modification) every weekend. >> However I had never run 'make check'. >> I will run 'make

Re: [Qemu-devel] [PATCH qemu-ga] Fix a bug where qemu-ga service is stuck during stop operation

Quoting Sameeh Jubran (2017-03-21 08:59:11) > After triggering a freeze command without any following thaw command, > qemu-ga will not respond to stop operation. This behaviour is wanted on Linux > as there is no time limit for a freeze command and we want to prevent > quitting in the middle of

Re: [Qemu-devel] [Qemu-stable] [PATCH 00/81] Patch Round-up for stable 2.8.1, freeze on 2017-03-27

Hi, I'd like to ask when QEMU 2.8.1 release? According to the previous planning, It should release in Mar 30. Thanks, -Gonglei > -Original Message- > From: Qemu-stable > [mailto:qemu-stable-bounces+arei.gonglei=huawei@nongnu.org] On > Behalf Of Michael Roth > Sent: Tuesday, March

Re: [Qemu-devel] How to provide build/CI environment for NetBSD host

Hi, From: Peter Maydell , Date: Tue, 4 Apr 2017 22:43:50 +0100 > On 4 April 2017 at 22:22, Ryo ONODERA wrote: >> I saw "Warning of unsupported host systems" >> in http://wiki.qemu-project.org/ChangeLog/2.9 wiki page. >> >> I would like to

Re: [Qemu-devel] [PATCH v2 2/6] qdict: Add convenience helpers for wrapped puts

On 01/19/2017 08:38 AM, Eric Blake wrote: > On 01/19/2017 03:25 AM, Markus Armbruster wrote: >> Eric Blake writes: >> >>> Quite a few users of qdict_put() were manually wrapping a >>> non-QObject. We can make such call-sites shorter, by providing >>> common macros to do the

Re: [Qemu-devel] [PATCH qemu-ga] qemu-ga: Don't display errors to the user on thaw command

Quoting Sameeh Jubran (2017-03-21 09:14:35) > Errors that are related to ur inner implementation for the thaw command > shouldn't be displayed to the user. > > Signed-off-by: Sameeh Jubran > --- > qga/vss-win32/requester.cpp | 8 > 1 file changed, 4 insertions(+), 4

Re: [Qemu-devel] [PATCH v2 0/3] Update AppleSMC for OS X Sierra 10.12.4 guests

On Tue, Apr 04, 2017 at 09:35:00PM +0200, Alexander Graf wrote: > On 04/04/2017 07:01 PM, Gabriel L. Somlo wrote: > > As of 10.12.4 (currently the latest Sierra update), OS X refuses to boot > > unless the AppleSMC supports a third I/O port, which provides the current > > error status when read. >

Re: [Qemu-devel] How to provide build/CI environment for NetBSD host

On 4 April 2017 at 23:28, Ryo ONODERA wrote: > I use qemu from master branch (with some modification) every weekend. > However I had never run 'make check'. > I will run 'make check'. Hmm. ivshmem_server doesn't link for me, because it uses shm_open() but doesn't link with

[Qemu-devel] [PATCH v1 4/5] cadence_gem: Make the revision a property

Expose the Cadence GEM revision as a property. Signed-off-by: Alistair Francis --- hw/net/cadence_gem.c | 6 +- include/hw/net/cadence_gem.h | 1 + 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/hw/net/cadence_gem.c b/hw/net/cadence_gem.c

Re: [Qemu-devel] [PATCH] Fix Event Viewer errors caused by qemu-ga

Quoting Sameeh Jubran (2017-03-22 03:14:53) >On Tue, Mar 21, 2017 at 6:09 PM, Michael Roth > >wrote: > >> Quoting Sameeh Jubran (2017-03-21 05:49:52) >>> When the command "guest-fsfreeze-freeze" is executed it causes >>> the VSS service to log the errors below in the

[Qemu-devel] [PATCH v1 5/5] xlnx-zynqmp: Set the Cadence GEM revision

Signed-off-by: Alistair Francis --- hw/arm/xlnx-zynqmp.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/hw/arm/xlnx-zynqmp.c b/hw/arm/xlnx-zynqmp.c index bc4e66b..e41b6fe 100644 --- a/hw/arm/xlnx-zynqmp.c +++ b/hw/arm/xlnx-zynqmp.c @@ -30,6

Re: [Qemu-devel] [PATCH v2 0/3] Update AppleSMC for OS X Sierra 10.12.4 guests

On 04/04/2017 07:01 PM, Gabriel L. Somlo wrote: As of 10.12.4 (currently the latest Sierra update), OS X refuses to boot unless the AppleSMC supports a third I/O port, which provides the current error status when read. Looks much nicer after this series :). Thanks a lot! Reviewed-by:

[Qemu-devel] [PATCH v2 07/21] kvmclock: Remove user_creatable flag

kvmclock should be used by guests only when the appropriate CPUID feature flags are set on the VCPU, and it is automatically created by kvmclock_create() when those feature flags are set. This means creating a kvmclock device using -device is useless. Remove user_creatable from its device class.

[Qemu-devel] [PATCH v2 02/21] sysbus: Set user_creatable=false by default on TYPE_SYS_BUS_DEVICE

commit 33cd52b5d7b9adfd009e95f07e6c64dd88ae2a31 unset cannot_instantiate_with_device_add_yet in TYPE_SYSBUS, making all sysbus devices appear on "-device help" and lack the "no-user" flag in "info qdm". To fix this, we can set user_creatable=false by default on TYPE_SYS_BUS_DEVICE, but this

[Qemu-devel] [PATCH v2 19/21] virtio-mmio: Remove user_creatable flag

virtio-mmio needs to be wired and mapped by other device or board code, and won't work with -device. Remove the user_creatable flag from the device class. Cc: Peter Maydell Cc: Shannon Zhao Cc: "Michael S. Tsirkin"

Re: [Qemu-devel] [PATCH qemu-ga v2] qemu-ga: Make QGA VSS provider service run only when needed

Quoting Sameeh Jubran (2017-03-23 11:26:50) > Currently the service runs in background on boot even though it is not > needed and once it is running it never stops. The service needs to be > running only during freeze operation and it should be stopped after > executing thaw. > > Signed-off-by:

[Qemu-devel] [PATCH v1 3/5] cadence_gem: Only trigger interrupts if the status register is set

Only trigger multi-queue GEM interrupts if the interrupt status register is set. This logic was already used for non multi-queue interrupts but it also applies to multi-queue interrupts. Signed-off-by: Alistair Francis --- hw/net/cadence_gem.c | 2 +- 1 file

[Qemu-devel] [PATCH v1 2/5] cadence_gem: Correct the multi-queue can rx logic

Correct the buffer descriptor busy logic to work correctly when using multiple queues. Signed-off-by: Alistair Francis --- hw/net/cadence_gem.c | 18 +++--- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/hw/net/cadence_gem.c

[Qemu-devel] centos 7.2 guest doesn't boot without kvmvapic in TCG mode

I disabled kvmvapic by diff --git a/hw/intc/apic_common.c b/hw/intc/apic_common.c index c3829e3..52be2b0 100644 --- a/hw/intc/apic_common.c +++ b/hw/intc/apic_common.c @@ -440,7 +440,7 @@ static const VMStateDescription vmstate_apic_common = { static Property apic_properties_common[] = {

[Qemu-devel] [PATCH]Enable kvmvapic only when host doesn't support VAPIC capability in KVM mode

In KVM mode, enable kvmvapic only when host doesn't support VAPIC capability. Save the time to set up kvmvapic in some hosts. Signed-off -by: Anthony Xu diff --git a/hw/intc/apic_common.c b/hw/intc/apic_common.c index c3829e3..d5c53af 100644 --- a/hw/intc/apic_common.c

Re: [Qemu-devel] [RFC] migration/block:limit the time used for block migration

On Wed, Mar 29, 2017 at 11:57 PM, Juan Quintela wrote: > > 858585 jemmy wrote: > > On Tue, Mar 28, 2017 at 5:47 PM, Juan Quintela wrote: > >> Lidong Chen wrote: > >>> when migration with quick speed,

Re: [Qemu-devel] [Qemu-stable] [PATCH 00/81] Patch Round-up for stable 2.8.1, freeze on 2017-03-27

Quoting Gonglei (Arei) (2017-04-04 21:01:54) > Hi, > > I'd like to ask when QEMU 2.8.1 release? According to the previous planning, > It should release in Mar 30. It's already been released :) https://lists.nongnu.org/archive/html/qemu-devel/2017-03/msg06332.html > > Thanks, > -Gonglei > >

Re: [Qemu-devel] [Qemu-stable] [PATCH 00/81] Patch Round-up for stable 2.8.1, freeze on 2017-03-27

> > > > > > > > -Original Message- > > > From: Michael Roth [mailto:mdr...@linux.vnet.ibm.com] > > > Sent: Wednesday, April 05, 2017 12:09 PM > > > To: Gonglei (Arei); qemu-devel@nongnu.org > > > Cc: qemu-sta...@nongnu.org > > > Subject: RE: [Qemu-stable] [PATCH 00/81] Patch Round-up for

Re: [Qemu-devel] [PATCH kernel v8 2/4] virtio-balloon: VIRTIO_BALLOON_F_CHUNK_TRANSFER

On Thursday, March 16, 2017 3:09 PM Wei Wang wrote: > The implementation of the current virtio-balloon is not very efficient, > because > the ballooned pages are transferred to the host one by one. Here is the > breakdown of the time in percentage spent on each step of the balloon > inflating >

Re: [Qemu-devel] [Qemu-stable] [PATCH 00/81] Patch Round-up for stable 2.8.1, freeze on 2017-03-27

Hi Michael, > -Original Message- > From: Michael Roth [mailto:mdr...@linux.vnet.ibm.com] > Sent: Wednesday, April 05, 2017 12:09 PM > To: Gonglei (Arei); qemu-devel@nongnu.org > Cc: qemu-sta...@nongnu.org > Subject: RE: [Qemu-stable] [PATCH 00/81] Patch Round-up for stable 2.8.1, >

Re: [Qemu-devel] [Qemu-stable] [PATCH 00/81] Patch Round-up for stable 2.8.1, freeze on 2017-03-27

Quoting Gonglei (Arei) (2017-04-04 23:51:26) > Hi Michael, > > > > -Original Message- > > From: Michael Roth [mailto:mdr...@linux.vnet.ibm.com] > > Sent: Wednesday, April 05, 2017 12:09 PM > > To: Gonglei (Arei); qemu-devel@nongnu.org > > Cc: qemu-sta...@nongnu.org > > Subject: RE:

Re: [Qemu-devel] [PATCH v5 0/9] ppc/pnv: interrupt controller (POWER8)

On Mon, Apr 03, 2017 at 09:45:56AM +0200, Cédric Le Goater wrote: > Hello, > > Here is a series adding support for the interrupt controller as found > on a POWER8 system. POWER9 uses a different interrupt controller > called XIVE, still to be worked on. > > The initial patches are more cleanups

Re: [Qemu-devel] [RFC 02/19] s390: Add FIXME for unexplained user_creatable=false line

On Mon, 3 Apr 2017 16:20:11 -0300 Eduardo Habkost wrote: > On Mon, Apr 03, 2017 at 10:55:38AM +0200, Cornelia Huck wrote: > > On Fri, 31 Mar 2017 21:46:07 -0300 > > Eduardo Habkost wrote: > > > > > TYPE_S390_PCI_HOST_BRIDGE has user_creatable=false but

Re: [Qemu-devel] [RFC 03/19] sysbus: Set user_creatable=false by default on TYPE_SYS_BUS_DEVICE

On 04.04.2017 08:53, Alexander Graf wrote: > > > On 03.04.17 23:00, Eduardo Habkost wrote: >> On Mon, Apr 03, 2017 at 10:15:44PM +0200, Alexander Graf wrote: >>> >>> >>> On 03.04.17 22:10, Eduardo Habkost wrote: On Mon, Apr 03, 2017 at 08:49:16PM +0100, Peter Maydell wrote: > On 1 April

Re: [Qemu-devel] [RFC 13/19] unimplemented-device: Remove user_creatable flag

On 03.04.2017 22:05, Eduardo Habkost wrote: > On Mon, Apr 03, 2017 at 08:42:12PM +0100, Peter Maydell wrote: >> On 3 April 2017 at 19:30, Eduardo Habkost wrote: >>> On Mon, Apr 03, 2017 at 03:08:06PM +0100, Peter Maydell wrote: On 3 April 2017 at 14:54, Eduardo Habkost

Re: [Qemu-devel] [PATCH 0/7] Provide support for the software TPM emulator

* Patrick Ohly (patrick.o...@intel.com) wrote: > On Mon, 2017-04-03 at 18:38 +0100, Dr. David Alan Gilbert wrote: > > Or you could just remove the spawning code and use existing sockets; less > > code! > > That would be harder to use reliably in the automated testing that this > feature is

Re: [Qemu-devel] [PATCH v1 2/3] applesmc: consolidate port i/o into single contiguous region

On 04/04/2017 02:04 AM, Gabriel L. Somlo wrote: On Mon, Apr 03, 2017 at 12:27:15PM +0200, Paolo Bonzini wrote: On 03/04/2017 11:32, Alexander Graf wrote: Newer AppleSMC revisions support an error status (read) port in addition to the data and command ports currently supported. Register the

Re: [Qemu-devel] [RFC 13/19] unimplemented-device: Remove user_creatable flag

> Am 04.04.2017 um 09:05 schrieb Thomas Huth : > >> On 03.04.2017 22:05, Eduardo Habkost wrote: >>> On Mon, Apr 03, 2017 at 08:42:12PM +0100, Peter Maydell wrote: On 3 April 2017 at 19:30, Eduardo Habkost wrote: > On Mon, Apr 03, 2017 at

Re: [Qemu-devel] nbd: Possible regression in 2.9 RCs

Hi, On 03.04.2017 21:52, Kashyap Chamarthy wrote: On Fri, Mar 31, 2017 at 05:49:52PM +, Ciprian Barbu wrote: Hi, [...] We also use libvirt v1.3.4, which might be a problem, but at least we want to understand if the commit in question introduced an obvious problem or if it's all in the

[Qemu-devel] qemu_savevm_state_header()

Hi I am new in qemu vm live migration. what does 'qemu_savevm_state_header()' fuction do? thanks

Re: [Qemu-devel] [Bug 1679358] [NEW] ARM: SCTLR fields not being preserved

On 3 April 2017 at 23:17, Yifan wrote: > There are fields in SCTLR that are RAO/SBOP or WI or in the case of the > RR field, accessible only in secure mode. Currently it seems that qemu > just propagates any write to SCTLR to the register and this screwed up > in a bootloader

Re: [Qemu-devel] [RFC PATCH v1 0/9] MTTCG and record/replay fixes for rc3

Paolo Bonzini writes: > On 03/04/2017 14:45, Alex Bennée wrote: >> cpus: check cpu->running in cpu_get_icount_raw() >> >> I'm not sure the race happens and once outside of cpu->running the >> icount counters should be zero. However it seems a sensible >> precaution.

Re: [Qemu-devel] [PATCH] win32: replace custom mutex and condition variable with native primitives

On Mon, 3 Apr 2017 18:12:34 + Andrew Baumann wrote: > > From: Cornelia Huck [mailto:cornelia.h...@de.ibm.com] > > Sent: Monday, 3 April 2017 7:20 > > > > On Fri, 24 Mar 2017 15:01:41 -0700 > > Andrew Baumann wrote: > > > > >

Re: [Qemu-devel] [RFC 03/19] sysbus: Set user_creatable=false by default on TYPE_SYS_BUS_DEVICE

On 03.04.17 23:00, Eduardo Habkost wrote: On Mon, Apr 03, 2017 at 10:15:44PM +0200, Alexander Graf wrote: On 03.04.17 22:10, Eduardo Habkost wrote: On Mon, Apr 03, 2017 at 08:49:16PM +0100, Peter Maydell wrote: On 1 April 2017 at 01:46, Eduardo Habkost wrote: commit

Re: [Qemu-devel] [RFC 03/19] sysbus: Set user_creatable=false by default on TYPE_SYS_BUS_DEVICE

On 04.04.17 08:58, Thomas Huth wrote: On 04.04.2017 08:53, Alexander Graf wrote: On 03.04.17 23:00, Eduardo Habkost wrote: On Mon, Apr 03, 2017 at 10:15:44PM +0200, Alexander Graf wrote: On 03.04.17 22:10, Eduardo Habkost wrote: On Mon, Apr 03, 2017 at 08:49:16PM +0100, Peter Maydell

Re: [Qemu-devel] nbd: Possible regression in 2.9 RCs

Hi, On 03.04.2017 22:44, Eric Blake wrote: On 04/03/2017 07:39 AM, Max Reitz wrote: As for just allowing the NBD server write access to the device... To me that appears pretty difficult from an implementation perspective. We assert that nobody can write without having requested write access

Re: [Qemu-devel] [RFC PATCH v1 7/9] cpus: move icount preparation out of tcg_exec_cpu

Pavel Dovgalyuk writes: > I guess you are trying to fix the sympthoms of the case > when iothread is trying to access instruction count. In theory the main-loop should be sequenced before or after vCPU events because of the BQL. I'm not sure why this is not currently the

Re: [Qemu-devel] [PATCH v4 0/4] X86/HMP: Expose x86 model specific registers via human monitor

ping I kindly request your comments. On 29.03.2017 20:30, Julian Kirsch wrote: > Provide read/write access to x86 model specific registers (MSRs) by means of > two new HMP commands "msr_get" and "msr_set". The rationale behind this > is to improve introspection capabilities for system

[Qemu-devel] [PATCH v2 0/1] qga: Add 'guest-get-host-name' command

From: Vinzenz Feenstra Since v1: - Renamed from FQDN to hostname and expanded documentation Vinzenz Feenstra (1): qga: Add 'guest-get-host-name' command qga/commands.c | 11 +++ qga/qapi-schema.json | 29 + 2 files changed, 40

[Qemu-devel] [PATCH v2 1/1] qga: Add 'guest-get-host-name' command

From: Vinzenz Feenstra Retrieving the guest host name is a very useful feature for virtual management systems. This information can help to have more user friendly VM access details, instead of an IP there would be the host name. Also the host name reported can be used to

Re: [Qemu-devel] [PATCH v5] qga: Add `guest-get-timezone` command

Ping > On Mar 23, 2017, at 12:39 PM, Vinzenz 'evilissimo' Feenstra > wrote: > > From: Vinzenz Feenstra > > Adds a new command `guest-get-timezone` reporting the currently > configured timezone on the system. The information on what timezone is >

Re: [Qemu-devel] [PATCH v2 1/3] libqtest: Ignore QMP events when parsing the response for HMP commands

On 03.04.2017 21:09, John Snow wrote: > > > On 03/30/2017 03:50 AM, Thomas Huth wrote: >> When running certain HMP commands (like "device_del") via QMP, we >> can sometimes get a QMP event in the response first, so that the >> "g_assert(ret)" statement in qtest_hmp() triggers and the test >>

Re: [Qemu-devel] [PATCH v5] qga: Add `guest-get-timezone` command

I have tested the patch on Windows 2012 R2 Reviewed-by: Sameeh Jubran Tested-by: Sameeh Jubran On Thu, Mar 23, 2017 at 2:39 PM, Vinzenz 'evilissimo' Feenstra < vfeen...@redhat.com> wrote: > From: Vinzenz Feenstra > > Adds a new

Re: [Qemu-devel] [RfC PATCH 0/4] make display updates thread safe.

On 04/04/17 07:12, Gerd Hoffmann wrote: > Hi, > >> -unsigned long align = 1 << (TARGET_PAGE_BITS + BITS_PER_LEVEL); >> +unsigned long align = 1UL << (TARGET_PAGE_BITS + BITS_PER_LEVEL); > >> There were 2 issues here: without the UL suffix on align I was getting >> incorrect first/last

[Qemu-devel] [PATCH 06/10] cg3: fix up size parameter for memory_region_get_dirty()

From: Mark Cave-Ayland The code was incorrectly calculating the end address rather than the size of the required region. Signed-off-by: Mark Cave-Ayland --- hw/display/cg3.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[Qemu-devel] [PATCH 01/10] bitmap: add bitmap_copy_and_clear_atomic

Signed-off-by: Gerd Hoffmann --- include/qemu/bitmap.h | 2 ++ util/bitmap.c | 11 +++ 2 files changed, 13 insertions(+) diff --git a/include/qemu/bitmap.h b/include/qemu/bitmap.h index 63ea2d0..c318da1 100644 --- a/include/qemu/bitmap.h +++

[Qemu-devel] [PATCH 05/10] cg3: remove TARGET_PAGE_SIZE rounding on dirty page detection

From: Mark Cave-Ayland This was an artifact from very early versions of the code from before the memory API and is no longer needed. Signed-off-by: Mark Cave-Ayland --- hw/display/cg3.c | 5 ++--- 1 file changed, 2 insertions(+), 3

[Qemu-devel] [PATCH 07/10] cg3: make display updates thread safe

From: Mark Cave-Ayland Signed-off-by: Mark Cave-Ayland --- hw/display/cg3.c | 37 +++-- 1 file changed, 19 insertions(+), 18 deletions(-) diff --git a/hw/display/cg3.c b/hw/display/cg3.c index

[Qemu-devel] [PATCH 09/10] tcx: make display updates thread safe

From: Mark Cave-Ayland Signed-off-by: Mark Cave-Ayland --- hw/display/tcx.c | 85 +++- 1 file changed, 29 insertions(+), 56 deletions(-) diff --git a/hw/display/tcx.c

Re: [Qemu-devel] [PATCH 02/10] memory: add support getting and using a dirty bitmap copy.

On 04/04/2017 12:23, Gerd Hoffmann wrote: > > memory_region_copy_and_clear_dirty() will create a copy of the dirty > bitmap for the specified range, clear the dirty bitmap and return the > copy. The returned bitmap can be a bit larger than requested, the range > is expanded so the code can

Re: [Qemu-devel] [PATCH v3 0/3] hw/arm/exynos: Minor cleanups

On 13 March 2017 at 18:47, Krzysztof Kozlowski wrote: > Hi, > > Minor cleanups, no dependencies. > > Changes since v1 > > 1. Patch 1/3: Address missed Philippe's comments about error reporting >verbosity. > > Changes since v2 > > 1. Patch

Re: [Qemu-devel] [PATCH v2] hw/misc: Add Exynos4210 Pseudo Random Number Generator

On 18 March 2017 at 19:25, Krzysztof Kozlowski wrote: > Add emulation for Exynos4210 Pseudo Random Number Generator which could > work on fixed seeds or with seeds provided by True Random Number > Generator block inside the SoC. > > Implement only the fixed seeds part of it in

Re: [Qemu-devel] [PATCH 0/7] Provide support for the software TPM emulator

On 04/03/2017 01:07 PM, Daniel P. Berrange wrote: On Fri, Mar 31, 2017 at 04:10:09PM +0300, Amarnath Valluri wrote: Briefly, Theses set of patches introduces: - new TPM backend driver to support software TPM emulators(swtpm(1)). - and few supported fixes/enhancements/cleanup to existing tpm

Re: [Qemu-devel] [Qemu-trivial] [PATCH v5] util: Use g_malloc/g_free in envlist.c

On 03/28/2017 10:47 AM, Peter Maydell wrote: On 28 March 2017 at 14:44, Philippe Mathieu-Daudé wrote: Hi Saurav, you should read the QEMU Coding Style and replace your tabs by 4 spaces. Er, in review comments on v3 we said not to do that... oops I missed Stefan comment in

Re: [Qemu-devel] [RFC PATCH v1 7/9] cpus: move icount preparation out of tcg_exec_cpu

On 04/04/2017 12:46, Alex Bennée wrote: >> In theory the main-loop should be sequenced before or after vCPU events >> because of the BQL. I'm not sure why this is not currently the case. > > It seems cpu_handle_exception doesn't take the BQL until > replay_exception() has done its thing. This

Re: [Qemu-devel] nbd: Possible regression in 2.9 RCs

On 04/04/2017 10:17, ciprian.barbu wrote: >> >> but we do NOT make any guarantees of supporting >> >> new qemu, old libvirt > > Sounds reasonable enough, I guess we didn't look at it this way. Yes, but usually it's "new qemu, very old libvirt", like several years old. I think this should be

Re: [Qemu-devel] [PATCH 2/7] tpm-backend: Move thread handling inside TPMBackend

On 04.04.2017 13:56, Marc-André Lureau wrote: Hi On Fri, Mar 31, 2017 at 5:04 PM Amarnath Valluri > wrote: Move thread handling inside TPMBackend, this way backend implementations need not to maintain their own

Re: [Qemu-devel] [PATCH v3 1/1] slirp: add SOCKS5 support

Hi Laurent, I waited this feature for long and excited to try it soon :) Please find some comments inline. On 04/03/2017 08:56 PM, Laurent Vivier wrote: When the VM is used behind a firewall, This allows the use of a SOCKS5 proxy server to connect the VM IP stack directly to the Internet.

Re: [Qemu-devel] [Qemu-trivial] [PATCH v5] util: Use g_malloc/g_free in envlist.c

On 03/20/2017 02:38 PM, Saurav Sachidanand wrote: Change malloc/strdup/free to g_malloc/g_strdup/g_free in util/envlist.c. Remove NULL checks for pointers returned from g_malloc and g_strdup as they exit in case of failure. Also, update calls to envlist_create to reflect this. Free array and

[Qemu-devel] [PATCH 02/10] memory: add support getting and using a dirty bitmap copy.

This patch adds support for getting and using a local copy of the dirty bitmap. memory_region_copy_and_clear_dirty() will create a copy of the dirty bitmap for the specified range, clear the dirty bitmap and return the copy. The returned bitmap can be a bit larger than requested, the range is

  1   2   3   >