[Qemu-devel] [PULL 05/69] qemu-doc: update deprecation section to use -nic and -netdev hubport

The deprecated SLIRP options -tftp, -bootp, -redir, -smb provide sample replacements that use "-net nic". Suggest "-nic" instead, since we finally have a path towards getting rid of "-net". For "-net vlan" the replacement involves hubport network devices, so mention that too. Cc: Jason Wang

[Qemu-devel] [PULL 15/69] chardev: use chardev's gcontext for async connect

From: Peter Xu Generalize the function to create the async QIO task connection. Also, fix the context pointer to use the chardev's gcontext. Reviewed-by: Paolo Bonzini Signed-off-by: Peter Xu Message-Id:

[Qemu-devel] [PULL 07/69] build-sys: make help could have 'modules' target

From: Marc-André Lureau Available when configure --enable-modules. Signed-off-by: Marc-André Lureau Message-Id: <20180306161728.20890-1-marcandre.lur...@redhat.com> Signed-off-by: Paolo Bonzini --- Makefile | 3

[Qemu-devel] [PULL 10/69] vl: export machine_init_done

From: Peter Xu We have that variable but not exported. Export that so modules can have a way to poke on whether machine init has finished. Meanwhile, set that up even before calling the notifiers, so that notifiers who may depend on this field will get a correct answer.

[Qemu-devel] [PULL 11/69] chardev: fix handling of EAGAIN for TCP chardev

From: Daniel P. Berrangé When this commit was applied commit 9894dc0cdcc397ee5b26370bc53da6d360a363c2 Author: Daniel P. Berrange Date: Tue Jan 19 11:14:29 2016 + char: convert from GIOChannel to QIOChannel The tcp_chr_recv() function

[Qemu-devel] [PULL 04/69] scsi-disk.c: consider bl->max_transfer in INQUIRY emulation

From: Daniel Henrique Barboza The calculation of the max_transfer atribute of BlockDriverState makes considerations such as max_segments and transfer_length via the BLKSECTGET ioctl (if available). However, bl->max_transfer isn't considered when emulating the

[Qemu-devel] [PULL 02/69] net: allow using any PCI NICs in -net or -nic

Remove the hard-coded list of PCI NIC names; instead, fill an array using all PCI devices listed under DEVICE_CATEGORY_NETWORK. Keep the old shortcut "virtio" for virtio-net-pci. Suggested-by: Thomas Huth Reviewed-by: Thomas Huth Reviewed-by: Jason Wang

[Qemu-devel] [PULL 06/69] qemu-doc: Add the paragraph about the -no-frame deprecation again

From: Thomas Huth The section has accidentially been removed while resolving a contextual conflict during a rebase, so add this again. Fixes: f29d4450428fe07e9d6b0655cef2e59bfa0b2ea5 Signed-off-by: Thomas Huth Message-Id:

[Qemu-devel] [PULL 03/69] q35: change default NIC to e1000e

The e1000 NIC is getting old and is not a very good default for a PCIe machine type. Change it to e1000e, which should be supported by a good number of guests. In particular, drivers for 82574 were added first to Linux 2.6.27 (2008) and Windows 2008 R2. This does mean that Windows 2008 will not

[Qemu-devel] [PULL 00/69] Misc patches for QEMU soft freeze

Not sure why this didn't make it to the list yesterday---most likely I didn't remove --dry-run... Now I understand why everybody was waiting for my pull request. The following changes since commit 819fd4699c7b36d574292bcbd8bc25e9d716c84b: Merge remote-tracking branch

[Qemu-devel] [PULL 01/69] qom: introduce object_class_get_list_sorted

Unify half a dozen copies of very similar code (the only difference being whether comparisons were case-sensitive) and use it also in Tricore, which did not do any sorting of CPU model names. Reviewed-by: Philippe Mathieu-Daudé Signed-off-by: Paolo Bonzini

Re: [Qemu-devel] [PATCH v4 0/5] Enable TOPOEXT to support hyperthreading on AMD CPU

Tested-by: Kash Pande signature.asc Description: OpenPGP digital signature

[Qemu-devel] [PULL 22/22] test/acpi-test-data: add ACPI tables for dimmpxm test

From: Haozhong Zhang Reviewers can use ACPI tables in this patch to run test_acpi_{piix4,q35}_tcg_dimm_pxm cases. Signed-off-by: Haozhong Zhang Reviewed-by: Michael S. Tsirkin Signed-off-by: Michael S. Tsirkin

[Qemu-devel] [PULL 17/22] hw/pci: remove obsolete PCIDevice->init()

From: Philippe Mathieu-Daudé All PCI devices are now QOM'ified. Signed-off-by: Philippe Mathieu-Daudé Reviewed-by: Marcel Apfelbaum Reviewed-by: Michael S. Tsirkin Signed-off-by: Michael S. Tsirkin ---

[Qemu-devel] [PULL 16/22] standard-headers: update virtio_net.h

include speed/duplex fields Signed-off-by: Michael S. Tsirkin --- include/standard-headers/linux/virtio_net.h | 13 + 1 file changed, 13 insertions(+) diff --git a/include/standard-headers/linux/virtio_net.h b/include/standard-headers/linux/virtio_net.h index

Re: [Qemu-devel] [PULL 00/36] QAPI patches for 2018-03-12, 2.12 softfreeze

On 03/13/2018 09:17 AM, Eric Blake wrote: This builds and passes 'make check', so even though the OOB portion depends on chardev fixes that are still pending a pull request from Paolo, that dependence can only be observed at runtime by clients that use the new oob feature.  Given the timing of

Re: [Qemu-devel] [RFC PATCH] i2c: device passthrough HACK(!) & evaluation

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: 20180313200245.2350-1-wsa+rene...@sang-engineering.com Subject: [Qemu-devel] [RFC PATCH]

[Qemu-devel] [PULL 09/22] pc: acpi: isolate FADT specific data into AcpiFadtData structure

From: Igor Mammedov move FADT data initialization out of fadt_setup() into dedicated init_fadt_data() that will set common for pc/q35 values in AcpiFadtData structure and acpi_get_pm_info() will complement it with pc/q35 specific values initialization. That will allow to

[Qemu-devel] [PULL 21/22] tests/bios-tables-test: add test cases for DIMM proximity

From: Haozhong Zhang QEMU now builds one SRAT memory affinity structure for each PC-DIMM and NVDIMM device presented at boot time with the proximity domain specified in the device option 'node', rather than only one SRAT memory affinity structure covering the entire

Re: [Qemu-devel] [PATCH] checkpatch: warn about missing MAINTAINERS file changes

Hi, This series seems to have some coding style problems. See output below for more information: Type: series Message-id: 20180312131806.23209-1-stefa...@redhat.com Subject: [Qemu-devel] [PATCH] checkpatch: warn about missing MAINTAINERS file changes === TEST SCRIPT BEGIN === #!/bin/bash

[Qemu-devel] [PULL 15/22] qemu-options-wrapper.h: fix include patch

qemu-options.def is included from build directory not from source directory. Use include <> accordingly: include "" means look in the current (source) directory search first. cc: Peter Maydell Signed-off-by: Michael S. Tsirkin ---

[Qemu-devel] [PULL 10/22] pc: acpi: use build_append_foo() API to construct FADT

From: Igor Mammedov build_append_foo() API doesn't need explicit endianness conversions which eliminates a source of errors and it makes build_fadt() look like declarative definition of FADT table in ACPI spec, which makes it easy to review. Also it allows easily extending

[Qemu-devel] [PULL 20/22] hw/acpi-build: build SRAT memory affinity structures for DIMM devices

From: Haozhong Zhang ACPI 6.2A Table 5-129 "SPA Range Structure" requires the proximity domain of a NVDIMM SPA range must match with corresponding entry in SRAT table. The address ranges of vNVDIMM in QEMU are allocated from the hot-pluggable address space, which is

[Qemu-devel] [PULL 13/22] tests: acpi: don't read all fields in test_acpi_fadt_table()

From: Igor Mammedov there is no point to read fields here but not actually checking them so drop it and read only header + dsdt/facs addresses since it's needed later to fetch that tables. With this cleanup we can get rid of AcpiFadtDescriptorRev3/ ACPI_FADT_COMMON_DEF

[Qemu-devel] [PULL 19/22] qmp: distinguish PC-DIMM and NVDIMM in MemoryDeviceInfoList

From: Haozhong Zhang It may need to treat PC-DIMM and NVDIMM differently, e.g., when deciding the necessity of non-volatile flag bit in SRAT memory affinity structures. A new field 'nvdimm' is added to the union type MemoryDeviceInfo for such purpose. Its type is

[Qemu-devel] [PULL 01/22] scripts/update-linux-headers: add ethtool.h and update to 4.16.0-rc4

From: Jason Baron A subsequent patch to add support for setting linkspeed/duplex in virtio-net, requires a few definitions from ethtool.h, which ends up pulling in kernel.h and sysinfo.h as well. Signed-off-by: Jason Baron Cc: "Michael S. Tsirkin"

[Qemu-devel] [PULL 11/22] acpi: move build_fadt() from i386 specific to generic ACPI source

From: Igor Mammedov It will be extended and reused by follow up patch for ARM target. PS: Since it's generic function now, don't patch FIRMWARE_CTRL, DSDT fields if they don't point to tables since platform might not provide them and use X_ variants instead if applicable.

[Qemu-devel] [PULL 18/22] pc-dimm: make qmp_pc_dimm_device_list() sort devices by address

From: Haozhong Zhang Make qmp_pc_dimm_device_list() return sorted by start address list of devices so that it could be reused in places that would need sorted list*. Reuse existing pc_dimm_built_list() to get sorted list. While at it hide recursive callbacks from

[Qemu-devel] [PULL 08/22] acpi: move ACPI_PORT_SMI_CMD define to header it belongs to

From: Igor Mammedov ACPI_PORT_SMI_CMD is alias for APM_CNT_IOPORT, so make it really one instead of duplicating its value. Signed-off-by: Igor Mammedov Reviewed-by: Eric Auger Tested-by: Eric Auger

[Qemu-devel] [PULL 07/22] acpi: add build_append_gas() helper for Generic Address Structure

From: Igor Mammedov it will help to add Generic Address Structure to ACPI tables without using packed C structures and avoid endianness issues as API doesn't need an explicit conversion. Signed-off-by: Igor Mammedov Reviewed-by: Eric Auger

[Qemu-devel] [PULL 14/22] vhost: used_memslots refactoring

From: Jay Zhou Used_memslots is shared by vhost kernel and user, it is equal to dev->mem->nregions, which is correct for vhost kernel, but not for vhost user, the latter one uses memory regions that have file descriptor. E.g. a VM has a vhost-user NIC and 8(vhost user

[Qemu-devel] [PULL 03/22] virtio-net: add linkspeed and duplex settings to virtio-net

From: Jason Baron Although linkspeed and duplex can be set in a linux guest via 'ethtool -s', this requires custom ethtool commands for virtio-net by default. Introduce a new feature flag, VIRTIO_NET_F_SPEED_DUPLEX, which allows the hypervisor to export a linkspeed and duplex

[Qemu-devel] [PULL 12/22] virt_arm: acpi: reuse common build_fadt()

From: Igor Mammedov Extend generic build_fadt() to support rev5.1 FADT and reuse it for 'virt' board, it would allow to phase out usage of AcpiFadtDescriptorRev5_1 and later ACPI_FADT_COMMON_DEF. Signed-off-by: Igor Mammedov Reviewed-by: Eric Auger

[Qemu-devel] [PULL 05/22] pc: replace pm object initialization with one-liner in acpi_get_pm_info()

From: Igor Mammedov next patch will need it before it gets to piix4/lpc branches that initializes 'obj' now. Signed-off-by: Igor Mammedov Reviewed-by: Eric Auger Reviewed-by: Philippe Mathieu-Daudé Tested-by:

[Qemu-devel] [PULL 06/22] acpi: reuse AcpiGenericAddress instead of Acpi20GenericAddress

From: Igor Mammedov Drop duplicate in form of Acpi20GenericAddress and reuse AcpiGenericAddress. Signed-off-by: Igor Mammedov Reviewed-by: Eric Auger Tested-by: Eric Auger Reviewed-by: Michael S. Tsirkin

[Qemu-devel] [PULL 02/22] virtio-net: use 64-bit values for feature flags

From: Jason Baron In prepartion for using some of the high order feature bits, make sure that virtio-net uses 64-bit values everywhere. Signed-off-by: Jason Baron Cc: "Michael S. Tsirkin" Cc: Jason Wang Cc:

[Qemu-devel] [PULL 04/22] acpi: remove unused acpi-dsdt.aml

From: Igor Mammedov SeaBIOS blob which is currently shipped with QEMU doesn't need acpi-dsdt.aml nor is able to use it and code that loaded it in QEMU was removed by (commit 9fb7aaaf4c "pc: drop external DSDT loading") in 2013. Signed-off-by: Igor Mammedov

[Qemu-devel] [PULL 00/22] virtio,vhost,pci,pc: features, cleanups

The following changes since commit 026aaf47c02b79036feb830206cfebb2a726510d: Merge remote-tracking branch 'remotes/ehabkost/tags/python-next-pull-request' into staging (2018-03-13 16:26:44 +) are available in the git repository at: git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git

Re: [Qemu-devel] [PATCH v3] vmgenid: allow VM Generation ID modification via QMP/HMP

On Fri, Mar 02, 2018 at 10:37:20AM +0200, Or Idgar wrote: > From: Or Idgar > > This patch allow changing the Virtual Machine Generation > ID through QMP/HMP while the vm guest is running. > the spec (http://go.microsoft.com/fwlink/?LinkId=260709) > mentions that "when the

Re: [Qemu-devel] [PATCH 1/3] nvram: at24c: remove doubled prefix for ERR

> > -ERR(TYPE_AT24C_EE > > -" : failed to write backing file\n"); > > +ERR("failed to write backing file\n"); > > printf/fprintf are deprecated, since you are modifying this file can you > use a newer API, "qemu/error-report.h" for example.

[Qemu-devel] [PULL 11/13] migration: add postcopy migration of dirty bitmaps

From: Vladimir Sementsov-Ogievskiy Postcopy migration of dirty bitmaps. Only named dirty bitmaps are migrated. If destination qemu is already containing a dirty bitmap with the same name as a migrated bitmap (for the same node), then, if their granularities are the

[Qemu-devel] [PULL 02/13] block/dirty-bitmap: fix locking in bdrv_reclaim_dirty_bitmap

From: Vladimir Sementsov-Ogievskiy Like other setters here these functions should take a lock. Signed-off-by: Vladimir Sementsov-Ogievskiy Reviewed-by: Fam Zheng Reviewed-by: John Snow Message-id:

[Qemu-devel] [PULL 12/13] iotests: add dirty bitmap migration test

From: Vladimir Sementsov-Ogievskiy 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. Signed-off-by: Vladimir Sementsov-Ogievskiy Message-id:

[Qemu-devel] [PULL 07/13] migration: include migrate_dirty_bitmaps in migrate_postcopy

From: Vladimir Sementsov-Ogievskiy Enable postcopy if dirty bitmap migration is enabled. Signed-off-by: Vladimir Sementsov-Ogievskiy Reviewed-by: Juan Quintela Reviewed-by: John Snow Reviewed-by: Fam

[Qemu-devel] [PULL 13/13] iotests: add dirty bitmap postcopy test

From: Vladimir Sementsov-Ogievskiy Test - start two vms (vm_a, vm_b) - in a - do writes from set A - do writes from set B - fix bitmap sha256 - clear bitmap - do writes from set A - start migration - than, in b - wait vm start (postcopy

[Qemu-devel] [PULL 09/13] migration: add is_active_iterate handler

From: Vladimir Sementsov-Ogievskiy 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

[Qemu-devel] [PULL 04/13] dirty-bitmap: add locked state

From: Vladimir Sementsov-Ogievskiy Add special state, when qmp operations on the bitmap are disabled. It is needed during bitmap migration. "Frozen" state is not appropriate here, because it looks like bitmap is unchanged. Signed-off-by: Vladimir Sementsov-Ogievskiy

Re: [Qemu-devel] [PATCH 3/3] nvram: at24c: use a sane default for "rom-size"

Hi Philippe, > > static Property at24c_eeprom_props[] = { > > -DEFINE_PROP_UINT32("rom-size", EEPROMState, rsize, 0), > > +DEFINE_PROP_UINT32("rom-size", EEPROMState, rsize, 128), > > This patch should goes before your 2/3 in your series. I don't mind much, but why? My reasoning was

[Qemu-devel] [PULL 05/13] migration: introduce postcopy-only pending

From: Vladimir Sementsov-Ogievskiy 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 Reviewed-by: Dr. David Alan

[Qemu-devel] [PULL 08/13] migration/qemu-file: add qemu_put_counted_string()

From: Vladimir Sementsov-Ogievskiy 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. Signed-off-by:

[Qemu-devel] [PULL 03/13] block/dirty-bitmap: add _locked version of bdrv_reclaim_dirty_bitmap

From: Vladimir Sementsov-Ogievskiy Signed-off-by: Vladimir Sementsov-Ogievskiy Reviewed-by: John Snow Message-id: 20180207155837.92351-4-vsement...@virtuozzo.com Signed-off-by: John Snow ---

[Qemu-devel] [PULL 06/13] qapi: add dirty-bitmaps migration capability

From: Vladimir Sementsov-Ogievskiy Signed-off-by: Vladimir Sementsov-Ogievskiy Reviewed-by: John Snow Reviewed-by: Eric Blake Reviewed-by: Juan Quintela Reviewed-by: Fam Zheng

[Qemu-devel] [PULL 10/13] migration: allow qmp command migrate-start-postcopy for any postcopy

From: Vladimir Sementsov-Ogievskiy Allow migrate-start-postcopy for any postcopy type Signed-off-by: Vladimir Sementsov-Ogievskiy Reviewed-by: Dr. David Alan Gilbert Message-id:

[Qemu-devel] [PULL 01/13] block/dirty-bitmap: add bdrv_dirty_bitmap_enable_successor()

From: Vladimir Sementsov-Ogievskiy Enabling bitmap successor is necessary to enable successors of bitmaps being migrated before target vm start. Signed-off-by: Vladimir Sementsov-Ogievskiy Reviewed-by: John Snow

[Qemu-devel] [PULL 00/13] Bitmaps patches

The following changes since commit 026aaf47c02b79036feb830206cfebb2a726510d: Merge remote-tracking branch 'remotes/ehabkost/tags/python-next-pull-request' into staging (2018-03-13 16:26:44 +) are available in the Git repository at: https://github.com/jnsnow/qemu.git

Re: [Qemu-devel] [PATCH v5 00/29] postcopy+vhost-user/shared ram

On Mon, Mar 12, 2018 at 05:20:55PM +, Dr. David Alan Gilbert (git) wrote: > From: "Dr. David Alan Gilbert" > > This set enables postcopy migration with shared memory to a vhost user > process. > It's based off current head. > > Testing is mostly performed with

[Qemu-devel] [PULL v2 00/17] NBD patches for 2018-03-13 (2.12 softfreeze)

The following changes since commit 026aaf47c02b79036feb830206cfebb2a726510d: Merge remote-tracking branch 'remotes/ehabkost/tags/python-next-pull-request' into staging (2018-03-13 16:26:44 +) are available in the Git repository at: git://repo.or.cz/qemu/ericb.git

[Qemu-devel] [PULL v2 14/17] nbd: BLOCK_STATUS for standard get_block_status function: client part

From: Vladimir Sementsov-Ogievskiy Minimal realization: only one extent in server answer is supported. Flag NBD_CMD_FLAG_REQ_ONE is used to force this behavior. Signed-off-by: Vladimir Sementsov-Ogievskiy Message-Id:

Re: [Qemu-devel] [PATCH v5 09/29] postcopy: Allow registering of fd handler

On Mon, Mar 12, 2018 at 05:21:04PM +, Dr. David Alan Gilbert (git) wrote: > From: "Dr. David Alan Gilbert" > > Allow other userfaultfd's to be registered into the fault thread > so that handlers for shared memory can get responses. > > Signed-off-by: Dr. David Alan

[Qemu-devel] [PULL 11/11] ppc/spapr, vfio: Turn off MSIX emulation for VFIO devices

From: Alexey Kardashevskiy This adds a possibility for the platform to tell VFIO not to emulate MSIX so MMIO memory regions do not get split into chunks in flatview and the entire page can be registered as a KVM memory slot and make direct MMIO access possible for the guest.

[Qemu-devel] [PULL 10/11] vfio-pci: Allow mmap of MSIX BAR

From: Alexey Kardashevskiy At the moment we unconditionally avoid mapping MSIX data of a BAR and emulate MSIX table in QEMU. However it is 1) not always necessary as a platform may provide a paravirt interface for MSIX configuration; 2) can affect the speed of MMIO access by

[Qemu-devel] [PULL 08/11] vfio/display: adding dmabuf support

From: Gerd Hoffmann Wire up dmabuf-based display. Signed-off-by: Gerd Hoffmann Signed-off-by: Alex Williamson --- hw/vfio/display.c | 182 + include/hw/vfio/vfio-common.h |

[Qemu-devel] [PULL 06/11] vfio/display: core & wireup

From: Gerd Hoffmann Infrastructure for display support. Must be enabled using 'display' property. Signed-off-by: Gerd Hoffmann Reviewed By: Kirti Wankhede Signed-off-by: Alex Williamson ---

[Qemu-devel] [PULL 07/11] vfio/display: adding region support

From: Gerd Hoffmann Wire up region-based display. Signed-off-by: Gerd Hoffmann Reviewed By: Kirti Wankhede Signed-off-by: Alex Williamson --- hw/vfio/display.c | 117

[Qemu-devel] [PULL 05/11] vfio/common: cleanup in vfio_region_finalize

From: Gerd Hoffmann Signed-off-by: Gerd Hoffmann Reviewed by: Kirti Wankhede Signed-off-by: Alex Williamson --- hw/vfio/common.c |7 +++ 1 file changed, 7 insertions(+) diff --git

[Qemu-devel] [PULL 09/11] vfio/pci: Relax DMA map errors for MMIO regions

From: Alexey Kardashevskiy At the moment if vfio_memory_listener is registered in the system memory address space, it maps/unmaps every RAM memory region for DMA. It expects system page size aligned memory sections so vfio_dma_map would not fail and so far this has been the case.

[Qemu-devel] [PULL 02/11] ui/pixman: add qemu_drm_format_to_pixman()

From: Gerd Hoffmann Map drm fourcc codes to pixman formats. Signed-off-by: Gerd Hoffmann Reviewed by: Kirti Wankhede Signed-off-by: Alex Williamson --- include/ui/qemu-pixman.h |5 +

[Qemu-devel] [PULL 00/11] vfio updates for QEMU-2.12 soft freeze

The following changes since commit 9f750794985d7386f088da941c76b73880b2b6c4: sev/i386: add sev_get_capabilities() (2018-03-13 17:36:06 +0100) are available in the Git repository at: git://github.com/awilliam/qemu-vfio.git tags/vfio-update-20180313.0 for you to fetch changes up to

[Qemu-devel] [PULL 04/11] secondary-vga: properly close QemuConsole on unplug

From: Gerd Hoffmann Using the new graphic_console_close() function. Signed-off-by: Gerd Hoffmann Signed-off-by: Alex Williamson --- hw/display/vga-pci.c |9 + 1 file changed, 9 insertions(+) diff --git

[Qemu-devel] [PULL 03/11] console: minimal hotplug suport

From: Gerd Hoffmann This patch allows to unbind devices from QemuConsoles, using the new graphic_console_close() function. The QemuConsole will show a static display then, saying the device was unplugged. When re-plugging a display later on the QemuConsole will be reused.

[Qemu-devel] [PULL 01/11] standard-headers: add drm/drm_fourcc.h

From: Gerd Hoffmann So we can use the drm fourcc codes without a dependency on libdrm-devel. Signed-off-by: Gerd Hoffmann Signed-off-by: Alex Williamson --- include/standard-headers/drm/drm_fourcc.h | 411

Re: [Qemu-devel] [PATCH v2 0/8] nbd block status base:allocation

On 03/12/2018 10:11 PM, Eric Blake wrote:    CC  block/nbd-client.o    CC  block/sheepdog.o /var/tmp/patchew-tester-tmp-erqpie2w/src/block/nbd-client.c: In function ‘nbd_client_co_block_status’: /var/tmp/patchew-tester-tmp-erqpie2w/src/block/nbd-client.c:890:15: error:

Re: [Qemu-devel] [PATCH v11 00/13] Dirty bitmaps postcopy migration

* Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote: > It looks like a bug in a recent commit to checkpatch. It don't support do { } > while Yes, adding Su Hang and Eric in and trimming some others out. So yes, ignore this patchew failure for this case, but we need to fix that

[Qemu-devel] regression in timer code?

Hi Pavel, the commit b39e3f34c9de7ead6a11a74aa2de78baf41d81a7 ("icount: fixed saving/restoring of icount warp timers") has changed something that made timers test for target/xtensa unstable. Specifically ccount_write case in the tests/tcg/xtensa/test_timer.S now fails for me about half of the

Re: [Qemu-devel] [PATCH v11 00/13] Dirty bitmaps postcopy migration

On 03/13/2018 03:01 PM, Vladimir Sementsov-Ogievskiy wrote: It looks like a bug in a recent commit to checkpatch. It don't support do { } while Checking PATCH 11/13: migration: add postcopy migration of dirty bitmaps... ERROR: braces {} are necessary for all arms of this statement #737:

[Qemu-devel] [RFC PATCH] i2c: device passthrough HACK(!) & evaluation

I was asked to investigate I2C device passthrough possibilities for QEMU on Linux. The idea was to expose only a single device, not the whole bus. There was no specific use case explained, so some decisions are still to be made. E.g. I think the host-device should get its own virtualized bus

Re: [Qemu-devel] [PATCH v11 00/13] Dirty bitmaps postcopy migration

It looks like a bug in a recent commit to checkpatch. It don't support do { } while Best regards, Vladimir. От: no-re...@patchew.org Отправлено: 13 марта 2018 г. 22:03:29 Кому: Vladimir Sementsov-Ogievskiy Копия: f...@redhat.com;

Re: [Qemu-devel] [PATCH v12 08/28] target/i386: add Secure Encrypted Virtulization (SEV) object

* Eduardo Habkost (ehabk...@redhat.com) wrote: > On Tue, Mar 13, 2018 at 08:04:51PM +0100, Paolo Bonzini wrote: > > On 13/03/2018 19:49, Eduardo Habkost wrote: > > >>> > > >>> Exactly, in other words these two options are part of the guest > > >>> ABI, and QEMU promises to never make the guest ABI

Re: [Qemu-devel] [PATCH v11 11/13] migration: add postcopy migration of dirty bitmaps

On 03/13/2018 02:29 PM, Vladimir Sementsov-Ogievskiy wrote: > 13.03.2018 21:22, Dr. David Alan Gilbert wrote: >> * Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote: >>> Postcopy migration of dirty bitmaps. Only named dirty bitmaps are >>> migrated. >>> >>> If destination qemu is

Re: [Qemu-devel] [PULL v2 0/9] Socket next patches

Hi, This series seems to have some coding style problems. See output below for more information: Type: series Message-id: 20180313181248.16215-1-berra...@redhat.com Subject: [Qemu-devel] [PULL v2 0/9] Socket next patches === TEST SCRIPT BEGIN === #!/bin/bash BASE=base n=1 total=$(git log

Re: [Qemu-devel] [PULL 00/17] NBD patches for 2018-03-13 (2.12 softfreeze)

On 03/13/2018 01:17 PM, no-re...@patchew.org wrote: Hi, This series failed build test on s390x host. Please find the details below. Type: series Message-id: 20180313171345.659672-1-ebl...@redhat.com Subject: [Qemu-devel] [PULL 00/17] NBD patches for 2018-03-13 (2.12 softfreeze) CC

Re: [Qemu-devel] [PATCH v12 08/28] target/i386: add Secure Encrypted Virtulization (SEV) object

On Tue, Mar 13, 2018 at 08:04:51PM +0100, Paolo Bonzini wrote: > On 13/03/2018 19:49, Eduardo Habkost wrote: > >>> > >>> Exactly, in other words these two options are part of the guest > >>> ABI, and QEMU promises to never make the guest ABI depend on the > >>> host hardware unless you're using

Re: [Qemu-devel] [PATCH qemu v7 2/4] vfio/pci: Relax DMA map errors for MMIO regions

[Making a meta-comment that I've pointed out to others before] On 03/13/2018 12:13 PM, Auger Eric wrote: Hi Alex, ... On Fri, Feb 09, 2018 at 06:55:01PM +1100, Alexey Kardashevskiy wrote: At the moment if vfio_memory_listener is registered in the system memory 17 levels of '>' before I

Re: [Qemu-devel] [PULL 2/9] cutils: add qemu_strtoi & qemu_strtoui parsers for int/unsigned int types

On 12.03.2018 21:12, Daniel P. Berrangé wrote: > From: "Daniel P. Berrange" > > There are qemu_strtoNN functions for various sized integers. This adds two > more for plain int & unsigned int types, with suitable range checking. > There is a prior art in NetBSD with

Re: [Qemu-devel] [PATCH v12 08/28] target/i386: add Secure Encrypted Virtulization (SEV) object

On 13/03/2018 19:49, Eduardo Habkost wrote: >>> >>> Exactly, in other words these two options are part of the guest >>> ABI, and QEMU promises to never make the guest ABI depend on the >>> host hardware unless you're using "-cpu host". >> >> This is not entirely true; while MAXPHYADDR is constant

[Qemu-devel] [PULL 00/11] target/xtensa linux-user support

026aaf47c02b79036feb830206cfebb2a726510d: Merge remote-tracking branch 'remotes/ehabkost/tags/python-next-pull-request' into staging (2018-03-13 16:26:44 +) are available in the git repository at: git://github.com/OSLL/qemu-xtensa.git tags/20180313-xtensa for you to fetch changes up

Re: [Qemu-devel] [PATCH 1/2] qcow2: Give the refcount cache the minimum possible size by default

On 03/13/2018 01:48 PM, Alberto Garcia wrote: On Tue 13 Mar 2018 07:23:36 PM CET, Eric Blake wrote: +*refcount_cache_size = +MIN(combined_cache_size, min_refcount_cache); but here, if combined_cache_size is smaller than min_refcount_cache, +

Re: [Qemu-devel] [PULL 00/17] NBD patches for 2018-03-13 (2.12 softfreeze)

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: 20180313171345.659672-1-ebl...@redhat.com Subject: [Qemu-devel] [PULL 00/17] NBD patches

[Qemu-devel] [PULL v2 9/9] char: allow passing pre-opened socket file descriptor at startup

From: "Daniel P. Berrange" When starting QEMU management apps will usually setup a monitor socket, and then open it immediately after startup. If not using QEMU's own -daemonize arg, this process can be troublesome to handle correctly. The mgmt app will need to repeatedly

[Qemu-devel] [PULL v2 7/9] sockets: allow SocketAddress 'fd' to reference numeric file descriptors

From: "Daniel P. Berrange" The SocketAddress 'fd' kind accepts the name of a file descriptor passed to the monitor with the 'getfd' command. This makes it impossible to use the 'fd' kind in cases where a monitor is not available. This can apply in handling command line argv

Re: [Qemu-devel] [PATCH v11 00/13] Dirty bitmaps postcopy migration

Hi, This series seems to have some coding style problems. See output below for more information: Type: series Message-id: 20180313180320.339796-1-vsement...@virtuozzo.com Subject: [Qemu-devel] [PATCH v11 00/13] Dirty bitmaps postcopy migration === TEST SCRIPT BEGIN === #!/bin/bash BASE=base

[Qemu-devel] [PULL v2 5/9] sockets: move fd_is_socket() into common sockets code

From: "Daniel P. Berrange" The fd_is_socket() helper method is useful in a few places, so put it in the common sockets code. Make the code more compact while moving it. Reviewed-by: Eric Blake Reviewed-by: Marc-André Lureau

Re: [Qemu-devel] [PATCH 1/2] qcow2: Give the refcount cache the minimum possible size by default

On Tue 13 Mar 2018 07:23:36 PM CET, Eric Blake wrote: >> +*refcount_cache_size = >> +MIN(combined_cache_size, min_refcount_cache); > > but here, if combined_cache_size is smaller than min_refcount_cache, > >> +*l2_cache_size = combined_cache_size

[Qemu-devel] [PULL v2 2/9] cutils: add qemu_strtoi & qemu_strtoui parsers for int/unsigned int types

From: "Daniel P. Berrange" There are qemu_strtoNN functions for various sized integers. This adds two more for plain int & unsigned int types, with suitable range checking. Reviewed-by: Eric Blake Reviewed-by: Marc-André Lureau

Re: [Qemu-devel] [PULL 0/7] Machine queue, 2018-03-12

On 12 March 2018 at 22:34, Eduardo Habkost wrote: > The following changes since commit 6ceb1b51f05f9e1892d082960ed602dca7b6696e: > > Merge remote-tracking branch > 'remotes/kraxel/tags/audio-20180312-pull-request' into staging (2018-03-12 > 16:14:37 +) > > are

[Qemu-devel] [PULL v2 0/9] Socket next patches

The following changes since commit 59667bb167f773965ce6547352f312eff0d4d523: Merge remote-tracking branch 'remotes/ehabkost/tags/x86-next-pull-request' into staging (2018-03-13 14:02:47 +) are available in the Git repository at: https://github.com/berrange/qemu

[Qemu-devel] [Bug 1755479] Re: Cortex M:qemu abort with optimized code and icount

I just tested the patch and it resolves this problem. Thanks! -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1755479 Title: Cortex M:qemu abort with optimized code and icount Status in QEMU: New

Re: [Qemu-devel] [PATCH v11 10/13] migration: allow qmp command migrate-start-postcopy for any postcopy

* Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote: > Allow migrate-start-postcopy for any postcopy type > > Signed-off-by: Vladimir Sementsov-Ogievskiy Reviewed-by: Dr. David Alan Gilbert > --- > migration/migration.c | 2 +- > 1

Re: [Qemu-devel] [PULL 2/9] cutils: add qemu_strtoi & qemu_strtoui parsers for int/unsigned int types

On Mon, Mar 12, 2018 at 08:12:58PM +, Daniel P. Berrangé wrote: > From: "Daniel P. Berrange" > > There are qemu_strtoNN functions for various sized integers. This adds two > more for plain int & unsigned int types, with suitable range checking. > > Reviewed-by: Eric

[Qemu-devel] [PATCH v11 06/13] qapi: add dirty-bitmaps migration capability

Signed-off-by: Vladimir Sementsov-Ogievskiy Reviewed-by: John Snow Reviewed-by: Eric Blake Reviewed-by: Juan Quintela Reviewed-by: Fam Zheng --- qapi/migration.json | 6 +-

<    1   2   3   4   5   6   >