Re: [Qemu-devel] [RFC v2 0/2] kvm "fake DAX" device flushing

2018-06-03 Thread Pankaj Gupta
Hi Igor, > > [...] > > - Qemu virtio-pmem device > > It exposes a persistent memory range to KVM guest which > > at host side is file backed memory and works as persistent > > memory device. In addition to this it provides virtio > > device handling of flushing interface. KVM guest

Re: [Qemu-devel] [PATCH V8 01/17] filter-rewriter: fix memory leak for connection in connection_track_table

2018-06-03 Thread Jason Wang
On 2018年06月03日 13:05, Zhang Chen wrote: After a net connection is closed, we didn't clear its releated resources in connection_track_table, which will lead to memory leak. Let't track the state of net connection, if it is closed, its related resources will be cleared up. Signed-off-by:

Re: [Qemu-devel] [RFC v2 2/4] tests: iotests: don't compare SHUTDOWN event

2018-06-03 Thread Peter Xu
On Thu, May 31, 2018 at 09:42:23AM -0500, Eric Blake wrote: > On 05/31/2018 12:16 AM, Peter Xu wrote: > > This event is not really necessary. After OOB series it might affect > > the timing of the script so this event may or may not be there comparing > > to the old *.out results. Let's just

[Qemu-devel] [Bug 1025244] Re: qcow2 image increasing disk size above the virtual limit

2018-06-03 Thread Launchpad Bug Tracker
[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: qemu-kvm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1025244] Re: qcow2 image increasing disk size above the virtual limit

2018-06-03 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/1025244 Title: qcow2

[Qemu-devel] [Bug 1426092] Re: virtio-balloon-device locks up Guest

2018-06-03 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/1426092 Title:

Re: [Qemu-devel] [PULL 0/5] Migration pull request

2018-06-03 Thread no-reply
Hi, This series seems to have some coding style problems. See output below for more information: Type: series Message-id: 20180604042156.13812-1-quint...@redhat.com Subject: [Qemu-devel] [PULL 0/5] Migration pull request === TEST SCRIPT BEGIN === #!/bin/bash BASE=base n=1 total=$(git log

[Qemu-devel] [PULL 5/5] migration: not wait RDMA_CM_EVENT_DISCONNECTED event after rdma_disconnect

2018-06-03 Thread Juan Quintela
From: Lidong Chen When cancel migration during RDMA precopy, the source qemu main thread hangs sometime. The backtrace is: (gdb) bt #0 0x7f249eabd43d in write () from /lib64/libpthread.so.0 #1 0x7f24a1ce98e4 in rdma_get_cm_event (channel=0x4675d10, event=0x7ffe2f643dd0)

[Qemu-devel] [PULL 4/5] migration: remove unnecessary variables len in QIOChannelRDMA

2018-06-03 Thread Juan Quintela
From: Lidong Chen Because qio_channel_rdma_writev and qio_channel_rdma_readv maybe invoked by different threads concurrently, this patch removes unnecessary variables len in QIOChannelRDMA and use local variable instead. Signed-off-by: Lidong Chen Reviewed-by: Dr. David Alan Gilbert

[Qemu-devel] [PULL 3/5] migration: Don't activate block devices if using -S

2018-06-03 Thread Juan Quintela
From: "Dr. David Alan Gilbert" Activating the block devices causes the locks to be taken on the backing file. If we're running with -S and the destination libvirt hasn't started the destination with 'cont', it's expecting the locks are still untaken. Don't activate the block devices if we're

[Qemu-devel] [PULL 2/5] migration: discard non-migratable RAMBlocks

2018-06-03 Thread Juan Quintela
From: Cédric Le Goater On the POWER9 processor, the XIVE interrupt controller can control interrupt sources using MMIO to trigger events, to EOI or to turn off the sources. Priority management and interrupt acknowledgment is also controlled by MMIO in the presenter sub-engine. These MMIO

[Qemu-devel] [PULL 0/5] Migration pull request

2018-06-03 Thread Juan Quintela
The following changes since commit 392fba9f583223786f844dce9b2e7f9a0ce0147a: Merge remote-tracking branch 'remotes/stsquad/tags/pull-travis-updates-010618-1' into staging (2018-06-01 17:32:30 +0100) are available in the Git repository at: git://github.com/juanquintela/qemu.git

[Qemu-devel] [PULL 1/5] migration: introduce decompress-error-check

2018-06-03 Thread Juan Quintela
From: Xiao Guangrong QEMU 3.0 enables strict check for compression & decompression to make the migration more robust, that depends on the source to fix the internal design which triggers the unexpected error conditions To make it work for migrating old version QEMU to 2.13 QEMU, we introduce

Re: [Qemu-devel] [PATCH v2 for 2.13] migration: Don't activate block devices if using -S

2018-06-03 Thread Juan Quintela
"Dr. David Alan Gilbert (git)" wrote: > From: "Dr. David Alan Gilbert" > > Activating the block devices causes the locks to be taken on > the backing file. If we're running with -S and the destination libvirt > hasn't started the destination with 'cont', it's expecting the locks are > still

Re: [Qemu-devel] [PATCH v4] migration: discard non-migratable RAMBlocks

2018-06-03 Thread Juan Quintela
Cédric Le Goater wrote: > On the POWER9 processor, the XIVE interrupt controller can control > interrupt sources using MMIO to trigger events, to EOI or to turn off > the sources. Priority management and interrupt acknowledgment is also > controlled by MMIO in the presenter sub-engine. > > These

[Qemu-devel] [PATCH qemu v4] memory/hmp: Print owners/parents in "info mtree"

2018-06-03 Thread Alexey Kardashevskiy
This adds owners/parents (which are the same, just occasionally owner==NULL) printing for memory regions; a new '-o' flag enabled new output. Signed-off-by: Alexey Kardashevskiy --- The only orphan object I know is printed now as: - (prio 0, i/o):

Re: [Qemu-devel] [PATCH v7 3/5] migration: API to clear bits of guest free pages from the dirty bitmap

2018-06-03 Thread Peter Xu
On Fri, Jun 01, 2018 at 08:32:27PM +0800, Wei Wang wrote: > On 06/01/2018 06:06 PM, Peter Xu wrote: > > On Fri, Jun 01, 2018 at 03:36:01PM +0800, Wei Wang wrote: > > > On 06/01/2018 12:00 PM, Peter Xu wrote: > > > > On Tue, Apr 24, 2018 at 02:13:46PM +0800, Wei Wang wrote: > > > > >/* > > > >

Re: [Qemu-devel] [PATCH 4/8] virtio: add detach element for packed ring(1.1)

2018-06-03 Thread Michael S. Tsirkin
On Mon, Jun 04, 2018 at 09:34:35AM +0800, Wei Xu wrote: > On Tue, Apr 10, 2018 at 03:32:53PM +0800, Jason Wang wrote: > > > > > > On 2018年04月04日 20:54, w...@redhat.com wrote: > > >From: Wei Xu > > > > > >helper for packed ring > > > > It's odd and hard to review if you put detach patch first.

Re: [Qemu-devel] [PATCH RFC] hw/pc: set q35 as the default x86 machine

2018-06-03 Thread Michael S. Tsirkin
On Sun, Jun 03, 2018 at 12:27:49PM +0300, Marcel Apfelbaum wrote: > Moving to QEMU 3.0 seems like a good opportunity for such a change. > > I440FX is really old and does not support modern features like IOMMU. > Q35's SATA emulation is faster than pc's IDE, native PCI express hotplug > is cleaner

Re: [Qemu-devel] [PATCH 4/8] virtio: add detach element for packed ring(1.1)

2018-06-03 Thread Wei Xu
On Tue, Apr 10, 2018 at 03:32:53PM +0800, Jason Wang wrote: > > > On 2018年04月04日 20:54, w...@redhat.com wrote: > >From: Wei Xu > > > >helper for packed ring > > It's odd and hard to review if you put detach patch first. I think this > patch needs to be reordered after the implementation of

Re: [Qemu-devel] [PATCH] ppc: e500: use g_strdup_printf() instead of snprintf()

2018-06-03 Thread David Gibson
On Tue, May 08, 2018 at 12:01:59PM +0100, Peter Maydell wrote: > On 8 May 2018 at 10:34, Greg Kurz wrote: > > On Mon, 7 May 2018 12:53:45 -0500 > > Eric Blake wrote: > > > >> On 05/07/2018 04:02 AM, Greg Kurz wrote: > >> > qemu-system-ppc fails to build with GCC 8.0.1: > >> > > >> >

Re: [Qemu-devel] [PATCH 2/4] macio: add trace-events to timer device

2018-06-03 Thread David Gibson
On Sun, May 06, 2018 at 03:20:03PM +0100, Mark Cave-Ayland wrote: > Signed-off-by: Mark Cave-Ayland Applied, thanks. > --- > hw/misc/macio/macio.c | 3 +++ > hw/misc/macio/trace-events | 4 > 2 files changed, 7 insertions(+) > > diff --git a/hw/misc/macio/macio.c

Re: [Qemu-devel] [PATCH 1/4] uninorth: add impl min_access_size and max_access_size to unin_ops

2018-06-03 Thread David Gibson
On Sun, May 06, 2018 at 03:20:02PM +0100, Mark Cave-Ayland wrote: > >From testing all my local images the uninorth registers are only ever > read or written with 32-bit accesses. If that's the case, shouldn't you be setting the range of valid accesses, rather than the range of implemented

Re: [Qemu-devel] [PATCH v3] target/ppc: Allow PIR read in privileged mode

2018-06-03 Thread David Gibson
On Mon, May 07, 2018 at 01:52:42PM -0300, luporl wrote: > According to PowerISA, the PIR register should be readable in privileged > mode also, not only in hypervisor privileged mode. > > PowerISA 3.0 - 4.3.3 Processor Identification Register > > "Read access to the PIR is privileged; write

Re: [Qemu-devel] [PATCH 4/4] uninorth: remove token register from uninorth device

2018-06-03 Thread David Gibson
On Sun, May 06, 2018 at 03:20:05PM +0100, Mark Cave-Ayland wrote: > >From observation of various OS sources it can be seen that the token register > introduced in 4e46dcdbd3 "PPC: Newworld: Add uninorth token register" is not > required, since the only register currently implemented is the

Re: [Qemu-devel] [PATCH 6/6] linux-user: Use *at functions to implement interp_prefix

2018-06-03 Thread Laurent Vivier
On 01/06/2018 00:49, Richard Henderson wrote: > If the interp_prefix is a complete chroot, it may have a *lot* of files. > Setting up the cache for this is quite expensive. > > For the most part, we can use the *at versions of various syscalls to > attempt the operation in the prefix. For the

[Qemu-devel] [PATCH 2/4] hw/timer: Add basic M41T80 emulation

2018-06-03 Thread BALATON Zoltan
Basic emulation of the M41T80 serial (I2C) RTC chip. Only getting time of day is implemented. Setting time and RTC alarm are not supported. Signed-off-by: BALATON Zoltan --- MAINTAINERS | 1 + default-configs/ppc-softmmu.mak | 1 + hw/timer/Makefile.objs | 1 +

[Qemu-devel] [PATCH 4/4] sm501: Do not clear read only bits when writing register

2018-06-03 Thread BALATON Zoltan
When writing a register that has read only bits besides reserved bits we have to avoid changing read only bits that may have non zero default values. While at it, fix a reserved bit mask and a white space error. Signed-off-by: BALATON Zoltan --- hw/display/sm501.c | 6 +++--- 1 file changed, 3

[Qemu-devel] [PATCH 0/4] Misc sam460ex improvements

2018-06-03 Thread BALATON Zoltan
Some more improvements to sam460ex emulation: - Implemented RTC (which also needed fixing I2C to work) - Fix a problem in sm501 which led to AmigaOS slow down BALATON Zoltan (4): ppc4xx_i2c: Rewrite PPC4xx I2C emulation hw/timer: Add basic M41T80 emulation sam460ex: Add RTC device sm501:

[Qemu-devel] [PATCH 3/4] sam460ex: Add RTC device

2018-06-03 Thread BALATON Zoltan
The Sam460ex has an M41T80 serial RTC chip on I2C bus 0 at address 0x68. Signed-off-by: BALATON Zoltan --- hw/ppc/sam460ex.c | 1 + 1 file changed, 1 insertion(+) diff --git a/hw/ppc/sam460ex.c b/hw/ppc/sam460ex.c index a48e6e6..3848885 100644 --- a/hw/ppc/sam460ex.c +++ b/hw/ppc/sam460ex.c @@

[Qemu-devel] [PATCH 1/4] ppc4xx_i2c: Rewrite PPC4xx I2C emulation

2018-06-03 Thread BALATON Zoltan
I2C emulation currently is just enough for U-Boot to access SPD EEPROMs but features that guests use to access I2C devices are not correctly emulated. Rewrite to implement missing features to make it work with all clients. Signed-off-by: BALATON Zoltan --- Maybe this could be split up into more

Re: [Qemu-devel] [PATCH for 2.10 26/35] linux-user: use is_error() to avoid warnings and make the code clearer

2018-06-03 Thread Laurent Vivier
Le 29/05/2018 à 17:19, Laurent Vivier a écrit : > Le 29/05/2018 à 16:25, Philippe Mathieu-Daudé a écrit : >> Hi Laurent, > > Hi Philippe, > >> On 07/24/2017 04:16 PM, Laurent Vivier wrote: >>> Le 24/07/2017 à 20:27, Philippe Mathieu-Daudé a écrit : linux-user/flatload.c:740:9: warning: Loss

Re: [Qemu-devel] [RFC v3] qapi: command category to stimulate high-level machine devices

2018-06-03 Thread no-reply
Hi, This series failed docker-mingw@fedora build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. Type: series Message-id: 20180603203412.11033-1-cont...@steffen-goertz.de Subject: [Qemu-devel] [RFC v3] qapi:

[Qemu-devel] [RFC v3] qapi: command category to stimulate high-level machine devices

2018-06-03 Thread Steffen Görtz
Changes in v2: - Remove stray 1 Changes in v1: - Fix coding style issues Add a new category "stimulate" to host commands that act upon high-level devices associated with machines/boards. This is patch is part of an effort to add support for BBC:microbit educational computer to QEMU. The

Re: [Qemu-devel] [RFC v2] qapi: command category to stimulate high-level machine devices

2018-06-03 Thread no-reply
Hi, This series failed build test on s390x host. Please find the details below. Type: series Message-id: 20180603192242.17675-1-cont...@steffen-goertz.de Subject: [Qemu-devel] [RFC v2] qapi: command category to stimulate high-level machine devices === TEST SCRIPT BEGIN === #!/bin/bash #

Re: [Qemu-devel] [RFC v2] qapi: command category to stimulate high-level machine devices

2018-06-03 Thread no-reply
Hi, This series failed docker-mingw@fedora build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. Type: series Message-id: 20180603192242.17675-1-cont...@steffen-goertz.de Subject: [Qemu-devel] [RFC v2] qapi:

[Qemu-devel] [RFC v2] qapi: command category to stimulate high-level machine devices

2018-06-03 Thread Steffen Görtz
Changes since v1: - Fix coding style issues Add a new category "stimulate" to host commands that act upon high-level devices associated with machines/boards. This is patch is part of an effort to add support for BBC:microbit educational computer to QEMU. The microbit board, as many other

Re: [Qemu-devel] [PATCH 3/8] virtio: add empty check for packed ring

2018-06-03 Thread Wei Xu
On Tue, Apr 10, 2018 at 03:23:03PM +0800, Jason Wang wrote: > > > On 2018年04月04日 20:53, w...@redhat.com wrote: > >From: Wei Xu > > > >helper for ring empty check. > > And descriptor read. OK. > > > > >Signed-off-by: Wei Xu > >--- > > hw/virtio/virtio.c | 62 > >

[Qemu-devel] [Bug 1754542] Re: colo: vm crash with segmentation fault

2018-06-03 Thread Zhang Chen
Hi Suiheng, This bug have been fixed in my latest patch. Please retest it. https://www.mail-archive.com/qemu-devel@nongnu.org/msg538383.html github: https://github.com/zhangckid/qemu/tree/qemu-colo-18jun1 Thanks Zhang Chen -- You received this bug notification because you are a member of

Re: [Qemu-devel] [PATCH 1/8] virtio: feature bit, data structure for packed ring

2018-06-03 Thread Wei Xu
On Tue, Apr 10, 2018 at 03:05:24PM +0800, Jason Wang wrote: > > > On 2018年04月04日 20:53, w...@redhat.com wrote: > >From: Wei Xu > > > >Only minimum definitions from the spec are included > >for prototype. > > > >Signed-off-by: Wei Xu > >--- > > hw/virtio/virtio.c |

Re: [Qemu-devel] Virtio-net drivers immune to Nethammer?

2018-06-03 Thread Michael S. Tsirkin
On Sat, Jun 02, 2018 at 03:08:54AM +, procmem wrote: > > > Michael S. Tsirkin: > > On Fri, Jun 01, 2018 at 01:15:44PM +, procmem wrote: > >> > >> > >> Stefan Hajnoczi: > >>> On Mon, May 21, 2018 at 11:24:43PM +, procmem wrote: > Hi I'm a privacy distro maintainer investigating

Re: [Qemu-devel] [PATCH v4 11/12] migration: poll the cm event while wait RDMA work request completion

2018-06-03 Thread Aviad Yehezkel
+Gal Gal, please comment with our findings. Thanks! On 5/31/2018 10:36 AM, 858585 jemmy wrote: On Thu, May 31, 2018 at 1:33 AM, Dr. David Alan Gilbert wrote: * Lidong Chen (jemmy858...@gmail.com) wrote: If the peer qemu is crashed, the qemu_rdma_wait_comp_channel function maybe loop

Re: [Qemu-devel] [PATCH v4 04/12] migration: avoid concurrent invoke channel_close by different threads

2018-06-03 Thread 858585 jemmy
On Sun, Jun 3, 2018 at 9:50 PM, 858585 jemmy wrote: > On Thu, May 31, 2018 at 6:52 PM, Dr. David Alan Gilbert > wrote: >> * 858585 jemmy (jemmy858...@gmail.com) wrote: >>> On Wed, May 30, 2018 at 10:45 PM, Dr. David Alan Gilbert >>> wrote: >>> > * Lidong Chen (jemmy858...@gmail.com) wrote: >>>

Re: [Qemu-devel] [PATCH v4 04/12] migration: avoid concurrent invoke channel_close by different threads

2018-06-03 Thread 858585 jemmy
On Thu, May 31, 2018 at 6:52 PM, Dr. David Alan Gilbert wrote: > * 858585 jemmy (jemmy858...@gmail.com) wrote: >> On Wed, May 30, 2018 at 10:45 PM, Dr. David Alan Gilbert >> wrote: >> > * Lidong Chen (jemmy858...@gmail.com) wrote: >> >> From: Lidong Chen >> >> >> >> The channel_close maybe

Re: [Qemu-devel] Cortex M0 emulation tasks

2018-06-03 Thread Liviu Ionescu
On 2 June 2018 at 17:15:15, Stefan Hajnoczi (stefa...@gmail.com) wrote: > > I have put together a basic Cortex M0 ARMv6-M CPU that can serve > as > the basis for this work. Please see the RFC patches that I've sent > separately. you can also take a look at the Cortex-M implementation in the GNU

Re: [Qemu-devel] [PATCH 2/2] hw/arm/armv7m: Remove unused armv7m_init() function

2018-06-03 Thread Peter Maydell
On 3 June 2018 at 01:48, Joel Stanley wrote: > Hi Peter, > > On 2 June 2018 at 00:13, Peter Maydell wrote: >> Remove the now-unused armv7m_init() function. This was a legacy from >> before we properly QOMified ARMv7M, and it has some flaws: >> >> * it combines work that needs to be done by an

Re: [Qemu-devel] Mistake on man page

2018-06-03 Thread kvaps
Ok, thanks for the clarification. On Fri, Jun 1, 2018 at 7:17 PM Daniel P. Berrangé wrote: > On Fri, Jun 01, 2018 at 04:47:55PM +0200, kvaps wrote: > > Hi, here is mistake in man page for qemu-nbd: > > > > --- a/qemu-nbd.texi > > +++ b/qemu-nbd.texi > > @@ -1,2 +1,2 @@ > > --- a/qemu-nbd.texi >

[Qemu-devel] [Bug 1774853] Re: claims temp file is used by another process

2018-06-03 Thread tsiros
someone please delete this ** Changed in: qemu Status: New => Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1774853 Title: claims temp file is used by another process Status in

[Qemu-devel] [Bug 1774853] [NEW] claims temp file is used by another process

2018-06-03 Thread tsiros
Public bug reported: QEMU emulator version 2.12.50 (v2.12.0-12378-g99a34dc4d2-dirty) "c:\Program Files\qemu\qemu-system-x86_64.exe" -net none -parallel none -bios OVMF.fd -L . -hda fat:rw:image vvfat image chs 1024,16,63 c:\Program Files\qemu\qemu-system-x86_64.exe: -hda fat:rw:image: Could not

[Qemu-devel] [PATCH RFC] hw/pc: set q35 as the default x86 machine

2018-06-03 Thread Marcel Apfelbaum
Moving to QEMU 3.0 seems like a good opportunity for such a change. I440FX is really old and does not support modern features like IOMMU. Q35's SATA emulation is faster than pc's IDE, native PCI express hotplug is cleaner than ACPI based one and so on... Also the libvirt guys added very good