[Qemu-devel] [PATCH v11 05/13] 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/register.h | 17 +++-- migration/savevm.h | 5

[Qemu-devel] [PULL 00/18] Linux user for 2.12 patches

The following changes since commit b39b61e410022f96ceb53d4381d25cba5126ac44: memory: fix flatview_access_valid RCU read lock/unlock imbalance (2018-03-09 15:55:20 +) are available in the Git repository at: git://github.com/vivier/qemu.git tags/linux-user-for-2.12-pull-request for you

[Qemu-devel] [PATCH v11 09/13] 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 Reviewed-by: Juan Quintela Reviewed-by: John

[Qemu-devel] [PULL 11/18] linux-user: Rename validate_guest_space => init_guest_commpage

From: Luke Shumaker init_guest_commpage is a much more honest description of what the function does. validate_guest_space not only suggests that the function has no side-effects, but also introduces confusion as to why it is only needed on 32-bit ARM targets.

[Qemu-devel] [PULL 03/18] linux-user: allows to use "--systemd ALL" with qemu-binfmt-conf.sh

qemu-binfmt-conf.sh when it is used with systemd needs to know for which CPU the systemd-binfmt.service file must be created (i.e. "--systemd ppc"). But sometime, for instance for test purpose, we need to create an entry for all known architectures. This patch entroduce the "ALL" parameter for

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

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 same the migration will be done, otherwise the error will be

[Qemu-devel] [PULL v2 1/9] char: don't silently skip tn3270 protocol init when TLS is enabled

From: "Daniel P. Berrange" Even if common tn3270 implementations do not support TLS, it is trivial to have them proxied over a proxy like stunnel which adds TLS at the sockets layer. We should thus not silently skip tn3270 protocol initialization when TLS is enabled.

[Qemu-devel] [PULL 07/18] linux-user: fix target_mprotect/target_munmap error return values

From: Max Filippov target_mprotect/target_munmap return value goes through get_errno at the call site, thus the functions must either set errno to host error code and return -1 or return negative guest error code. Do the latter. Cc: qemu-sta...@nongnu.org Cc: Riku Voipio

Re: [Qemu-devel] [PATCH v11 05/13] migration: introduce postcopy-only pending

* Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote: > 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.

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

* Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote: > 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

[Qemu-devel] [PULL 13/18] linux-user: init_guest_space: Correctly handle guest_start in commpage initialization

From: Luke Shumaker init_guest_commpage needs to check if the mapped space, which ends at real_start+real_size overlaps with where it needs to put the commpage, which is (assuming sane qemu_host_page_size) guest_base + 0x000, where guest_base is real_start -

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

On Tue, Mar 13, 2018 at 06:29:10PM +, Peter Maydell wrote: > On 12 March 2018 at 22:34, Eduardo Habkost wrote: > > The following changes since commit 6ceb1b51f05f9e1892d082960ed602dca7b6696e: > > > > Merge remote-tracking branch > >

[Qemu-devel] [PULL v2 4/9] sockets: strengthen test suite IP protocol availability checks

From: "Daniel P. Berrange" Instead of just checking whether it is possible to bind() on a socket, also check that we can successfully connect() to the socket we bound to. This more closely replicates the level of functionality that tests will actually use. Reviewed-by: Eric

[Qemu-devel] [PULL v2 6/9] sockets: check that the named file descriptor is a socket

From: "Daniel P. Berrange" The SocketAddress struct has an "fd" type, which references the name of a file descriptor passed over the monitor using the "getfd" command. We currently blindly assume the FD is a socket, which can lead to hard to diagnose errors later. This adds

[Qemu-devel] [PULL v2 8/9] char: refactor parsing of socket address information

From: "Daniel P. Berrange" To prepare for handling more address types, refactor the parsing of socket address information to make it more robust and extensible. Reviewed-by: Eric Blake Reviewed-by: Marc-André Lureau

[Qemu-devel] [PATCH v11 08/13] 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. Signed-off-by: Vladimir Sementsov-Ogievskiy Reviewed-by:

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

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 Reviewed-by: John Snow

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

On Tue, Mar 13, 2018 at 09:42:51AM +0100, Paolo Bonzini wrote: > On 08/03/2018 23:44, Eduardo Habkost wrote: > >> I think doing so will be an issue for the migration. Consider your above > >> use case, a SEV guest is running on EPYC with cbitpos=47 and if we > >> migrate to some $NEXT AMD CPU

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

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

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

Re: [Qemu-devel] [PULL 00/41] Block layer patches

Hi, This series seems to have some coding style problems. See output below for more information: Type: series Message-id: 20180313161803.1814-1-kw...@redhat.com Subject: [Qemu-devel] [PULL 00/41] Block layer patches === TEST SCRIPT BEGIN === #!/bin/bash BASE=base n=1 total=$(git log --oneline

[Qemu-devel] [PULL 02/18] linux-user: Remove the unused "not implemented" signal handling stubs

From: Peter Maydell Now we've dropped unicore32, all of the architectures we support for linux-user implement the signal handling routines. The dummy "just print a message" versions are unimplemented, so we can drop them entirely. Signed-off-by: Peter Maydell

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

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 Zheng --- migration/migration.c | 2 +- 1

[Qemu-devel] [PATCH v11 12/13] 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. Signed-off-by: Vladimir Sementsov-Ogievskiy --- tests/qemu-iotests/169 | 156

[Qemu-devel] [PULL 14/18] linux-user: init_guest_space: Clarify page alignment logic

From: Luke Shumaker There are 3 parts to this change: - Add a comment showing the relative sizes and positions of the blocks of memory - introduce and use new aligned_{start,size} instead of adjusting real_{start_size} - When we clean up (on failure),

[Qemu-devel] [PULL 17/18] linux-user: init_guest_space: Don't try to align if we'll reject it

From: Luke Shumaker If the ensure-alignment code gets triggered, then the "if (host_start && real_start != current_start)" check will always trigger, so save 2 syscalls and put that check first. Note that we can't just switch to using MAP_FIXED for that check, because then

Re: [Qemu-devel] [PULL 0/4] Python queue, 2018-03-12

On 12 March 2018 at 22:11, 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 16/18] linux-user: init_guest_space: Clean up control flow a bit

From: Luke Shumaker Instead of doing if (check1) { if (check2) { success; } } retry; Do a clearer if (!check1) { goto try_again; } if (!check2) { goto try_again;

[Qemu-devel] [PULL 18/18] linux-user: init_guest_space: Add a comment about search strategy

From: Luke Shumaker Signed-off-by: Luke Shumaker Message-Id: <20171228180814.9749-10-luke...@lukeshu.com> Reviewed-by: Peter Maydell Signed-off-by: Laurent Vivier --- linux-user/elfload.c | 4 1 file

[Qemu-devel] [PULL v2 3/9] sockets: pull code for testing IP availability out of specific test

From: "Daniel P. Berrange" The test-io-channel-socket.c file has some useful helper functions for checking if a specific IP protocol is available. Other tests need to perform similar kinds of checks to avoid running tests that will fail due to missing IP protocols.

Re: [Qemu-devel] [PATCH 2/2] docs: Document the new default sizes of the qcow2 caches

On 03/13/2018 10:02 AM, Alberto Garcia wrote: We have just reduced the refcount cache size to the minimum unless the user explicitly requests a larger one, so we have to update the documentation to reflect this change. Signed-off-by: Alberto Garcia --- docs/qcow2-cache.txt

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

Signed-off-by: Vladimir Sementsov-Ogievskiy Reviewed-by: John Snow Message-id: 20180207155837.92351-4-vsement...@virtuozzo.com Signed-off-by: John Snow --- include/block/dirty-bitmap.h | 3 +++ block/dirty-bitmap.c | 28

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

Yes, it looks like we accidentally broke icount. This patch from the mailing list fixes it: https://lists.gnu.org/archive/html/qemu-devel/2018-02/msg06595.html though it hasn't been code-reviewed yet. -- You received this bug notification because you are a member of qemu- devel-ml, which is

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

On 13 March 2018 at 18:23, Daniel P. Berrangé wrote: > On Tue, Mar 13, 2018 at 04:27:08PM +, Daniel P. Berrangé wrote: >> This feels unrelated to the series, so possibly a non-deterministic >> failure > > Looking at the test source code, it has a 60 second wait for the >

Re: [Qemu-devel] [PULL 18/41] blockjobs: add block-job-finalize

On 03/13/2018 11:17 AM, Kevin Wolf wrote: From: John Snow Instead of automatically transitioning from PENDING to CONCLUDED, gate the .prepare() and .commit() phases behind an explicit acknowledgement provided by the QMP monitor if auto_finalize = false has been requested.

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

Allow migrate-start-postcopy for any postcopy type 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 094196c236..59b4fe6090

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

On 03/13/2018 10:02 AM, Alberto Garcia wrote: The L2 and refcount caches have default sizes that can be overriden using the l2-cache-size and refcount-cache-size (an additional parameter named cache-size sets the combined size of both caches). Unless forced by one of the aforementioned

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

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 already containing a dirty bitmap with the same name as a migrated bitmap (for the

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

On Tue, Mar 13, 2018 at 04:27:08PM +, Daniel P. Berrangé wrote: > On Tue, Mar 13, 2018 at 04:20:19PM +, Peter Maydell wrote: > > On 12 March 2018 at 20:12, Daniel P. Berrangé wrote: > > > The following changes since commit > > >

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

[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

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

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

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

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;

[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

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

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

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

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] [PATCH 8/8] migration: remove ram_save_compressed_page()

From: Xiao Guangrong Now, we can reuse the path in ram_save_page() to post the page out as normal, then the only thing remained in ram_save_compressed_page() is compression that we can move it out to the caller Signed-off-by: Xiao Guangrong

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

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: 20180312152126.286890-1-vsement...@virtuozzo.com Subject: [Qemu-devel] [PATCH v2 0/8] nbd

Re: [Qemu-devel] [PATCH qemu v2] slirp/debug: Print IP addresses in human readable form

Hi, This series seems to have some coding style problems. See output below for more information: Type: series Message-id: 20180313044944.21058-1-...@ozlabs.ru Subject: [Qemu-devel] [PATCH qemu v2] slirp/debug: Print IP addresses in human readable form === TEST SCRIPT BEGIN === #!/bin/bash

Re: [Qemu-devel] [PATCH qemu v2] slirp/debug: Print IP addresses in human readable form

Alexey Kardashevskiy, on mar. 13 mars 2018 15:49:44 +1100, wrote: > Signed-off-by: Alexey Kardashevskiy Applied to my tree, thanks! > --- > > checkpatch.pl complains on every single changed line as it keeps > using tabs - do I need to post 's/\t//g'? > > --- > Changes: >

[Qemu-devel] [PATCH 6/8] migration: move calling save_zero_page to the common place

From: Xiao Guangrong save_zero_page() is always our first approach to try, move it to the common place before calling ram_save_compressed_page and ram_save_page Signed-off-by: Xiao Guangrong --- migration/ram.c | 106

Re: [Qemu-devel] [PATCH V3 0/4] vfio: Introduce Live migration capability to vfio_mdev device

> -Original Message- > From: Alex Williamson [mailto:alex.william...@redhat.com] > Sent: Tuesday, March 13, 2018 6:22 AM > To: Zhang, Yulei > Cc: qemu-devel@nongnu.org; Tian, Kevin ; > zhen...@linux.intel.com; kwankh...@nvidia.com; Juan

[Qemu-devel] [PATCH 5/8] migration: move calling control_save_page to the common place

From: Xiao Guangrong The function is called by both ram_save_page and ram_save_target_page, so move it to the common caller to cleanup the code Signed-off-by: Xiao Guangrong --- migration/ram.c | 16 1 file changed, 8

[Qemu-devel] [PATCH 7/8] migration: introduce save_normal_page()

From: Xiao Guangrong It directly sends the page to the stream neither checking zero nor using xbzrle or compression Signed-off-by: Xiao Guangrong --- migration/ram.c | 50 ++ 1 file changed,

Re: [Qemu-devel] [PATCH v2 resend] block/mirror: change the semantic of 'force' of block-job-cancel

On 03/12/2018 10:13 PM, Jeff Cody wrote: > On Fri, Mar 02, 2018 at 11:20:55AM -0500, John Snow wrote: >> >> >> On 03/02/2018 10:39 AM, Eric Blake wrote: >>> On 02/26/2018 08:05 PM, Liang Li wrote: When doing drive mirror to a low speed shared storage, if there was heavy BLK IO write

Re: [Qemu-devel] [PATCH v10 05/12] migration: introduce postcopy-only pending

12.03.2018 18:30, Dr. David Alan Gilbert wrote: * Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote: 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

[Qemu-devel] [PATCH 4/8] migration: introduce control_save_page()

From: Xiao Guangrong Abstract the common function control_save_page() to cleanup the code, no logic is changed Signed-off-by: Xiao Guangrong --- migration/ram.c | 174 +--- 1 file

[Qemu-devel] [PATCH 0/8] migration: improve and cleanup compression

From: Xiao Guangrong This is the first part of our work to improve compression to make it be more useful in the production. The first patch resolves the problem that the migration thread spends too much CPU resource to compression memory if it jumps to a new block

[Qemu-devel] [PATCH 1/8] migration: stop compressing page in migration thread

From: Xiao Guangrong As compression is a heavy work, do not do it in migration thread, instead, we post it out as a normal page Signed-off-by: Xiao Guangrong --- migration/ram.c | 32 1 file changed, 16

[Qemu-devel] [PATCH 2/8] migration: stop allocating and freeing memory frequently

From: Xiao Guangrong Current code uses compress2()/uncompress() to compress/decompress memory, these two function manager memory allocation and release internally, that causes huge memory is allocated and freed very frequently More worse, frequently returning memory

[Qemu-devel] [PATCH 3/8] migration: support to detect compression and decompression errors

From: Xiao Guangrong Currently the page being compressed is allowed to be updated by the VM on the source QEMU, correspondingly the destination QEMU just ignores the decompression error. However, we completely miss the chance to catch real errors, then the VM is

Re: [Qemu-devel] [PATCH] KVM: x86: Add support for save/load MSR_SMI_COUNT

On 13/03/2018 01:22, Liran Alon wrote: > > Another gentle ping. > > (Just following "If your patch seems to have been ignored" section in QEMU's > submitting patches guidelines...) > > - liran.a...@oracle.com wrote: > >> Gentle ping. >>

Re: [Qemu-devel] [PATCH] iotests: Fix stuck NBD process on 33

On 13/3/2018 12:12 AM, Max Reitz wrote: On 2018-03-12 22:11, Eric Blake wrote: Commit afe35cde6 added additional actions to test 33, but forgot to reset the image between tests. As a result, './check -nbd 33' fails because the qemu-nbd process from the first half is still occupying the port,

Re: [Qemu-devel] [PATCH v4 0/8] nvdimm: guarantee persistence of QEMU writes to persistent memory

On Tue, Mar 13, 2018 at 08:11:50AM +0800, Haozhong Zhang wrote: > On 03/12/18 15:39 +, Stefan Hajnoczi wrote: > > On Wed, Feb 28, 2018 at 03:25:50PM +0800, Haozhong Zhang wrote: > > > QEMU writes to vNVDIMM backends in the vNVDIMM label emulation and > > > live migration. If the backend is on

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

On 13.03.2018 11:37, Stefan Hajnoczi wrote: > On Mon, Mar 12, 2018 at 02:46:20PM +0100, Thomas Huth wrote: >> On 12.03.2018 14:18, Stefan Hajnoczi wrote: >>> Warn if files are added/renamed/deleted without MAINTAINERS file >>> changes. This has helped me in Linux and we could benefit from this

[Qemu-devel] [PATCH v2 1/2] block: Fix flags in reopen queue

Reopen flags are not synchronized according to the bdrv_reopen_queue_child precedence until bdrv_reopen_prepare. It is a bit too late: we already check the consistency in bdrv_check_perm before that. This fixes the bug that when bdrv_reopen a RO node as RW, the flags for backing child are wrong.

Re: [Qemu-devel] [PATCH v7 17/23] migration: setup ramstate for resume

On Mon, Mar 12, 2018 at 05:30:12PM +, Dr. David Alan Gilbert wrote: > * Peter Xu (pet...@redhat.com) wrote: > > After we updated the dirty bitmaps of ramblocks, we also need to update > > the critical fields in RAMState to make sure it is ready for a resume. > > > > Signed-off-by: Peter Xu

Re: [Qemu-devel] [PATCH v12 24/28] sev/i386: add migration blocker

On 08/03/2018 13:48, Brijesh Singh wrote: > sev_set_guest_state(SEV_STATE_RUNNING); > + > +/* add migration blocker */ > +error_setg(_mig_blocker, > + "SEV: Migration is not implemented"); > +ret = migrate_add_blocker(sev_mig_blocker, _err); > +if (local_err) { >

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

On Mon, Mar 12, 2018 at 02:46:20PM +0100, Thomas Huth wrote: > On 12.03.2018 14:18, Stefan Hajnoczi wrote: > > Warn if files are added/renamed/deleted without MAINTAINERS file > > changes. This has helped me in Linux and we could benefit from this > > check in QEMU. > > > > This patch is a

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

Hi Wolfram, On 03/12/2018 10:42 PM, Wolfram Sang wrote: > 0 as "rom-size" doesn't make much sense, let's use the smallest 24cXX > which has 128 byte. > > Signed-off-by: Wolfram Sang > --- > hw/nvram/eeprom_at24c.c | 2 +- > 1 file changed, 1 insertion(+), 1

Re: [Qemu-devel] [PATCH 2/3] nvram: at24c: prevent segfault by checking "rom-size"

On 03/12/2018 10:42 PM, Wolfram Sang wrote: > The value for "rom-size" is used as a divisor, so it must not be 0 or it > will segfault. A size of 0 wouldn't make sense as well. > > Signed-off-by: Wolfram Sang > --- > hw/nvram/eeprom_at24c.c | 5 + > 1 file

Re: [Qemu-devel] [RFC PATCH 00/30] Xen Q35 Bringup patches + support for PCIe Extended Capabilities for passed through devices

On Tue, Mar 13, 2018 at 09:37:55PM +1000, Alexey G wrote: > On Tue, 13 Mar 2018 09:21:54 + > Daniel P. Berrangé wrote: > > >The subject line says to expect 30 patches, but you've only sent 18 to > >the list here. I eventually figured out that the first 12 patches were >

Re: [Qemu-devel] [PATCH] update Linux headers to 4.15

On 13 March 2018 at 11:45, Christian Borntraeger wrote: > > > On 03/13/2018 11:39 AM, Paolo Bonzini wrote: >> Signed-off-by: Paolo Bonzini >> --- >> include/standard-headers/linux/input-event-codes.h | 1 + >>

[Qemu-devel] [PATCH v2 0/2] block: Fix permission during reopen

v2: Use update_flags_from_options. [Kevin] We write open the whole backing chain during reopen. It is not necessary and will cause image locking problems if the backing image is shared. Fam Zheng (2): block: Fix flags in reopen queue iotests: Add regression test for commit base locking

[Qemu-devel] [PATCH v2 2/2] iotests: Add regression test for commit base locking

Signed-off-by: Fam Zheng --- tests/qemu-iotests/153 | 8 tests/qemu-iotests/153.out | 4 2 files changed, 12 insertions(+) diff --git a/tests/qemu-iotests/153 b/tests/qemu-iotests/153 index adfd02695b..a7875e6899 100755 --- a/tests/qemu-iotests/153 +++

Re: [Qemu-devel] [PATCH] update Linux headers to 4.15

On 13/03/2018 12:57, Peter Maydell wrote: > On 13 March 2018 at 11:45, Christian Borntraeger > wrote: >> >> >> On 03/13/2018 11:39 AM, Paolo Bonzini wrote: >>> Signed-off-by: Paolo Bonzini >>> --- >>>

Re: [Qemu-devel] [PATCH V3 1/4] vfio: introduce a new VFIO subregion for mdev device migration support

> -Original Message- > From: Dr. David Alan Gilbert [mailto:dgilb...@redhat.com] > Sent: Friday, March 9, 2018 7:43 PM > To: Zhang, Yulei > Cc: qemu-devel@nongnu.org; Tian, Kevin ; > alex.william...@redhat.com; kwankh...@nvidia.com; >

  1   2   3   4   5   6   >