[Qemu-devel] log every write to Aarch64 regs

Hello, List! I have a subset of Aarch64 registers and I need to print something to QEMU log every time the emulator writes new data to them. Is this problem fully or partially solvable in QEMU? What QEMU components should I look inside to implement this? Thanks in advance! -- Sincerely

Re: [Qemu-devel] [v2] tftp: fake support for netascii protocol

❦ 22 novembre 2016 10:49 GMT, Stefan Hajnoczi  : >> I guess the question is that while the patch above could be accepted for >> the upcoming 2.8 (I don't see it breaking existing systems), a patch >> that would implement the transformation would be a lot more involved, >> and

[Qemu-devel] [PATCH v2] vfio: avoid adding same iommu mr for notify

When one IOMMU memory region is splitted into multiple memory sections, vfio will register multiple same notifiers to a vIOMMU for the same region. That's not sensible. What we need is to register one IOMMU notifier for each IOMMU region, not per section. Solution is simple - we traverse the

Re: [Qemu-devel] [PULL 07/11] target-ppc: Fix CPU migration from qemu-2.6 <-> later versions

Quoting David Gibson (2016-11-22 23:10:09) > On Wed, Nov 23, 2016 at 01:49:39PM +1100, David Gibson wrote: > > When migration for target-ppc was converted to vmstate, several > > VMSTATE_EQUAL() checks were foolishly included of things that really > > should be internal state. Specifically we

Re: [Qemu-devel] [PATCH 2/9] target-ppc: Fix xscmpodp and xscmpudp instructions

On Wed, Nov 23, 2016 at 03:01:18PM +1100, David Gibson wrote: > On Tue, Nov 22, 2016 at 05:15:58PM +0530, Nikunj A Dadhania wrote: > > From: Bharata B Rao > > > > - xscmpodp & xscmpudp are missing flags reset. > > - In xscmpodp, VXCC should be set only if VE is 0 for

Re: [Qemu-devel] [Qemu-ppc] [RFC PATCH qemu] spapr_pci: Create PCI-express root bus by default

On Tue, Nov 22, 2016 at 01:26:49PM +1100, Alexey Kardashevskiy wrote: > On 22/11/16 00:08, Andrea Bolognani wrote: > > On Mon, 2016-11-21 at 13:12 +1100, Alexey Kardashevskiy wrote: > > 1) switch to PCI Express on newer machine types, and > >expose some sort of capability

Re: [Qemu-devel] [Qemu-ppc] [RFC PATCH qemu] spapr_pci: Create PCI-express root bus by default

On Fri, Nov 18, 2016 at 09:17:22AM +0100, Andrea Bolognani wrote: > On Thu, 2016-11-17 at 13:02 +1100, Alexey Kardashevskiy wrote: > > > That said, considering that a big part of the PCI address > > > allocation logic is based off whether the specific machine > > > type exposes a legay PCI Root

Re: [Qemu-devel] [PULL 07/11] target-ppc: Fix CPU migration from qemu-2.6 <-> later versions

On Wed, Nov 23, 2016 at 01:49:39PM +1100, David Gibson wrote: > When migration for target-ppc was converted to vmstate, several > VMSTATE_EQUAL() checks were foolishly included of things that really > should be internal state. Specifically we verified equality of the > insns_flags and

Re: [Qemu-devel] [PATCH 8/9] target-ppc: add vextu[bhw]lx instructions

David Gibson writes: > [ Unknown signature status ] > On Tue, Nov 22, 2016 at 05:16:04PM +0530, Nikunj A Dadhania wrote: >> From: Avinesh Kumar >> >> vextublx: Vector Extract Unsigned Byte Left >> vextuhlx: Vector Extract Unsigned

Re: [Qemu-devel] [RFC v2 0/3] virtio-net: Add support to MTU feature

On Wed, Nov 23, 2016 at 11:42:52AM +0800, Jason Wang wrote: > > > > > > > > Seems to me like an easy way to get out of sync. > > > > > > > > > > > >If we send it to the backend, that has a chance to check > > > > > >mtu and disconnect on error. > > > > > > > >For vhost-user backend, we can send

[Qemu-devel] [PATCH 3/3] qapi: Drop support for qobject_from_jsonf("%"PRId64)

The qobject_from_jsonf() function implements a pseudo-printf language for creating a QObject; however, it is hard-coded to only parse a subset of formats understood by printf(). In particular, any use of a 64-bit integer works only if the system's definition of PRId64 matches what the parser

[Qemu-devel] [PATCH 1/3] qmp-event: Avoid qobject_from_jsonf("%"PRId64)

The qobject_from_jsonf() function implements a pseudo-printf language for creating a QObject; however, it is hard-coded to only parse a subset of formats understood by printf(). In particular, any use of a 64-bit integer works only if the system's definition of PRId64 matches what the parser

Re: [Qemu-devel] [PATCH 1/9] target-ppc: Consolidate instruction decode helpers

On Tue, Nov 22, 2016 at 05:15:57PM +0530, Nikunj A Dadhania wrote: > From: Bharata B Rao > > Move instruction decode helpers to target-ppc/internal.h so that some > of these can be used from outside of translate.c. This movement also > helps to get rid of some

[Qemu-devel] [PATCH for-2.8 0/3] Fix MacOS runtime failure of qobject_from_jsonf()

programmingk...@gmail.com[*] reported a runtime failure on a 32-bit Mac OS compilation, where "%"PRId64 expands to "%qd". Fortunately, we had very few spots that were relying on our pseudo-printf JSON parsing of 64-bit numbers, so it was easier to just convert callers and rip out the 64-bit

[Qemu-devel] [PATCH 2/3] test-qga: Avoid qobject_from_jsonf("%"PRId64)

The qobject_from_jsonf() function implements a pseudo-printf language for creating a QObject; however, it is hard-coded to only parse a subset of formats understood by printf(). In particular, any use of a 64-bit integer works only if the system's definition of PRId64 matches what the parser

Re: [Qemu-devel] [PATCH 5/9] target-ppc: implement lxsd and lxssp instructions

On Tue, Nov 22, 2016 at 05:16:01PM +0530, Nikunj A Dadhania wrote: > lxsd: Load VSX Scalar Dword > lxssp: Load VSX Scalar Single > > Moreover, DS-Form instructions shares the same primary opcode, bits > 30:31 are used to decode the instruction. Use a common routine to decode > primary

Re: [Qemu-devel] [PATCH 2/9] target-ppc: Fix xscmpodp and xscmpudp instructions

On Tue, Nov 22, 2016 at 05:15:58PM +0530, Nikunj A Dadhania wrote: > From: Bharata B Rao > > - xscmpodp & xscmpudp are missing flags reset. > - In xscmpodp, VXCC should be set only if VE is 0 for signalling NaN case > and VXCC should be set by explicitly checking

Re: [Qemu-devel] [PATCH 4/9] target-ppc: Add xscmpoqp and xscmpuqp instructions

On Tue, Nov 22, 2016 at 05:16:00PM +0530, Nikunj A Dadhania wrote: > From: Bharata B Rao > > xscmpoqp - VSX Scalar Compare Ordered Quad-Precision > xscmpuqp - VSX Scalar Compare Unordered Quad-Precision > > Signed-off-by: Bharata B Rao >

Re: [Qemu-devel] [PATCH 8/9] target-ppc: add vextu[bhw]lx instructions

On Tue, Nov 22, 2016 at 05:16:04PM +0530, Nikunj A Dadhania wrote: > From: Avinesh Kumar > > vextublx: Vector Extract Unsigned Byte Left > vextuhlx: Vector Extract Unsigned Halfword Left > vextuwlx: Vector Extract Unsigned Word Left > > Signed-off-by: Avinesh

Re: [Qemu-devel] [PATCH 3/9] target-ppc: Add xscmpexp[dp, qp] instructions

On Tue, Nov 22, 2016 at 05:15:59PM +0530, Nikunj A Dadhania wrote: > From: Bharata B Rao > > xscmpexpdp: VSX Scalar Compare Exponents Double-Precision > xscmpexpqp: VSX Scalar Compare Exponents Quad-Precision > > Signed-off-by: Bharata B Rao

Re: [Qemu-devel] [RFC v2 0/3] virtio-net: Add support to MTU feature

On 2016年11月23日 04:38, Michael S. Tsirkin wrote: On Tue, Nov 22, 2016 at 06:56:43PM +0100, Maxime Coquelin wrote: > > >On 11/22/2016 03:41 PM, Michael S. Tsirkin wrote: > >On Tue, Nov 22, 2016 at 09:32:01AM -0500, Aaron Conole wrote: > > >Maxime Coquelin writes:

Re: [Qemu-devel] [RFC 14/15] ppc: Initialize default bus lists

On 22/11/16 12:12, Eduardo Habkost wrote: > Populate default_bus_types for some machines. Work in progress, I > didn't check if all machines were converted (so we could enable Yup, pseries is missed here. diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c index c3269c7..ab5939e 100644 ---

Re: [Qemu-devel] [PATCH] block/mirror: enable detect zeroes when driving mirror

On 2016年11月22日 21:44, Eric Blake wrote: On 11/21/2016 08:31 PM, wyang wrote: On 2016年11月21日 14:51, Vasiliy Tolstov wrote: 21 Ноя 2016 г. 4:27 пользователь "Yang Wei" > написал: In order to preserve sparse disk image, detect_zeroes should also be

Re: [Qemu-devel] [Qemu-block] [PATCH] block/mirror: enable detect zeroes when driving mirror

On 2016年11月22日 18:09, Kevin Wolf wrote: Am 22.11.2016 um 04:45 hat wyang geschrieben: On 2016年11月21日 19:34, Kevin Wolf wrote: Am 21.11.2016 um 02:24 hat Yang Wei geschrieben: In order to preserve sparse disk image, detect_zeroes should also be enabled when bdrv_get_block_status_above()

Re: [Qemu-devel] [PULL 00/11] ppc-for-2.8 queue 20161123

Hi, Your series seems to have some coding style problems. See output below for more information: Subject: [Qemu-devel] [PULL 00/11] ppc-for-2.8 queue 20161123 Type: series Message-id: 1479869383-16162-1-git-send-email-da...@gibson.dropbear.id.au === TEST SCRIPT BEGIN === #!/bin/bash BASE=base

[Qemu-devel] [PULL 11/11] spapr: Fix 2.7<->2.8 migration of PCI host bridge

daa2369 "spapr_pci: Add a 64-bit MMIO window" subtly broke migration from qemu-2.7 to the current version. It split the device's MMIO window into two pieces for 32-bit and 64-bit MMIO. The patch included backwards compatibility code to convert the old property into the new format. However, the

[Qemu-devel] [PULL 10/11] Revert "spapr: Fix migration of PCI host bridges from qemu-2.7"

This reverts commit 9b54ca0ba781012eeea4237b7c4832ba2ea81d89. The commit above corrected a migration breakage between qemu-2.7 and qemu-2.8. However it did so by advancing the migration version for the PCI host bridge, which obviously breaks migration backwards to earlier qemu versions.

[Qemu-devel] [PULL 07/11] target-ppc: Fix CPU migration from qemu-2.6 <-> later versions

When migration for target-ppc was converted to vmstate, several VMSTATE_EQUAL() checks were foolishly included of things that really should be internal state. Specifically we verified equality of the insns_flags and insns_flags2 fields, which are used within TCG to determine which groups of

[Qemu-devel] [PULL 06/11] ppc: Make uninorth interrupt swizzling identical to Grackle

From: Benjamin Herrenschmidt It's currently broken as it uses an incorrect shift, it tries to use the slot number but uses the top bits of the bus number instead. Note: Neither implementation matches what OpenBIOS ends up putting in the device-tree either, which will

[Qemu-devel] [PULL 00/11] ppc-for-2.8 queue 20161123

The following changes since commit 00227fefd2059464cd2f59aed29944874c630e2f: Update version for v2.8.0-rc1 release (2016-11-22 22:29:08 +) are available in the git repository at: git://github.com/dgibson/qemu.git tags/ppc-for-2.8-20161123 for you to fetch changes up to

[Qemu-devel] [PULL 02/11] spapr: migration support for CAS-negotiated option vectors

From: Michael Roth With the additional of the OV5_HP_EVT option vector, we now have certain functionality (namely, memory unplug) that checks at run-time for whether or not the guest negotiated the option via CAS. Because we don't currently migrate these negotiated

[Qemu-devel] [PULL 09/11] target-ppc: Allow eventual removal of old migration mistakes

Until very recently, the vmstate for ppc cpus included some poorly thought out VMSTATE_EQUAL() components, that can easily break migration compatibility, and did so between qemu-2.6 and later versions. A hack was recently added which fixes this migration breakage, but it leaves the unhelpful

[Qemu-devel] [PULL 08/11] migration: Add VMSTATE_UINTTL_TEST()

include/migration/cpu.h defines VMSTATE_UINTTL() and several variants for migrating target_ulong fields. It's defined in terms of VMSTATE_UINT32() or VMSTATE_UINT64() as appropriate. It doesn't, however, include a VMSTATE_UINTTL_TEST() variant, which I'm going to need shortly. So, add it.

[Qemu-devel] [PULL 03/11] ppc: BOOK3E: nothing should be done when MSR:PR is set

From: Vladimir Svoboda The server architecture (BOOK3S) specifies that any instruction that sets MSR:PR will also set MSR:EE, IR and DR. However there is no such behavior specification for the embedded architecture (BOOK3E). Signed-off-by: Vladimir Svoboda

[Qemu-devel] [PULL 01/11] tests/postcopy: Use KVM on ppc64 only if it is KVM-HV

From: Thomas Huth The ppc64 postcopy test does not work with KVM-PR, and it is also causing annoying warning messages when run on a x86 host. So let's use KVM here only if we know that we're running with KVM-HV (which automatically also means that we're running on a ppc64

[Qemu-devel] [PULL 04/11] hw/char/spapr_vty: Return amount of free buffer entries in vty_can_receive()

From: Thomas Huth The can_receive() callbacks of the character devices should return the amount of characters that can be accepted at once, not just a boolean value (which rather means only one character at a time). Signed-off-by: Thomas Huth Signed-off-by:

[Qemu-devel] [PULL 05/11] target-ppc: fix index array of national digits

From: Jose Ricardo Ziviani Fixes the big endian array access of national digits, from commits b815587 and e2106d7. Signed-off-by: Jose Ricardo Ziviani Reviewed-by: Thomas Huth Signed-off-by: David Gibson

Re: [Qemu-devel] [PATCHv2 5/5] spapr: Fix 2.7<->2.8 migration of PCI host bridge

On 23/11/16 11:17, David Gibson wrote: > On Tue, Nov 22, 2016 at 07:17:27PM +1100, Alexey Kardashevskiy wrote: >> On 21/11/16 16:31, David Gibson wrote: >>> daa2369 "spapr_pci: Add a 64-bit MMIO window" subtly broke migration >>> from qemu-2.7 to the current version. It split the device's MMIO

Re: [Qemu-devel] [Qemu-block] [PATCH RFC 0/7] COLO block replication supports shared disk case

On 2016/11/22 18:33, Stefan Hajnoczi wrote: On Thu, Oct 20, 2016 at 09:57:33PM +0800, zhanghailiang wrote: COLO block replication doesn't support the shared disk case, Here we try to implement it. Just as the scenario of non-shared disk block replication, we are going to implement block

Re: [Qemu-devel] [PATCHv2 5/5] spapr: Fix 2.7<->2.8 migration of PCI host bridge

On Tue, Nov 22, 2016 at 07:17:27PM +1100, Alexey Kardashevskiy wrote: > On 21/11/16 16:31, David Gibson wrote: > > daa2369 "spapr_pci: Add a 64-bit MMIO window" subtly broke migration > > from qemu-2.7 to the current version. It split the device's MMIO > > window into two pieces for 32-bit and

Re: [Qemu-devel] [PATCHv2 1/5] target-ppc: Fix CPU migration from qemu-2.6 <-> later versions

On Tue, Nov 22, 2016 at 07:19:38PM +1100, Alexey Kardashevskiy wrote: > On 21/11/16 16:31, David Gibson wrote: > > When migration for target-ppc was converted to vmstate, several > > VMSTATE_EQUAL() checks were foolishly included of things that really > > should be internal state. Specifically we

Re: [Qemu-devel] [PATCH 4/4] arm: Add an RX8900 RTC to the ASpeed board

On Tue, 2016-11-22 at 17:56 +0100, Cédric Le Goater wrote: > On 11/17/2016 05:36 AM, Alastair D'Silva wrote: > > > > From: Alastair D'Silva > > > > Connect an RX8900 RTC to i2c12 of the AST2500 SOC at address 0x32 > > If this is a board device, we should include it under

Re: [Qemu-devel] [PATCH 2/4] qtest: Support named interrupts

On Tue, 2016-11-22 at 23:39 +0100, Paolo Bonzini wrote: > On 22/11/2016 23:31, Alastair D'Silva wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > +if (irq == NULL) { > > > > > > > > +qtest_send_prefix(chr); > > > > > > > > +

Re: [Qemu-devel] [PATCH for-2.8 1/3] migration: alternative way to set instance_id in SaveStateEntry

Quoting David Gibson (2016-11-22 00:15:10) > On Thu, Nov 17, 2016 at 07:40:25PM -0600, Michael Roth wrote: > > From: Jianjun Duan > > > > Currently migrated Devices are identified with an idstr which is > > calculated automatically using their path in the QOM

Re: [Qemu-devel] check-qjson failure

On 11/22/2016 10:00 AM, G 3 wrote: > > Here is the backtrace for check-qjson: > > #0 0x90047dac in kill () > #1 0x9012d7b4 in abort () > #2 0x62fc in __eprintf (string= to optimizations>, expression= optimizations>, line= optimizations>, filename= optimizations>) at

Re: [Qemu-devel] qobject/qjson.c:69: failed assertion `obj != NULL'

On 11/22/2016 04:22 PM, G 3 wrote: >> On the other hand, timestamp_put() (which now lives in qapi/qmp-event.c, >> rather than monitor.c) is still using qobject_from_jsonf() with PRId64 >> in current git master. If you don't want to hack the JSON parser (and I >> recommend that you don't), the

Re: [Qemu-devel] [PATCH 2/4] qtest: Support named interrupts

On 22/11/2016 23:31, Alastair D'Silva wrote: > > > +if (irq == NULL) { > > > +qtest_send_prefix(chr); > > > +qtest_send(chr, "FAIL Unknown IRQ\n"); > > > +return; > > > +} > > > + > > > +

Re: [Qemu-devel] [RFC 00/15] qmp: Report supported device types on 'query-machines'

(CCing people from the spapr PCI-express thread) On Mon, Nov 21, 2016 at 11:11:58PM -0200, Eduardo Habkost wrote: > The Problem > === > > Currently management software has no way to find out which device > types can be plugged in a machine, unless the machine is already > initialized. >

Re: [Qemu-devel] [PATCH 2/4] qtest: Support named interrupts

On Tue, 2016-11-22 at 18:24 +0100, Paolo Bonzini wrote: > > On 22/11/2016 18:22, Cédric Le Goater wrote: > > > > > > > > + > > > +g_assert(words[1]); /* device */ > > > +g_assert(words[2]); /* gpio list */ > > > +g_assert(words[3]); /* gpio line in list */ > > > +   

[Qemu-devel] [PULL 2/3] nbd: Allow unmap and fua during write zeroes

From: Eric Blake Commit fa778fff wired up support to send the NBD_CMD_WRITE_ZEROES, but forgot to inform the block layer that FUA unmapping of zeroes is supported. Without BDRV_REQ_MAY_UNMAP listed as a supported flag, the block layer will always insist on the NBD layer

[Qemu-devel] [PULL 3/3] scsi/esp: do not raise an interrupt when reading the FIFO register

From: Hervé Poussineau This fixes SCSI adapter self-tests done in MIPS Jazz emulation, broken since ff589551c8e8e9e95e211b9d8daafb4ed39f1aec. Signed-off-by: Hervé Poussineau Message-Id: <1479508397-8443-1-git-send-email-hpous...@reactos.org>

[Qemu-devel] [PULL 1/3] cpu_ldst.h: use correct guest address parameter

From: Bobby Bingham In the user emulation code path, tlb_vaddr_to_host erronesously passed vaddr as the guest address to be translated, instead of addr, the parameter which actually contained the guest address. This resulted in incorrect addresses being used when emulating

[Qemu-devel] [PULL 0/3] Misc fixes for QEMU 2.8.0-rc1

The following changes since commit a7764f1548ef9946af30a8f96be9cef10761f0c1: Fix FreeBSD (10.x) build after 7dc9ae43 (2016-11-22 10:56:01 +) are available in the git repository at: git://github.com/bonzini/qemu.git tags/for-upstream for you to fetch changes up to

Re: [Qemu-devel] qobject/qjson.c:69: failed assertion `obj != NULL'

On Nov 21, 2016, at 3:36 PM, Eric Blake wrote: On 11/21/2016 02:12 PM, G 3 wrote: On Nov 21, 2016, at 5:02 AM, Paolo Bonzini wrote: On 21/11/2016 07:30, G 3 wrote: When I try to use qemu-system-i386, I see this error message: qobject/qjson.c:69: failed assertion `obj != NULL'. The

Re: [Qemu-devel] [Qemu-ppc] [PATCH for-2.8 2/3] migration: spapr_drc: defined VMStateDescription struct

On Tue, 22 Nov 2016 11:33:44 -0600 Michael Roth wrote: > Quoting Michael Roth (2016-11-22 11:24:23) > > Quoting Greg Kurz (2016-11-22 10:35:52) > > > On Thu, 17 Nov 2016 19:40:26 -0600 > > > Michael Roth wrote: > > > > > > > From:

Re: [Qemu-devel] [PATCH] drm: update MAINTAINERS for qemu drivers (bochs, cirrus, qxl, virtio-gpu)

On 11/22/2016 01:41 PM, Paolo Bonzini wrote: > > > On 22/11/2016 19:54, Eric Blake wrote: >> DRM DRIVER FOR BOCHS VIRTUAL GPU >> M: Gerd Hoffmann >> -S: Odd Fixes >> +L: qemu-devel@nongnu.org qemu-devel list already has very high

Re: [Qemu-devel] [RFC v2 0/3] virtio-net: Add support to MTU feature

On Tue, Nov 22, 2016 at 06:56:43PM +0100, Maxime Coquelin wrote: > > > On 11/22/2016 03:41 PM, Michael S. Tsirkin wrote: > > On Tue, Nov 22, 2016 at 09:32:01AM -0500, Aaron Conole wrote: > > > Maxime Coquelin writes: > > > > > > > On 11/22/2016 05:07 AM, Jason Wang

Re: [Qemu-devel] [PATCH] hw/pci: disable pci-bridge's shpc by default

On 22/11/2016 18:26, Marcel Apfelbaum wrote: > On 11/18/2016 05:52 PM, Andrew Jones wrote: >> On Wed, Nov 16, 2016 at 07:05:25PM +0200, Marcel Apfelbaum wrote: >>> On 11/16/2016 06:44 PM, Andrew Jones wrote: On Sat, Nov 05, 2016 at 06:46:34PM +0200, Marcel Apfelbaum wrote: > On

Re: [Qemu-devel] [Qemu-ppc] [PATCH for-2.8 2/3] migration: spapr_drc: defined VMStateDescription struct

On Tue, 22 Nov 2016 11:24:23 -0600 Michael Roth wrote: > Quoting Greg Kurz (2016-11-22 10:35:52) > > On Thu, 17 Nov 2016 19:40:26 -0600 > > Michael Roth wrote: > > > > > From: Jianjun Duan > > > > > > To manage

Re: [Qemu-devel] [PATCH] drm: update MAINTAINERS for qemu drivers (bochs, cirrus, qxl, virtio-gpu)

On 22/11/2016 19:54, Eric Blake wrote: >>> >> DRM DRIVER FOR BOCHS VIRTUAL GPU >>> >> M: Gerd Hoffmann >>> >> -S: Odd Fixes >>> >> +L: qemu-devel@nongnu.org >> > >> > qemu-devel list already has very high traffic - not sure whether it >> > makes much sense

Re: [Qemu-devel] [PULL 0/5] xen-20161122-tag

> > git://xenbits.xen.org/people/sstabellini/qemu-dm.git tags/xen-20161122-tag > > for you to fetch changes up to f1784a222eed213ce3213f431bc2f9c570f20c3e: > > xen: attach pvusb usb bus to backend qdev (2016-11-22 10:29:41 -0800) > >

Re: [Qemu-devel] [Qemu-block] [PULL 0/4] Block layer patches for 2.8.0-rc1

On Tue, Nov 22, 2016 at 05:04:49PM +0100, Kevin Wolf wrote: > The following changes since commit a7764f1548ef9946af30a8f96be9cef10761f0c1: > > Fix FreeBSD (10.x) build after 7dc9ae43 (2016-11-22 10:56:01 +) > > are available in the git repository at: > > git://repo.or.cz/qemu/kevin.git

Re: [Qemu-devel] [PULL 1/1] seabios: update to 1.10.1 stable release

On Tue, Nov 22, 2016 at 04:23:25PM +0100, Gerd Hoffmann wrote: > On Di, 2016-11-22 at 11:02 +, Stefan Hajnoczi wrote: > > On Tue, Nov 22, 2016 at 10:15:44AM +0100, Gerd Hoffmann wrote: > > > diff --git a/roms/seabios b/roms/seabios > > > index d7adf60..8891697 16 > > > --- a/roms/seabios >

Re: [Qemu-devel] [PULL 0/1] seabios: update to 1.10.1 stable release

lowing changes since commit c36ed06e9159fa484b711dfdd27ec64d7ac3d17a: > > Merge remote-tracking branch 'mst/tags/for_upstream' into staging > (2016-11-21 11:09:58 +) > > are available in the git repository at: > > > git://git.kraxel.org/qemu tags/pull-

Re: [Qemu-devel] [PATCH v3 00/10] aio: experimental virtio-blk polling mode

On 11/22/2016 05:31 PM, Stefan Hajnoczi wrote: > v3: > * Avoid ppoll(2)/epoll_wait(2) if polling succeeded [Paolo] > * Disable guest->host virtqueue notification during polling [Christian] > * Rebased on top of my virtio-blk/scsi virtqueue notification disable patches > > v2: > *

Re: [Qemu-devel] [PATCH] drm: update MAINTAINERS for qemu drivers (bochs, cirrus, qxl, virtio-gpu)

On 11/22/2016 04:50 AM, Thomas Huth wrote: > On 22.11.2016 10:58, Gerd Hoffmann wrote: >> Changes: >> * add myself as maintainer, so patches land in my inbox. >> * add qemu-devel mailing list. >> * add drm-qemu git repo. >> * flip bochs and qxl status to "Maintained". >> >> Signed-off-by: Gerd

[Qemu-devel] [PULL 5/5] xen: attach pvusb usb bus to backend qdev

From: Juergen Gross Attach the usb bus of a new pvusb controller to the qdev associated with the Xen backend. Any device connected to that controller can now specify the bus and port directly via its properties. Signed-off-by: Juergen Gross Reviewed-by:

[Qemu-devel] [PULL 3/5] qdev: add function qdev_set_id()

From: Juergen Gross In order to have an easy way to add a new qdev with a specific id carve out the needed functionality from qdev_device_add() into a new function qdev_set_id(). Signed-off-by: Juergen Gross Reviewed-by: Stefano Stabellini

[Qemu-devel] [PULL 4/5] xen: create qdev for each backend device

From: Juergen Gross Create a qdev plugged to the xen-sysbus for each new backend device. This device can be used as a parent for all needed devices of that backend. The id of the new device will be "xen--" with being the xen backend type (e.g. "qdisk") and the xen backend

[Qemu-devel] [PULL 1/5] xen: fix ioreq handling

From: Jan Beulich Avoid double fetches and bounds check size to avoid overflowing internal variables. This is CVE-2016-9381 / XSA-197. Reported-by: yanghongke Signed-off-by: Jan Beulich Reviewed-by: Stefano Stabellini

[Qemu-devel] [PULL 2/5] xen: add an own bus for xen backend devices

From: Juergen Gross Add a bus for Xen backend devices in order to be able to establish a dedicated device path for pluggable devices. Signed-off-by: Juergen Gross Reviewed-by: Stefano Stabellini Signed-off-by: Stefano Stabellini

[Qemu-devel] [PULL 0/5] xen-20161122-tag

changes since commit a7764f1548ef9946af30a8f96be9cef10761f0c1: Fix FreeBSD (10.x) build after 7dc9ae43 (2016-11-22 10:56:01 +) are available in the git repository at: git://xenbits.xen.org/people/sstabellini/qemu-dm.git tags/xen-20161122-tag for you to fetch changes up to f1784a222eed213ce321

Re: [Qemu-devel] [kvm-unit-tests PATCH v6 00/11] arm/arm64: add gic framework

Andre, Alex, Eric, anybody, Any more comments on this? If not, I'll send a pull request to Radim and Paolo to finally get this merged. Thanks, drew On Mon, Nov 14, 2016 at 10:08:28PM +0100, Andrew Jones wrote: > v6: > - rebased to latest master > - several other changes thanks to Andre and

[Qemu-devel] [kvm-unit-tests PATCH v11 0/3] ARM PMU tests

Changes from v10: * Change the name of loop test function to precise_instrs_loop() * Minor comment fixes to measure_instrs() and to explain isb() in loop funcs Note: 1) Current KVM code has bugs in handling PMCCFILTR write. A fix (see below) is required for this unit testing code to work

Re: [Qemu-devel] [PULL for-2.8 0/2] target-alpha update

Sorry, I forgot to update the url of the submodule. Just editing .git/config isn't enough. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."

Re: [Qemu-devel] [RFC v2 0/3] virtio-net: Add support to MTU feature

On 11/22/2016 03:41 PM, Michael S. Tsirkin wrote: On Tue, Nov 22, 2016 at 09:32:01AM -0500, Aaron Conole wrote: Maxime Coquelin writes: On 11/22/2016 05:07 AM, Jason Wang wrote: On 2016年11月22日 00:23, Michael S. Tsirkin wrote: On Fri, Nov 18, 2016 at

[Qemu-devel] [kvm-unit-tests PATCH v11 3/3] arm: pmu: Add CPI checking

From: Christopher Covington Calculate the numbers of cycles per instruction (CPI) implied by ARM PMU cycle counter values. The code includes a strict checking facility intended for the -icount option in TCG mode in the configuration file. Signed-off-by: Christopher

[Qemu-devel] [kvm-unit-tests PATCH v11 1/3] arm: Add PMU test

From: Christopher Covington Beginning with a simple sanity check of the control register, add a unit test for the ARM Performance Monitors Unit (PMU). Signed-off-by: Christopher Covington Signed-off-by: Wei Huang Reviewed-by: Andrew

[Qemu-devel] [kvm-unit-tests PATCH v11 2/3] arm: pmu: Check cycle count increases

From: Christopher Covington Ensure that reads of the PMCCNTR_EL0 are monotonically increasing, even for the smallest delta of two subsequent reads. Signed-off-by: Christopher Covington Signed-off-by: Wei Huang Reviewed-by: Andrew

[Qemu-devel] [PATCH 12/17] migration: add postcopy migration of dirty bitmaps

Postcopy migration of dirty bitmaps. Only named dirty bitmaps, associated with root nodes and non-root named nodes are migrated. If destination qemu is already containing a dirty bitmap with the same name as a migrated bitmap (for the same node), than, if their granularities are the same the

[Qemu-devel] [PATCH 14/17] qmp: add x-debug-block-dirty-bitmap-sha256

Signed-off-by: Vladimir Sementsov-Ogievskiy --- block/dirty-bitmap.c | 5 + blockdev.c | 33 + include/block/dirty-bitmap.h | 2 ++ include/qemu/hbitmap.h | 8 qapi/block-core.json |

[Qemu-devel] [PATCH 11/17] migration: add is_active_iterate handler

Only-postcopy savevm states (dirty-bitmap) don't need live iteration, so to disable them and stop transporting empty sections there is a new savevm handler. Signed-off-by: Vladimir Sementsov-Ogievskiy --- include/migration/vmstate.h | 1 + migration/savevm.c |

[Qemu-devel] [PATCH 01/17] migration: add has_postcopy savevm handler

Now postcopy-able states are recognized by not NULL save_live_complete_postcopy handler. But when we have several different postcopy-able states, it is not convenient. Ram postcopy may be disabled, while some other postcopy enabled, in this case Ram state should behave as it is not postcopy-able.

[Qemu-devel] [PATCH 07/17] qapi: add dirty-bitmaps migration capability

Reviewed-by: John Snow Reviewed-by: Eric Blake Signed-off-by: Vladimir Sementsov-Ogievskiy --- include/migration/migration.h | 1 + migration/migration.c | 9 + qapi-schema.json | 4 +++- 3 files

[Qemu-devel] [PATCH 08/17] block/dirty-bitmap: add bdrv_dirty_bitmap_release_successor

To just release successor and unfreeze bitmap without any additional work. Signed-off-by: Vladimir Sementsov-Ogievskiy Signed-off-by: Denis V. Lunev --- block/dirty-bitmap.c | 10 ++ include/block/dirty-bitmap.h | 2 ++ 2 files

[Qemu-devel] [PATCH 02/17] migration: fix ram_save_pending

Fill postcopy-able pending only if ram postcopy is enabled. It is necessary because of there will be other postcopy-able states and when ram postcopy is disabled, it should not spoil common postcopy related pending. Reviewed-by: Dr. David Alan Gilbert Reviewed-by: Juan

[Qemu-devel] [PATCH 09/17] migration: include migrate_dirty_bitmaps in migrate_postcopy

Enable postcopy if dirty bitmap migration is endabled. Signed-off-by: Vladimir Sementsov-Ogievskiy --- migration/migration.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/migration/migration.c b/migration/migration.c index 38398cc..080d487 100644

[Qemu-devel] [PATCH 04/17] migration: introduce postcopy-only pending

There would be savevm states (dirty-bitmap) which can migrate only in postcopy stage. The corresponding pending is introduced here. Signed-off-by: Vladimir Sementsov-Ogievskiy --- include/migration/vmstate.h | 5 +++-- include/sysemu/sysemu.h | 5 +++--

Re: [Qemu-devel] [Qemu-ppc] [PATCH for-2.8 2/3] migration: spapr_drc: defined VMStateDescription struct

Quoting Michael Roth (2016-11-22 11:24:23) > Quoting Greg Kurz (2016-11-22 10:35:52) > > On Thu, 17 Nov 2016 19:40:26 -0600 > > Michael Roth wrote: > > > > > From: Jianjun Duan > > > > > > To manage hotplug/unplug of dynamic resources such

[Qemu-devel] [PATCH 05/17] block: add bdrv_next_dirty_bitmap()

Like bdrv_next() - bdrv_next_dirty_bitmap() is a function to provide access to private dirty bitmaps list. Reviewed-by: John Snow Signed-off-by: Vladimir Sementsov-Ogievskiy --- block/dirty-bitmap.c | 10 ++

[Qemu-devel] [PATCH 09/21] qcow2: add .bdrv_load_autoloading_dirty_bitmaps

Auto loading bitmaps are bitmaps in Qcow2, with the AUTO flag set. They are loaded when the image is opened and become BdrvDirtyBitmaps for the corresponding drive. Extra data in bitmaps is not supported for now. Signed-off-by: Vladimir Sementsov-Ogievskiy ---

[Qemu-devel] [PATCH 11/21] block: introduce persistent dirty bitmaps

New field BdrvDirtyBitmap.persistent means, that bitmap should be saved on bdrv_close, using format driver. Format driver should maintain bitmap storing. Signed-off-by: Vladimir Sementsov-Ogievskiy --- block.c | 31 +++

[Qemu-devel] [PATCH 06/17] block: add bdrv_dirty_bitmap_enable_successor()

Enabling bitmap successor is necessary to enable successors of bitmaps being migrated before target vm start. Signed-off-by: Vladimir Sementsov-Ogievskiy --- block/dirty-bitmap.c | 5 + include/block/dirty-bitmap.h | 1 + 2 files changed, 6 insertions(+)

[Qemu-devel] [PATCH 17/17] iotests: add dirty bitmap postcopy test

Test - start two vms (vm_a, vm_b) - in a - do writes from set A - do writes from set B - fix bitmap md5 - clear bitmap - do writes from set A - start migration - than, in b - wait vm start (postcopy should start) - do writes from set B - check btimap md5 The

[Qemu-devel] [PATCH v4 00/17] Dirty bitmaps postcopy migration

Hi all! There is a new version of dirty bitmap postcopy migration series. v4: clone: tag postcopy-v4 from https://src.openvz.org/scm/~vsementsov/qemu.git online: https://src.openvz.org/users/vsementsov/repos/qemu/browse?at=postcopy-v4 reroll, to fix "failed automatic build test" rebase on

[Qemu-devel] [PATCH 14/21] block: add bdrv_can_store_dirty_bitmap

This will be needed to check some restrictions before making bitmap persistent in qmp-block-dirty-bitmap-add (this functionality will be added by future patch) Signed-off-by: Vladimir Sementsov-Ogievskiy --- block.c | 22 ++

[Qemu-devel] [PATCH 16/17] iotests: add dirty bitmap migration test

The test starts two vms (vm_a, vm_b), create dirty bitmap in the first one, do several writes to corresponding device and then migrate vm_a to vm_b with dirty bitmaps. Signed-off-by: Vladimir Sementsov-Ogievskiy --- tests/qemu-iotests/169 | 86

[Qemu-devel] [PATCH 03/17] migration: split common postcopy out of ram postcopy

Split common postcopy staff from ram postcopy staff. Signed-off-by: Vladimir Sementsov-Ogievskiy --- include/migration/migration.h | 1 + migration/migration.c | 39 +++ migration/postcopy-ram.c | 4 +++-

[Qemu-devel] [PATCH 13/17] iotests: add add_incoming_migration to VM class

Reviewed-by: John Snow Signed-off-by: Vladimir Sementsov-Ogievskiy --- tests/qemu-iotests/iotests.py | 6 ++ 1 file changed, 6 insertions(+) diff --git a/tests/qemu-iotests/iotests.py b/tests/qemu-iotests/iotests.py index bec8eb4..f5ca4b8 100644

[Qemu-devel] [PATCH 10/17] migration/qemu-file: add qemu_put_counted_string()

Add function opposite to qemu_get_counted_string. qemu_put_counted_string puts one-byte length of the string (string should not be longer than 255 characters), and then it puts the string, without last zero byte. Reviewed-by: John Snow Signed-off-by: Vladimir

  1   2   3   >