[Qemu-devel] [Bug 546638] Re: Connection error when use PXE+NFS to boot guest

[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/546638 Title: Connection

[Qemu-devel] [Bug 526653] Re: Breakpoint on Memory address fails with KVM

[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/526653 Title: Breakpoint

[Qemu-devel] [PATCH 3/3] target/hppa: Fix cpu_clone_regs

By failing to return from the syscall in the child, the child issues another clone syscall and hilarity ensues. Signed-off-by: Richard Henderson --- linux-user/hppa/target_cpu.h | 4 1 file changed, 4 insertions(+) diff --git a/linux-user/hppa/target_cpu.h

[Qemu-devel] [PATCH 2/3] linux-user: Fix TARGET_SA_* defines for HPPA

From: Helge Deller Reported-by: Helge Deller Signed-off-by: Richard Henderson --- linux-user/syscall_defs.h | 8 1 file changed, 8 insertions(+) diff --git a/linux-user/syscall_defs.h b/linux-user/syscall_defs.h index 8b1ad74..2620b56

[Qemu-devel] [PATCH 0/3] Fixes for hppa-linux-user

The primary motivator here is in the third patch, allowing any threads to be created. Previously I had written off crashes using threads as lack of MTTCG support without really digging into it deeper. Ho hum. But in the process of looking for the root cause, Helge found two other things that

[Qemu-devel] [PATCH 1/3] linux-user: Restrict usage of sa_restorer

Reading and writing to an sa_restorer member that isn't supposed to exist corrupts user memory. Introduce TARGET_ARCH_HAS_SA_RESTORER, similar to the kernel's __ARCH_HAS_SA_RESTORER. Reported-by: Helge Deller Signed-off-by: Richard Henderson ---

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

On Wed, Mar 8, 2017 at 10:11 AM, Daniel P. Berrange wrote: > On Wed, Mar 08, 2017 at 09:59:32AM -0800, ashish mittal wrote: >> On Wed, Mar 8, 2017 at 5:04 AM, Ketan Nilangekar >> wrote: >> > >> > >> >> On Mar 8, 2017, at 1:13 AM, Daniel P.

Re: [Qemu-devel] Benchmarking linux-user performance

On Fri, Mar 10, 2017 at 12:48:31 +0100, Peter Maydell wrote: > On 10 March 2017 at 12:45, Dr. David Alan Gilbert wrote: > > * Emilio G. Cota (c...@braap.org) wrote: > >> x86_64 NBench Floating Point Performance > >> Host: Intel(R)

Re: [Qemu-devel] Benchmarking linux-user performance

On Fri, Mar 10, 2017 at 11:45:33 +, Dr. David Alan Gilbert wrote: > * Emilio G. Cota (c...@braap.org) wrote: > > https://github.com/cota/dbt-bench > > I'm using NBench because (1) it's just a few files and they take > > very little time to run (~5min per QEMU version, if performance > > on

Re: [Qemu-devel] [PATCHv2] scripts/dump-guest-memory.py: fix int128_get64 on recent gcc

On 03/10/17 12:28, Marc-André Lureau wrote: > The Int128 is no longer a struct, reaching a python exception: > Python Exception Attempt to extract a component of a > value that is not a (null).: > > Replace struct access with a cast to uint64[] instead. > > Fixes: >

[Qemu-devel] [Bug 1671876] Re: qemu 2.7.0 segfaults in qemu_co_queue_run_restart()

** Description changed: Hi, I've been experiencing frequent segfaults lately with qemu 2.7.0 running Ubuntu 16.04 guests. The crash usually happens in qemu_co_queue_run_restart(). I haven't seen this so far with any other guests or distros. Here is one back trace I obtained from

Re: [Qemu-devel] [PATCH v7 kernel 3/5] virtio-balloon: implementation of VIRTIO_BALLOON_F_CHUNK_TRANSFER

On Fri, Mar 10, 2017 at 09:35:21PM +0200, Michael S. Tsirkin wrote: > > bit 0 clear => bits 1-11 encode a page count, bits 12-63 encode a PFN, page > > size 4k. > > bit 0 set, bit 1 clear => bits 2-12 encode a page count, bits 13-63 encode > > a PFN, page size 8k > > bits 0+1 set, bit 2 clear =>

Re: [Qemu-devel] [PATCH v7 kernel 3/5] virtio-balloon: implementation of VIRTIO_BALLOON_F_CHUNK_TRANSFER

On Fri, Mar 10, 2017 at 09:10:53PM +0200, Michael S. Tsirkin wrote: > > I completely agree with you that we should be able to pass a hugepage > > as a single chunk. Also we shouldn't assume that host and guest have > > the same page size. I think we can come up with a scheme that actually > >

Re: [Qemu-devel] [PATCH v2 1/1] virtio-blk: fix race on guest notifiers

On 03/10/2017 05:47 PM, Paolo Bonzini wrote: > > On 07/03/2017 14:16, Halil Pasic wrote: >> The commits 03de2f527 "virtio-blk: do not use vring in dataplane" and >> 9ffe337c08 "virtio-blk: always use dataplane path if ioeventfd is active" >> changed how notifications are done for virtio-blk

Re: [Qemu-devel] [PATCH for-2.9] mirror: Fix backwards mirror_yield parameters

On 03/09/2017 09:25 PM, Eric Blake wrote: > [adding Stefan in cc, as trace maintainer] > > On 03/09/2017 09:15 PM, Eric Blake wrote: > > Perhaps I should update the subject to mention trace? > >> trace-events lists the parameters for mirror_yield consistently >> with other events (cnt just

[Qemu-devel] [PATCH v2] xen: don't save/restore the physmap on VM save/restore

Saving/restoring the physmap to/from xenstore was introduced to QEMU majorly in order to cover up the VRAM region restore issue. The sequence of restore operations implies that we should know the effective guest VRAM address *before* we have the VRAM region restored (which happens later).

[Qemu-devel] [PATCH v2 2/2] qdev: Constify local variable returned by blk_bs

Inside qdev_prop_set_drive() the value returned by blk_bs() is passed only as pointer to const to bdrv_get_node_name() and pointed values is not modified in other places so this can be made const for code safeness. Signed-off-by: Krzysztof Kozlowski ---

[Qemu-devel] [PATCH v2 0/2] qdev: Minor const improvements

Hi, Minor improvements. Changes since v1: 1. Follow suggestions from v1 discussion - drop other consts. Best regards, Krzysztof Krzysztof Kozlowski (2): qdev: Constify value passed to qdev_prop_set_macaddr qdev: Constify local variable returned by blk_bs hw/core/qdev-properties-system.c

[Qemu-devel] [PATCH v2 1/2] qdev: Constify value passed to qdev_prop_set_macaddr

The 'value' argument is not modified so this can be made const for code safeness. Signed-off-by: Krzysztof Kozlowski --- hw/core/qdev-properties.c| 3 ++- include/hw/qdev-properties.h | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git

Re: [Qemu-devel] [PATCH v7 kernel 3/5] virtio-balloon: implementation of VIRTIO_BALLOON_F_CHUNK_TRANSFER

On Fri, Mar 10, 2017 at 09:11:44AM -0800, Matthew Wilcox wrote: > On Fri, Mar 10, 2017 at 05:58:28PM +0200, Michael S. Tsirkin wrote: > > One of the issues of current balloon is the 4k page size > > assumption. For example if you free a huge page you > > have to split it up and pass 4k chunks to

Re: [Qemu-devel] [PATCH v1 1/2] reduce qemu's heap Rss size from 12252kB to 2752KB

> > Ideally, freeing QOM object should not require a global lock. > > If you see any other QOM requiring a global lock, please let us know, we > are willing to fix it. > > All of them. When unplugging a device, the device object will be freed > from an RCU callback. > Thanks for your reply,

Re: [Qemu-devel] [PATCH v7 kernel 3/5] virtio-balloon: implementation of VIRTIO_BALLOON_F_CHUNK_TRANSFER

On Fri, Mar 10, 2017 at 09:11:44AM -0800, Matthew Wilcox wrote: > On Fri, Mar 10, 2017 at 05:58:28PM +0200, Michael S. Tsirkin wrote: > > One of the issues of current balloon is the 4k page size > > assumption. For example if you free a huge page you > > have to split it up and pass 4k chunks to

Re: [Qemu-devel] [PATCH v3] SGABIOS: fix wrong video attrs for int 10h, ah==13h

On 10/03/2017 16:54, Herbie Robinson wrote: > Fix Bug #1670509: wrong video attrs for int 10h, ah==13h > The subroutine set_cursor_position is trashing %bx. > Unfortunately, %bl contains the video attribute for write_string. > > The fix saves %bx in the function prolog and restores it in > the

[Qemu-devel] [PULL 3/3] i386: Change stepping of Haswell to non-blacklisted value

glibc blacklists TSX on Haswell CPUs with model==60 and stepping < 4. To make the Haswell CPU model more useful, make those guests actually use TSX by changing CPU stepping to 4. References: * glibc commit 2702856bf45c82cf8e69f2064f5aa15c0ceb6359

[Qemu-devel] [PULL 1/3] i386: host_vendor_fms() helper function

Helper function for code that needs to check the host CPU vendor/family/model/stepping values. Signed-off-by: Eduardo Habkost Message-Id: <20170309181212.18864-2-ehabk...@redhat.com> Signed-off-by: Eduardo Habkost --- target/i386/cpu.h | 1 +

[Qemu-devel] [PULL 2/3] i386/kvm: Blacklist TSX on known broken hosts

Some Intel CPUs are known to have a broken TSX implementation. A microcode update from Intel disabled TSX on those CPUs, but GET_SUPPORTED_CPUID might be reporting it as supported if the hosts were not updated yet. Manually fixup the GET_SUPPORTED_CPUID data to ensure we will never enable TSX

[Qemu-devel] [PULL 0/3] x86: Haswell TSX blacklist fix for 2.9

The following changes since commit dd4d2578215cd380f40a38028a9904e15b135ef3: Merge remote-tracking branch 'remotes/kraxel/tags/pull-fixes-20170309-1' into staging (2017-03-09 13:16:05 +) are available in the git repository at: git://github.com/ehabkost/qemu.git tags/x86-pull-request

Re: [Qemu-devel] [PATCH for-2.8] dma/rc4030: translate memory accesses only when they occur

Ping again. Le 26/02/2017 à 20:19, Hervé Poussineau a écrit : Ping again. Le 22/02/2017 à 07:19, Hervé Poussineau a écrit : Ping? Le 18/11/2016 à 23:43, Hervé Poussineau a écrit : This simplifies the code a lot, and this fixes big memory leaks introduced in

Re: [Qemu-devel] [PATCH 0/2] hostmem: introduce host_memory_backend_mr_inited

On Fri, Mar 10, 2017 at 09:09:28PM +0800, Peter Xu wrote: > This is a tiny cleanup series for host backend mem. Patch 1 introduced > the new interface, patch 2 uses them. Please review, thanks. Reviewed-by: Eduardo Habkost Queueing for 2.10, on my machine-next branch. --

Re: [Qemu-devel] [PATCH for-2.9 v3 0/3] Use non-blacklisted family/model/stepping for Haswell CPU model

On Thu, Mar 09, 2017 at 03:12:09PM -0300, Eduardo Habkost wrote: > I plan to merge this bug fix into 2.9. I'm queueing this on my x86-next branch. > > Changes v2 -> v3: > * Rebase to latest master > * Don't touch max_x86_cpu_initfn() to reduce risk post > hard freeze > > Changes v1 -> v2: >

Re: [Qemu-devel] [PATCH for-2.9? v2 0/2] vl: Print warning if a non-empty default config-file is found

On Fri, Mar 10, 2017 at 10:18:26AM +0100, Paolo Bonzini wrote: > > > On 09/03/2017 19:20, Eduardo Habkost wrote: > > (This missed hard freeze, but I would still like to include the > > warning in 2.9 so we can remove the default config file in 2.10. > > I will include this series in a pull

Re: [Qemu-devel] [PATCH v1 2/2] reduce qemu's heap Rss size from 12252kB to 2752KB

> -Original Message- > From: Paolo Bonzini [mailto:pbonz...@redhat.com] > Sent: Friday, March 10, 2017 1:14 AM > To: Zhong, Yang ; qemu-devel@nongnu.org > Cc: Xu, Anthony ; Peng, Chao P > > Subject: Re: [PATCH v1 2/2]

[Qemu-devel] [Bug 1671876] Re: qemu 2.7.0 segfaults in qemu_co_queue_run_restart()

Could you please retry with the latest stable version (either 2.8.0 or 2.7.1) ... maybe the problem is already fixed there. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1671876 Title: qemu 2.7.0

[Qemu-devel] [Bug 1671876] Re: qemu 2.7.0 segfaults in qemu_co_queue_run_restart()

The VMs were running with the following arguments - -m 1024,slots=255,maxmem=256G -M pc-i440fx-2.7 -enable-kvm -nodefconfig -nodefaults -rtc base=utc -netdev

Re: [Qemu-devel] [PATCH v7 kernel 3/5] virtio-balloon: implementation of VIRTIO_BALLOON_F_CHUNK_TRANSFER

On Fri, Mar 10, 2017 at 05:58:28PM +0200, Michael S. Tsirkin wrote: > One of the issues of current balloon is the 4k page size > assumption. For example if you free a huge page you > have to split it up and pass 4k chunks to host. > Quite often host can't free these 4k chunks at all (e.g. > when

Re: [Qemu-devel] [PATCH v4] util: Removed unneeded header from path.c

On 10.03.2017 17:39, Suramya Shah wrote: > Signed-off-by: Suramya Shah > Reviewed-by: Eric Blake > --- > qemu-common.h is no longer necessary as of refactoring done in commit f348b6d. > util/path.c | 1 - > 1 file changed, 1 deletion(-) > > diff

[Qemu-devel] [Bug 1671876] Re: qemu 2.7.0 segfaults in qemu_co_queue_run_restart()

A third stack trace It generates the following stack trace - (gdb) bt #0 qemu_co_queue_run_restart (co=0x7f75ed30dbc0) at /build/pb-qemu-pssKUp/pb-qemu-2.7.0/util/qemu-coroutine-lock.c:59 #1 0x5619274829a9 in

[Qemu-devel] [Bug 1671876] [NEW] qemu 2.7.0 segfaults in qemu_co_queue_run_restart()

Public bug reported: Hi, I've been experiencing frequent segfaults lately with qemu 2.7.0 running Ubuntu 16.04 guests. The crash usually happens in qemu_co_queue_run_restart(). I haven't seen this so far with any other guests or distros. Here is one back trace I obtained from one of the

[Qemu-devel] [Bug 1671876] Re: qemu 2.7.0 segfaults in qemu_co_queue_run_restart()

Another stack trace - (gdb) bt #0 qemu_co_queue_run_restart (co=0x7f668be15260) at /build/pb-qemu-pssKUp/pb-qemu-2.7.0/util/qemu-coroutine-lock.c:59 #1 0x564cb19f59a9 in qemu_coroutine_enter (co=0x7f668be15260) at

Re: [Qemu-devel] [PATCH v2 1/1] virtio-blk: fix race on guest notifiers

On 07/03/2017 14:16, Halil Pasic wrote: > The commits 03de2f527 "virtio-blk: do not use vring in dataplane" and > 9ffe337c08 "virtio-blk: always use dataplane path if ioeventfd is active" > changed how notifications are done for virtio-blk substantially. Due to a > race condition, interrupts

Re: [Qemu-devel] [PATCH] configure: add the missing help output for optional features

On 10/03/2017 11:14, Lin Ma wrote: > Signed-off-by: Lin Ma > --- > configure | 12 > 1 file changed, 12 insertions(+) > > diff --git a/configure b/configure > index 6c21975..2603e10 100755 > --- a/configure > +++ b/configure > @@ -1335,6 +1335,12 @@ Advanced

Re: [Qemu-devel] [PATCH] x86: Allow to set NUMA distance for different NUMA nodes

On Fri, Mar 10, 2017 at 06:40:52PM +0200, Michael S. Tsirkin wrote: > On Fri, Mar 10, 2017 at 04:38:59PM +, Daniel P. Berrange wrote: > > On Fri, Mar 10, 2017 at 10:37:08AM -0600, Eric Blake wrote: > > > On 03/10/2017 04:18 AM, He Chen wrote: > > > > Current, QEMU does not provide a clear

Re: [Qemu-devel] [PATCH] x86: Allow to set NUMA distance for different NUMA nodes

On Fri, Mar 10, 2017 at 04:38:59PM +, Daniel P. Berrange wrote: > On Fri, Mar 10, 2017 at 10:37:08AM -0600, Eric Blake wrote: > > On 03/10/2017 04:18 AM, He Chen wrote: > > > Current, QEMU does not provide a clear command to set vNUMA distance for > > > guest although we already have `-numa`

[Qemu-devel] [PATCH v4] util: Removed unneeded header from path.c

Signed-off-by: Suramya Shah Reviewed-by: Eric Blake --- qemu-common.h is no longer necessary as of refactoring done in commit f348b6d. util/path.c | 1 - 1 file changed, 1 deletion(-) diff --git a/util/path.c b/util/path.c index 5479f76..7f9fc27

Re: [Qemu-devel] [PATCH] x86: Allow to set NUMA distance for different NUMA nodes

On Fri, Mar 10, 2017 at 10:37:08AM -0600, Eric Blake wrote: > On 03/10/2017 04:18 AM, He Chen wrote: > > Current, QEMU does not provide a clear command to set vNUMA distance for > > guest although we already have `-numa` command to set vNUMA nodes. > > > > > > > This patch is going to add SLIT

Re: [Qemu-devel] [PATCH] x86: Allow to set NUMA distance for different NUMA nodes

On 03/10/2017 04:18 AM, He Chen wrote: > Current, QEMU does not provide a clear command to set vNUMA distance for > guest although we already have `-numa` command to set vNUMA nodes. > > > This patch is going to add SLIT table support in QEMU, and provides > addtional option `dist` for command

Re: [Qemu-devel] [PATCH] x86: Allow to set NUMA distance for different NUMA nodes

On Fri, Mar 10, 2017 at 06:18:17PM +0800, He Chen wrote: > 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

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

On 10.03.2017 15:09, Igor Mammedov wrote: > we are trying no to use cpu_index in outside interfaces and > make it disappear from there. > It's possible to use qom-path instead or more natural > CpuInstanceProperties to specify a CPU. > > PS: > Comment applies to all QMP/monitor

Re: [Qemu-devel] [PATCH v1 1/2] reduce qemu's heap Rss size from 12252kB to 2752KB

On 10/03/2017 17:05, Xu, Anthony wrote: > Ideally, freeing QOM object should not require a global lock. > If you see any other QOM requiring a global lock, please let us know, we are > willing to fix it. All of them. When unplugging a device, the device object will be freed from an RCU

Re: [Qemu-devel] [PATCH v1 1/2] reduce qemu's heap Rss size from 12252kB to 2752KB

> -Original Message- > From: Paolo Bonzini [mailto:pbonz...@redhat.com] > Sent: Friday, March 10, 2017 12:42 AM > To: Zhong, Yang ; qemu-devel@nongnu.org > Cc: Xu, Anthony ; Peng, Chao P > > Subject: Re: [PATCH v1 1/2]

Re: [Qemu-devel] [PATCH v7 kernel 3/5] virtio-balloon: implementation of VIRTIO_BALLOON_F_CHUNK_TRANSFER

On Fri, Mar 10, 2017 at 07:37:28PM +0800, Wei Wang wrote: > On 03/09/2017 10:14 PM, Matthew Wilcox wrote: > > On Fri, Mar 03, 2017 at 01:40:28PM +0800, Wei Wang wrote: > > > From: Liang Li > > > 1) allocating pages (6.5%) > > > 2) sending PFNs to host (68.3%) > > > 3)

[Qemu-devel] [PATCH v3] SGABIOS: fix wrong video attrs for int 10h, ah==13h

Fix Bug #1670509: wrong video attrs for int 10h, ah==13h The subroutine set_cursor_position is trashing %bx. Unfortunately, %bl contains the video attribute for write_string. The fix saves %bx in the function prolog and restores it in the epilog. Signed-off-by: Herbie Robinson

Re: [Qemu-devel] external snapshots freezes block device since qemu 2.8

W dniu 2017-03-10 o 15:49, Kashyap Chamarthy pisze: On Thu, Mar 09, 2017 at 11:11:09AM +0100, Piotr Rybicki wrote: Hello there. I discovered, that since qemu 2.8 , external snapshots (very similar to: http://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit), When I wrote this

Re: [Qemu-devel] [virtio-dev] Re: [PATCH v7 kernel 3/5] virtio-balloon: implementation of VIRTIO_BALLOON_F_CHUNK_TRANSFER

On Fri, Mar 10, 2017 at 06:02:31PM +0800, Wei Wang wrote: > On 03/08/2017 12:01 PM, Michael S. Tsirkin wrote: > > On Fri, Mar 03, 2017 at 01:40:28PM +0800, Wei Wang wrote: > > > From: Liang Li > > > > > > The implementation of the current virtio-balloon is not very > > >

Re: [Qemu-devel] [PULL 15/17] spapr_pci: Advertise access to PCIe extended config space

On Fri, 2017-03-03 at 14:25 +1100, David Gibson wrote: > The (paravirtual) PCI host bridge on the 'pseries' machine in most > regards acts like a regular PCI bus, rather than a PCIe bus.  Despite > this, though, it does allow access to the PCIe extended config space. >  > We already implemented

Re: [Qemu-devel] external snapshots freezes block device since qemu 2.8

On Thu, Mar 09, 2017 at 11:11:09AM +0100, Piotr Rybicki wrote: > Hello there. > > I discovered, that since qemu 2.8 , external snapshots (very similar to: > http://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit), When I wrote this Wiki page, I tested it only with regular QCOW2

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

On Wed, 8 Mar 2017 09:26:58 +0100 Julian Kirsch wrote: [...] > > > >> +++ b/qapi-schema.json > >> @@ -2365,6 +2365,55 @@ > >>'data': {'val': 'int', 'size': 'int', 'filename': 'str'} } > >> > >> ## > >> +# @MsrInfo: > >> +# > >> +# Information about a MSR > >> +# > >>

[Qemu-devel] Dual userfaultfd behavior

Hi, David, Andrea and Mike The problem I want to discuss it's 1G hugepage based VM and post copy live migration. I would like to know your opinion on following approach of avoiding such problem: Once we have mmap'ed area through 1G hugetlbfs, remap physical pages with /dev/mem. It will be 2

Re: [Qemu-devel] [PATCH v2] Add inst_dirty_pages_rate in 'info migrate'

On Thu, Mar 09, 2017 at 06:05:38PM +0800, Chao Fan wrote: > On Wed, Mar 08, 2017 at 01:45:59PM +, Daniel P. Berrange wrote: > >On Wed, Mar 08, 2017 at 04:28:19PM +0800, Chao Fan wrote: > >> Auto-converge aims to accelerate migration by slowing down the > >> generation of dirty pages. But user

Re: [Qemu-devel] [virtio-dev] Re: [PATCH v7 kernel 3/5] virtio-balloon: implementation of VIRTIO_BALLOON_F_CHUNK_TRANSFER

Am 10.03.2017 um 11:02 schrieb Wei Wang: > On 03/08/2017 12:01 PM, Michael S. Tsirkin wrote: >> On Fri, Mar 03, 2017 at 01:40:28PM +0800, Wei Wang wrote: >>> From: Liang Li >>> >>> The implementation of the current virtio-balloon is not very >>> efficient, because the pages

[Qemu-devel] [PATCH 2/2] hostmem: use host_memory_backend_mr_inited() where proper

Use the new interface to boost readability. Signed-off-by: Peter Xu --- backends/hostmem-file.c | 6 +++--- backends/hostmem.c | 10 +- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/backends/hostmem-file.c b/backends/hostmem-file.c index

[Qemu-devel] [PATCH 0/2] hostmem: introduce host_memory_backend_mr_inited

This is a tiny cleanup series for host backend mem. Patch 1 introduced the new interface, patch 2 uses them. Please review, thanks. Peter Xu (2): hostmem: introduce host_memory_backend_mr_inited() hostmem: use host_memory_backend_mr_inited() where proper backends/hostmem-file.c | 6 +++---

[Qemu-devel] [PATCH 1/2] hostmem: introduce host_memory_backend_mr_inited()

We were checking this against memory region size of host memory backend's mr field to see whether the mr has been inited. This is efficient but less elegant. Let's make a helper for it to avoid confusions, along with some notes. Suggested-by: Peter Maydell

Re: [Qemu-devel] [PATCH 2/2] vl: Print CPU help after we've registered the CPU accelerators

On Tue, 2017-03-07 at 10:02 +0100, Thomas Huth wrote: > The problem is that on POWER, we've got a "family" of CPUs with > different sub-types, e.g. for POWER8: >  > $ qemu-system-ppc64 -cpu ? | grep POWER8 > PowerPC POWER8E_v2.1 PVR 004b0201 > PowerPC POWER8E  (alias for POWER8E_v2.1)

Re: [Qemu-devel] What's the next QEMU version after 2.9 ? (or: when is a good point in time to get rid of old interfaces)

On 10/03/2017 11:53, Thomas Huth wrote: > On 10.03.2017 12:22, Peter Maydell wrote: >> On 10 March 2017 at 12:07, Jason Wang wrote: >>> On 2017年03月09日 18:20, Yongbok Kim wrote: Indeed but we still use the platform to verify architectural compatibilities even for

Re: [Qemu-devel] What's the next QEMU version after 2.9 ? (or: when is a good point in time to get rid of old interfaces)

On 10.03.2017 12:22, Peter Maydell wrote: > On 10 March 2017 at 12:07, Jason Wang wrote: >> On 2017年03月09日 18:20, Yongbok Kim wrote: >>> Indeed but we still use the platform to verify architectural >>> compatibilities even for newer MIPS architectures. > >> I see, but I

Re: [Qemu-devel] Benchmarking linux-user performance

On 10 March 2017 at 12:45, Dr. David Alan Gilbert wrote: > * Emilio G. Cota (c...@braap.org) wrote: >> x86_64 NBench Floating Point Performance >> Host: Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz >> >> 1.88

Re: [Qemu-devel] Benchmarking linux-user performance

* Emilio G. Cota (c...@braap.org) wrote: > Hi all, > > Inspired by SimBench[1], I have written a set of scripts ("DBT-bench") > to easily obtain and plot performance numbers for linux-user. > > The (Perl) scripts are available here: > https://github.com/cota/dbt-bench > [ It's better to clone

Re: [Qemu-devel] [PATCH v7 kernel 3/5] virtio-balloon: implementation of VIRTIO_BALLOON_F_CHUNK_TRANSFER

On 03/09/2017 10:14 PM, Matthew Wilcox wrote: On Fri, Mar 03, 2017 at 01:40:28PM +0800, Wei Wang wrote: From: Liang Li 1) allocating pages (6.5%) 2) sending PFNs to host (68.3%) 3) address translation (6.1%) 4) madvise (19%) This patch optimizes step 2) by transfering

[Qemu-devel] [PATCHv2] scripts/dump-guest-memory.py: fix int128_get64 on recent gcc

The Int128 is no longer a struct, reaching a python exception: Python Exception Attempt to extract a component of a value that is not a (null).: Replace struct access with a cast to uint64[] instead. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1427466 Signed-off-by: Marc-André Lureau

Re: [Qemu-devel] What's the next QEMU version after 2.9 ? (or: when is a good point in time to get rid of old interfaces)

On 10 March 2017 at 12:07, Jason Wang wrote: > On 2017年03月09日 18:20, Yongbok Kim wrote: >> Indeed but we still use the platform to verify architectural >> compatibilities even for newer MIPS architectures. > I see, but I believe it may need some modifications in the code to

Re: [Qemu-devel] What's the next QEMU version after 2.9 ? (or: when is a good point in time to get rid of old interfaces)

On 2017年03月09日 18:20, Yongbok Kim wrote: On 09/03/2017 09:53, Jason Wang wrote: On 2017年03月09日 16:50, Thomas Huth wrote: On 09.03.2017 03:21, Jason Wang wrote: On 2017年03月08日 19:22, Thomas Huth wrote: On 08.03.2017 11:03, Peter Maydell wrote: On 8 March 2017 at 09:26, Thomas Huth

Re: [Qemu-devel] [PATCH] e1000e: correctly tear down MSI-X memory regions

On 2017年03月09日 20:05, Laurent Vivier wrote: On 09/03/2017 12:58, Paolo Bonzini wrote: MSI-X has been disabled by the time the e1000e device is unrealized, hence msix_uninit is never called. This causes the object to be leaked, which shows up as a RAMBlock with empty name when attempting

Re: [Qemu-devel] [PATCH] scripts/dump-guest-memory.py: fix int128_get64 on recent gcc

On 10/03/2017 11:54, Marc-André Lureau wrote: > Hi > > On Fri, Mar 10, 2017 at 2:00 PM Paolo Bonzini > wrote: > > > > On 10/03/2017 09:53, Marc-André Lureau wrote: > > The Int128 is no longer a struct, reaching a python exception: >

Re: [Qemu-devel] [PATCH] virtio: destroy region cache during reset

On 2017年03月09日 19:07, Cornelia Huck wrote: On Thu, 9 Mar 2017 10:19:47 +0800 Jason Wang wrote: On 2017年03月08日 18:12, Cornelia Huck wrote: On Wed, 8 Mar 2017 17:51:22 +0800 Jason Wang wrote: On 2017年03月08日 17:19, Cornelia Huck wrote: On Wed, 8

Re: [Qemu-devel] [PATCH] scripts/dump-guest-memory.py: fix int128_get64 on recent gcc

Hi On Fri, Mar 10, 2017 at 2:00 PM Paolo Bonzini wrote: > > > On 10/03/2017 09:53, Marc-André Lureau wrote: > > The Int128 is no longer a struct, reaching a python exception: > > Python Exception Attempt to extract a component of a > value that is not a (null).: > > > >

Re: [Qemu-devel] [PATCH V3] virtio: do not require IOMMU to be created in advance

On 2017年03月09日 23:32, Paolo Bonzini wrote: On 09/03/2017 16:31, Michael S. Tsirkin wrote: On Thu, Mar 09, 2017 at 11:05:36AM +0100, Paolo Bonzini wrote: On 09/03/2017 10:58, Jason Wang wrote: On 2017年03月09日 17:28, Igor Mammedov wrote: On Thu, 9 Mar 2017 10:32:44 +0800 Jason

Re: [Qemu-devel] [PATCH RFC v3 00/15] basic vfio-ccw infrastructure

On Thu, 9 Mar 2017 17:25:25 +0800 Dong Jia Shi wrote: > * Dong Jia Shi [2017-02-17 09:29:24 +0100]: > > > vfio-ccw: the basic infrastructure > > == > > > > Introduction > > > > > > Here we

[Qemu-devel] [PATCH] x86: Allow to set NUMA distance for different NUMA nodes

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:

[Qemu-devel] [PATCH] configure: add the missing help output for optional features

Signed-off-by: Lin Ma --- configure | 12 1 file changed, 12 insertions(+) diff --git a/configure b/configure index 6c21975..2603e10 100755 --- a/configure +++ b/configure @@ -1335,6 +1335,12 @@ Advanced options (experts only): --with-vss-sdk=SDK-path enable

Re: [Qemu-devel] [PATCH for-2.10 2/5] pseries: Implement HPT resizing

On Fri, Mar 10, 2017 at 6:43 AM, David Gibson wrote: > This patch implements hypercalls allowing a PAPR guest to resize its own > hash page table. This will eventually allow for more flexible memory > hotplug. > > The implementation is partially asynchronous,

Re: [Qemu-devel] [PATCH] hostmem: fix reference to uninit mr

On 10/03/2017 10:36, Peter Xu wrote: > On Fri, Mar 10, 2017 at 10:17:30AM +0100, Peter Maydell wrote: >> On 10 March 2017 at 09:59, Peter Xu wrote: >>> On Fri, Mar 10, 2017 at 09:33:57AM +0100, Paolo Bonzini wrote: On 10/03/2017 05:13, Peter Xu wrote: >

Re: [Qemu-devel] [virtio-dev] Re: [PATCH v7 kernel 3/5] virtio-balloon: implementation of VIRTIO_BALLOON_F_CHUNK_TRANSFER

On 03/08/2017 12:01 PM, Michael S. Tsirkin wrote: On Fri, Mar 03, 2017 at 01:40:28PM +0800, Wei Wang wrote: From: Liang Li The implementation of the current virtio-balloon is not very efficient, because the pages are transferred to the host one by one. Here is the

Re: [Qemu-devel] [PATCH] scripts/dump-guest-memory.py: fix int128_get64 on recent gcc

On 10/03/2017 09:53, Marc-André Lureau wrote: > The Int128 is no longer a struct, reaching a python exception: > Python Exception Attempt to extract a component of a > value that is not a (null).: > > Replace struct access with a cast to uint64 instead. > > Fixes: >

Re: [Qemu-devel] [PATCH 3/8] xen/9pfs: introduce Xen 9pfs backend

On Thu, 9 Mar 2017 18:54:26 +0100 Greg Kurz wrote: > On Mon, 6 Mar 2017 18:12:43 -0800 > Stefano Stabellini wrote: > > > Introduce the Xen 9pfs backend: add struct XenDevOps to register as a > > Xen backend and add struct V9fsTransport to register as

Re: [Qemu-devel] [PATCH 2/5] qemu-timer: do not include sysemu/cpus.h from util/qemu-timer.h

Paolo Bonzini writes: > This dependency is the wrong way, and we will need util/qemu-timer.h from > sysemu/cpus.h > in the next patch. > > Signed-off-by: Paolo Bonzini With the compile fixes I posted as a !fixup patch: Reviewed-by: Alex Bennée

Re: [Qemu-devel] [PATCH 1/5] qemu-timer: fix off-by-one

Paolo Bonzini writes: > If the first timer is exactly at the current value of the clock, the > deadline is met and the timer should fire. This fixes itself without icount, > but with icount execution of instructions will stop exactly at the deadline. > > Signed-off-by:

[Qemu-devel] [Bug 1645355] Re: x86: singlestepping through SYSCALL instruction causes exception in kernelspace

Hi Andreas, man thanks for your reply. I can confirm that applying the two patches fixes my problem in the older version of the QEMU. ** Changed in: qemu Status: New => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to

Re: [Qemu-devel] [PATCH] hostmem: fix reference to uninit mr

On Fri, Mar 10, 2017 at 10:17:30AM +0100, Peter Maydell wrote: > On 10 March 2017 at 09:59, Peter Xu wrote: > > On Fri, Mar 10, 2017 at 09:33:57AM +0100, Paolo Bonzini wrote: > >> > >> > >> On 10/03/2017 05:13, Peter Xu wrote: > >> > Trying to get memory region size of an

Re: [Qemu-devel] [PATCH] hostmem: fix reference to uninit mr

On 10/03/2017 09:59, Peter Xu wrote: >> What is the effect of the bug? The idea was to do the initialization >> once only (memory_region_size ought to be 0 when the MR is >> uninitialized; now it is ugly but it made more sense when MemoryRegion >> was just a C struct and not a QOM object). >

Re: [Qemu-devel] [PATCH for-2.9? v2 0/2] vl: Print warning if a non-empty default config-file is found

On 09/03/2017 19:20, Eduardo Habkost wrote: > (This missed hard freeze, but I would still like to include the > warning in 2.9 so we can remove the default config file in 2.10. > I will include this series in a pull request only if at least 2 > other maintainers send their Acked-by.) > > We

Re: [Qemu-devel] [PATCH] hostmem: fix reference to uninit mr

On 10 March 2017 at 09:59, Peter Xu wrote: > On Fri, Mar 10, 2017 at 09:33:57AM +0100, Paolo Bonzini wrote: >> >> >> On 10/03/2017 05:13, Peter Xu wrote: >> > Trying to get memory region size of an uninitialized memory region is >> > probably not a good idea. Let's just do the

Re: [Qemu-devel] [PATCH v1 2/2] reduce qemu's heap Rss size from 12252kB to 2752KB

On 10/03/2017 16:14, Yang Zhong wrote: > There is no need to delete subregion and do memory begin/commit for > subpage in memory_region_finalize(). > > This patch is from Anthony Xu . > > Signed-off-by: Yang Zhong > --- > memory.c | 13

Re: [Qemu-devel] [PATCH] hostmem: fix reference to uninit mr

On Fri, Mar 10, 2017 at 09:33:57AM +0100, Paolo Bonzini wrote: > > > On 10/03/2017 05:13, Peter Xu wrote: > > Trying to get memory region size of an uninitialized memory region is > > probably not a good idea. Let's just do the alloc no matter what. > > > > Signed-off-by: Peter Xu

[Qemu-devel] [PATCH] scripts/dump-guest-memory.py: fix int128_get64 on recent gcc

The Int128 is no longer a struct, reaching a python exception: Python Exception Attempt to extract a component of a value that is not a (null).: Replace struct access with a cast to uint64 instead. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1427466 Signed-off-by: Marc-André Lureau

Re: [Qemu-devel] [PATCH v2] memory_region: Fix name comments

On 09/03/2017 17:38, Dr. David Alan Gilbert wrote: > It is used by all of the _ram specific functions, so it seemed worth > including the comment. It's internal though. memory.c users never use it in a way that creates a RAMBlock. > (I also see it's used in some of the boards but I don't

Re: [Qemu-devel] [PATCH v1 1/2] reduce qemu's heap Rss size from 12252kB to 2752KB

On 10/03/2017 16:14, Yang Zhong wrote: > There are a lot of memory allocation during the qemu bootup, which are > freed later by RCU thread,which means the heap size becomes biger and > biger when allocation happens, but the heap may not be shrinked even > after release happens,because some

Re: [Qemu-devel] [PATCH v2] memory: reduce heap Rss size around 3M

On 10/03/2017 14:44, Yang Zhong wrote: > Since cpu-memory and memory have same address space,one malloced > memory is enough. This patch will skip memory malloc for memory > address space,which will reduce around 3M physical memory in heap. > > Signed-off-by: Yang Zhong >

Re: [Qemu-devel] [PATCH v3] os: don't corrupt pre-existing memory-backend data with prealloc

On 10/03/2017 05:30, Stefan Hajnoczi wrote: > On Fri, Mar 03, 2017 at 11:32:55AM +, Daniel P. Berrange wrote: >> When using a memory-backend object with prealloc turned on, QEMU >> will memset() the first byte in every memory page to zero. While >> this might have been acceptable for memory

Re: [Qemu-devel] [PATCH] hostmem: fix reference to uninit mr

On 10/03/2017 05:13, Peter Xu wrote: > Trying to get memory region size of an uninitialized memory region is > probably not a good idea. Let's just do the alloc no matter what. > > Signed-off-by: Peter Xu What is the effect of the bug? The idea was to do the initialization

  1   2   >