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 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] [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] [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] [PATCH kernel v8 2/4] virtio-balloon: VIRTIO_BALLOON_F_CHUNK_TRANSFER

On Wednesday, April 5, 2017 11:54 AM, Michael S. Tsirkin wrote: > On Wed, Apr 05, 2017 at 03:31:36AM +, Wang, Wei W wrote: > > 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

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] [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] [PATCH kernel v8 2/4] virtio-balloon: VIRTIO_BALLOON_F_CHUNK_TRANSFER

On Wed, Apr 05, 2017 at 03:31:36AM +, Wang, Wei W wrote: > 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

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] [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] [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 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 >

[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] [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. >

[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 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] [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 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] [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

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

[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

[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 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 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:

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] 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] 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

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] 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] 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] 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

[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

[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 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 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] [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:

[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 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"

[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 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 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 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)

[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] [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 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 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 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 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 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 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"

[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 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 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

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

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:

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

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

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 >

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 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 v11 0/2] block/vxhs.c: Add support for a new block device type called "vxhs"

On Mon, Apr 03, 2017 at 08:48:07PM -0700, Ashish Mittal wrote: > - Veritas HyperScale block driver in QEMU is designed to provide an > accelerated > IO path from KVM virtual machines to Veritas HyperScale storage service. > > - A network IO transfer library that translates block IO from

Re: [Qemu-devel] [PATCH 1/2] userfault: add pid into uffd_msg

* Alexey Perevalov (a.pereva...@samsung.com) wrote: > Signed-off-by: Alexey Perevalov > --- > linux-headers/linux/userfaultfd.h | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/linux-headers/linux/userfaultfd.h > b/linux-headers/linux/userfaultfd.h > index

Re: [Qemu-devel] [PATCH 42/51] ram: Pass RAMBlock to bitmap_sync

"Dr. David Alan Gilbert" wrote: > * Juan Quintela (quint...@redhat.com) wrote: >> "Dr. David Alan Gilbert" wrote: >> > * Juan Quintela (quint...@redhat.com) wrote: >> >> We change the meaning of start to be the offset from the beggining of >> >> the

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

"Dr. David Alan Gilbert" wrote: > * Juan Quintela (quint...@redhat.com) wrote: Hi >> @@ -1191,19 +1204,18 @@ static bool get_queued_page(RAMState *rs, >> MigrationState *ms, >> * >> * It should be empty at the end anyway, but in error cases there may >> * xbe some

Re: [Qemu-devel] [RFC PATCH v1 4/9] target/i386/misc_helper: wrap BQL around another IRQ generator

On Tue, Apr 04, 2017 at 09:53:15AM -0700, Richard Henderson wrote: > On 04/03/2017 05:45 AM, Alex Bennée wrote: > > Anything that calls into HW emulation must be protected by the BQL. > > > > Signed-off-by: Alex Bennée > > --- > > target/i386/misc_helper.c | 3 +++ > > 1

Re: [Qemu-devel] [PATCH v2 00/51] Creating RAMState for migration

* Juan Quintela (quint...@redhat.com) wrote: > "Dr. David Alan Gilbert" wrote: > > * Juan Quintela (quint...@redhat.com) wrote: > >> Hi > > > > Some high level points: > > > >> Continuation of previous series, all review comments addressed. New things: > >> - Consolidate all

Re: [Qemu-devel] [PATCH RFC] hw/pvrdma: Proposal of a new pvrdma device

On Tue, Apr 04, 2017 at 04:38:40PM +0300, Marcel Apfelbaum wrote: > On 04/03/2017 09:23 AM, Leon Romanovsky wrote: > > On Fri, Mar 31, 2017 at 06:45:43PM +0300, Marcel Apfelbaum wrote: > > > On 03/30/2017 11:28 PM, Doug Ledford wrote: > > > > On 3/30/17 9:13 AM, Leon Romanovsky wrote: > > > > > On

Re: [Qemu-devel] [PULL 0/2] 9pfs fixes for 2.9 2017-04-04

On 4 April 2017 at 17:13, Greg Kurz wrote: > The following changes since commit 87cc4c61020addea6a001b94b662596b1896d1b3: > > Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into > staging (2017-04-04 11:40:55 +0100) > > are available in the git repository at:

Re: [Qemu-devel] [PATCH v2 00/51] Creating RAMState for migration

"Dr. David Alan Gilbert" wrote: > * Juan Quintela (quint...@redhat.com) wrote: >> Hi > > Some high level points: > >> Continuation of previous series, all review comments addressed. New things: >> - Consolidate all function comments in the same style (yes, docs) >> - Be much

Re: [Qemu-devel] [PATCH 01/51] ram: Update all functions comments

"Dr. David Alan Gilbert" wrote: > * Juan Quintela (quint...@redhat.com) wrote: >> Added doc comments for existing functions comment and rewrite them in >> a common style. >> >> Signed-off-by: Juan Quintela >> --- >> migration/ram.c | 348 >>

[Qemu-devel] [PATCH v2 2/3] applesmc: implement error status port

As of release 10.12.4, OS X (Sierra) refuses to boot unless the AppleSMC supports an additional I/O port, expected to provide an error status code. Update the [cmd|data]_write() and data_read() methods to implement the required state machine, and add I/O region & methods to handle access to the

[Qemu-devel] [PATCH v2 1/3] applesmc: cosmetic whitespace and indentation cleanup

Signed-off-by: Gabriel Somlo Reviewed-by: Alexander Graf Reviewed-by: Philippe Mathieu-Daudé --- hw/misc/applesmc.c | 98 -- 1 file changed, 50 insertions(+), 48 deletions(-) diff --git

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

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. New since v1: - 1/3: don't touch the default OSK string, as it's unnecessary at this time -

[Qemu-devel] [PATCH v2 3/3] applesmc: fix port i/o access width

Set width of the two i/o regions dedicated to the AppleSMC's 8-bit data and command ports to 1 byte. Signed-off-by: Gabriel Somlo --- Setting these to 1-byte width works fine on any OS X version I could find to test on: 10.(6-12), inclusive. On linux, the applesmc kernel

Re: [Qemu-devel] [PULL 0/1] pci: fix

On 4 April 2017 at 16:35, Michael S. Tsirkin wrote: > The following changes since commit 87cc4c61020addea6a001b94b662596b1896d1b3: > > Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into > staging (2017-04-04 11:40:55 +0100) > > are available in the git

Re: [Qemu-devel] [RFC PATCH v1 6/9] cpus: check cpu->running in cpu_get_icount_raw()

On 04/03/2017 05:45 AM, Alex Bennée wrote: The lifetime of current_cpu is now the lifetime of the vCPU thread. However get_icount_raw() can apply a fudge factor if called while code is running to take into account the current executed instruction count. To ensure this is always the case we also

Re: [Qemu-devel] [RFC PATCH v1 5/9] cpus: remove icount handling from qemu_tcg_cpu_thread_fn

On 04/03/2017 05:45 AM, Alex Bennée wrote: We should never be running in multi-threaded mode with icount enabled. There is no point calling handle_icount_deadline here so remove it and assert !use_icount. Signed-off-by: Alex Bennée --- cpus.c | 4 ++-- 1 file changed,

Re: [Qemu-devel] [RFC PATCH v1 4/9] target/i386/misc_helper: wrap BQL around another IRQ generator

On 04/03/2017 05:45 AM, Alex Bennée wrote: Anything that calls into HW emulation must be protected by the BQL. Signed-off-by: Alex Bennée --- target/i386/misc_helper.c | 3 +++ 1 file changed, 3 insertions(+) Reviewed-by: Richard Henderson r~

Re: [Qemu-devel] [PULL v1 0/2] Merge qio 2017/04/04 v1

On 4 April 2017 at 16:20, Daniel P. Berrange wrote: > The following changes since commit 87cc4c61020addea6a001b94b662596b1896d1b3: > > Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into > staging (2017-04-04 11:40:55 +0100) > > are available in the git

Re: [Qemu-devel] [PATCH v3 02/21] mux: simplfy muxes_realize_done

Hi Philippe - Original Message - > Hi Marc-André, > > On 03/16/2017 06:21 AM, Marc-André Lureau wrote: > > mux_chr_event() already send events to all backends, rename it, > > export it, and use it from muxes_realize_done. This should help abstract > > away mux implementation. > > > >

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

On 04/04/2017 11:43 AM, Daniel P. Berrange wrote: On Mon, Apr 03, 2017 at 05:18:37PM +, Marc-André Lureau wrote: Hi On Mon, Apr 3, 2017 at 7:08 PM Daniel P. Berrange wrote: On Fri, Mar 31, 2017 at 04:10:09PM +0300, Amarnath Valluri wrote: Briefly, Theses set of

Re: [Qemu-devel] [PATCH 7/7] tpm: New backend driver to support TPM emulator

Hi (just a quick review, there will be more once the design discussion is over) On Fri, Mar 31, 2017 at 5:03 PM Amarnath Valluri wrote: > This change introduces a new TPM backend driver that can communicates with > communicate > swtpm(software TPM emulator) using

[Qemu-devel] [PULL 2/2] 9pfs: clear migration blocker at session reset

The migration blocker survives a device reset: if the guest mounts a 9p share and then gets rebooted with system_reset, it will be unmigratable until it remounts and umounts the 9p share again. This happens because the migration blocker is supposed to be cleared when we put the last reference on

[Qemu-devel] [PULL 1/2] 9pfs: fix multiple flush for same request

If a client tries to flush the same outstanding request several times, only the first flush completes. Subsequent ones keep waiting for the request completion in v9fs_flush() and, therefore, leak a PDU. This will cause QEMU to hang when draining active PDUs the next time the device is reset. Let

[Qemu-devel] [PULL 0/2] 9pfs fixes for 2.9 2017-04-04

The following changes since commit 87cc4c61020addea6a001b94b662596b1896d1b3: Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2017-04-04 11:40:55 +0100) are available in the git repository at: https://github.com/gkurz/qemu.git tags/for-upstream for you to

Re: [Qemu-devel] [PATCH RFC] hw/pvrdma: Proposal of a new pvrdma device

On Tue, Apr 04, 2017 at 04:38:40PM +0300, Marcel Apfelbaum wrote: > Here are some thoughts regarding the Soft RoCE usage in our project. > We thought about using it as backend for QEMU pvrdma device > we didn't how it will support our requirements. > > 1. Does Soft RoCE support inter process

Re: [Qemu-devel] [PATCH v11 1/2] block/vxhs.c: Add support for a new block device type called "vxhs"

On Mon, Apr 03, 2017 at 08:48:08PM -0700, Ashish Mittal wrote: > Source code for the qnio library that this code loads can be downloaded from: > https://github.com/VeritasHyperScale/libqnio.git > > Sample command line using JSON syntax: > ./x86_64-softmmu/qemu-system-x86_64 -name

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

* Paolo Bonzini (pbonz...@redhat.com) wrote: > > > > > So I'm inclined _not_ to take your patch. One possibility could be to > > > do the following: > > > > > > - for throttling between 0% and 80%, use the current algorithm. At 66%, > > > the CPU will work for 10 ms and sleep for 40 ms. > > >

[Qemu-devel] [PULL 0/1] pci: fix

The following changes since commit 87cc4c61020addea6a001b94b662596b1896d1b3: Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2017-04-04 11:40:55 +0100) are available in the git repository at: git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git

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

On Mon, Apr 03, 2017 at 05:18:37PM +, Marc-André Lureau wrote: > Hi > > On Mon, Apr 3, 2017 at 7:08 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

[Qemu-devel] [RFC PATCH for-2.9] block: Ignore guest dev permissions during incoming migration

Usually guest devices don't like other writers to the same image, so they use blk_set_perm() to prevent this from happening. In the migration phase before the VM is actually running, though, they don't have a problem with writes to the image. On the other hand, storage migration needs to be able

[Qemu-devel] [PULL 1/1] pci: Only unmap bus_master_enabled_region if was added previously

From: Alexey Kardashevskiy Normally pci_init_bus_master() would be called either via bus->machine_done.notify or directly from do_pci_register_device(). However if a device's realize() failed, pci_init_bus_master() is not called, and do_pci_unregister_device() fails on

Re: [Qemu-devel] PCI regression in 2.9

On Tue, Apr 04, 2017 at 11:30:13AM -0400, Jeff Cody wrote: > > I ran into this while running qemu iotests, and it looks like it is a > regression from 2.8. > > Here is the reproducer: > > $ ./x86_64-softmmu/qemu-system-x86_64 -drive if=virtio > qemu-system-x86_64: qemu-kvm/memory.c:2078:

[Qemu-devel] PCI regression in 2.9

I ran into this while running qemu iotests, and it looks like it is a regression from 2.8. Here is the reproducer: $ ./x86_64-softmmu/qemu-system-x86_64 -drive if=virtio qemu-system-x86_64: qemu-kvm/memory.c:2078: memory_region_del_subregion: Assertion `subregion->container == mr' failed

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

Well, I wouldn't object to a patch to fix it (it would have to correctly handle the various different versions of the CPU architecture we implement, etc), but I'm not planning on writing one today myself. -- You received this bug notification because you are a member of qemu- devel-ml, which is

[Qemu-devel] [PULL v1 1/2] io: fix incoming client socket initialization

From: Wang guang The channel socket was initialized manually, but forgot to set QIO_CHANNEL_FEATURE_SHUTDOWN. Thus, the colo_process_incoming_thread would hang at recvmsg. This patch just call qio_channel_socket_new to get channel, Which set QIO_CHANNEL_FEATURE_SHUTDOWN

[Qemu-devel] [PULL v1 0/2] Merge qio 2017/04/04 v1

The following changes since commit 87cc4c61020addea6a001b94b662596b1896d1b3: Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2017-04-04 11:40:55 +0100) are available in the git repository at: git://github.com/berrange/qemu tags/pull-qio-2017-04-04-1 for you

[Qemu-devel] [PULL v1 2/2] io: fix FD socket handling in DNS lookup

The qio_dns_resolver_lookup_sync() method is required to be a no-op for socket kinds that don't require name resolution. Thus the KIND_FD handling should not return an error. Signed-off-by: Daniel P. Berrange --- io/dns-resolver.c | 5 + 1 file changed, 1 insertion(+),

  1   2   3   >