[Qemu-devel] [PATCH v2 0/3] audio: -audiodev documentation tweaks

2019-09-18 Thread Stefan Hajnoczi
v2: * Added ALSA period-length fix [Zoltán] * Expanded PulseAudio latency documentation [Zoltán] Small fixes to the -audiodev documentation. Stefan Hajnoczi (3): audio: fix buffer-length typo in documentation audio: add -audiodev pa,in|out.latency= to documentation audio: fix ALSA period-

[Qemu-devel] [PATCH v2 0/3] cputlb: Adjust tlb bswap implementation

2019-09-12 Thread Richard Henderson
Changes from v1: * Move QEMU_ALWAYS_INLINE to qemu/compiler.h. * Rename some inline wrapper functions. * Don't break TLB_NOTDIRTY in patch 3. Blurb from v1: The version that Tony came up with, and I reviewed, doesn't actually work when applied to RAM. It only worked for i/o memory. This w

[Qemu-devel] [PATCH v2 0/3] xen: fix a potential crash in xen-bus

2019-09-12 Thread Paul Durrant
This series fixes a potential segfault caused by NotifierList corruption in xen-bus. The first two patches lay the groundwork and the third actually fixes the problem. Paul Durrant (3): xen / notify: introduce a new XenWatchList abstraction xen: introduce separate XenWatchList for XenDevice ob

Re: [Qemu-devel] [PATCH v2 0/3] UUID validation during migration

2019-09-12 Thread Dr. David Alan Gilbert
* Yury Kotov (yury-ko...@yandex-team.ru) wrote: > Hi, > V2: > * Remove x- prefix from capability name > * Fix expected status checking > * Fix description of capability > > This series adds an UUID validation at the start of the migration > on the target side. The idea is to identify the source o

[Qemu-devel] [PATCH v2 0/3] proper locking on bitmap add/remove paths

2019-09-11 Thread Vladimir Sementsov-Ogievskiy
We need to lock qcow2 mutex on accessing in-image metadata, especially on updating this metadata. Let's implement it. v2: fix uninitialized variable in 03, found by Patchew Vladimir Sementsov-Ogievskiy (3): block: move bdrv_can_store_new_dirty_bitmap to block/dirty-bitmap.c block/dirty-bitma

[Qemu-devel] [PATCH v2 0/3] some fix in tests/migration

2019-09-10 Thread Mao Zhongyi
This patchset mainly fixes memory leak, typo and return value of stress function in stress test. v2->v1: - use g_autofree to release memory automatically instead of free(). [Alex Bennée] Cc: arm...@redhat.com Cc: laur...@vivier.eu Cc: tony.ngu...@bt.c

Re: [Qemu-devel] [PATCH v2 0/3] tests/tcg: disentangle makefiles

2019-09-09 Thread Paolo Bonzini
On 04/09/19 16:27, Alex Bennée wrote: >> Ping? > > Sorry I should have said I've queued it to testing/next. I'll post the > series shortly after I've squashed the last annoying python 3.<>6 > problem. Great, thanks. Paolo

[Qemu-devel] [PATCH v2 0/3] Fix qcow2+luks corruption introduced by commit 8ac0f15f335

2019-09-06 Thread Maxim Levitsky
Commit 8ac0f15f335 accidently broke the COW of non changed areas of newly allocated clusters, when the write spans multiple clusters, and needs COW both prior and after the write. This results in 'after' COW area being encrypted with wrong sector address, which render it corrupted. Bugzilla: https

Re: [Qemu-devel] [PATCH v2 0/3] tests/tcg: disentangle makefiles

2019-09-04 Thread Alex Bennée
Paolo Bonzini writes: > Ping? Sorry I should have said I've queued it to testing/next. I'll post the series shortly after I've squashed the last annoying python 3.<>6 problem. > > Paolo > > > Il mer 7 ago 2019, 16:35 Paolo Bonzini ha scritto: > >> The tests/tcg rely a lot on per-target infor

Re: [Qemu-devel] [PATCH v2 0/3] tests/tcg: disentangle makefiles

2019-09-04 Thread Paolo Bonzini
Ping? Paolo Il mer 7 ago 2019, 16:35 Paolo Bonzini ha scritto: > The tests/tcg rely a lot on per-target informations from > the QEMU makefiles, but most of the definitions in there > aren't really relevant to TCG tests. > > This series is just a cleanup, but it could also be > a useful start i

[Qemu-devel] [PATCH v2 0/3] UUID validation during migration

2019-09-03 Thread Yury Kotov
Hi, V2: * Remove x- prefix from capability name * Fix expected status checking * Fix description of capability This series adds an UUID validation at the start of the migration on the target side. The idea is to identify the source of migration. Possible case of problem: 1. There are 3 servers:

Re: [Qemu-devel] [PATCH v2 0/3] colo: Add support for continious replication

2019-08-21 Thread Dr. David Alan Gilbert
; > To: Dr. David Alan Gilbert > > > Cc: qemu-devel ; Zhang, Chen > > > ; Jason Wang ; Xie > > > Changlong ; Wen Congyang > > > > > > Subject: Re: [Qemu-devel] [PATCH v2 0/3] colo: Add support for continious > > > replication > > > &

Re: [Qemu-devel] [PATCH v2 0/3] colo: Add support for continious replication

2019-08-20 Thread Zhang, Chen
> -Original Message- > From: Lukas Straub [mailto:lukasstra...@web.de] > Sent: Saturday, August 17, 2019 2:20 AM > To: Zhang, Chen > Cc: Dr. David Alan Gilbert ; qemu-devel de...@nongnu.org>; Jason Wang ; Xie Changlong > ; Wen Congyang > Subject: Re: [Qemu-de

[Qemu-devel] [PATCH v2 0/3] decodetree improvements

2019-08-17 Thread Richard Henderson
Changes from v1: * Drop unintended hunk from MultiField constructor. * Typo fixed in ParameterField documentation. Blurb from v1: These are split out from my decodetree coversion of the AArch32 base instruction sets. The first patch has been tidied per review from Peter. I now diagno

Re: [Qemu-devel] [PATCH v2 0/3] colo: Add support for continious replication

2019-08-16 Thread Lukas Straub
t; > ; Jason Wang ; Xie > > Changlong ; Wen Congyang > > > > Subject: Re: [Qemu-devel] [PATCH v2 0/3] colo: Add support for continious > > replication > > > > On Thu, 15 Aug 2019 19:57:37 +0100 > > "Dr. David Alan Gilbert" wrote: > > > &g

Re: [Qemu-devel] [PATCH v2 0/3] colo: Add support for continious replication

2019-08-15 Thread Zhang, Chen
> -Original Message- > From: Lukas Straub [mailto:lukasstra...@web.de] > Sent: Friday, August 16, 2019 3:48 AM > To: Dr. David Alan Gilbert > Cc: qemu-devel ; Zhang, Chen > ; Jason Wang ; Xie > Changlong ; Wen Congyang > > Subject: Re: [Qemu-devel] [PATCH v2

Re: [Qemu-devel] [PATCH v2 0/3] colo: Add support for continious replication

2019-08-15 Thread Lukas Straub
On Thu, 15 Aug 2019 19:57:37 +0100 "Dr. David Alan Gilbert" wrote: > * Lukas Straub (lukasstra...@web.de) wrote: > > Hello Everyone, > > These Patches add support for continious replication to colo. > > Please review. > > > OK, for those who haven't followed COLO for so long; 'continuous > replic

Re: [Qemu-devel] [PATCH v2 0/3] colo: Add support for continious replication

2019-08-15 Thread Dr. David Alan Gilbert
* Lukas Straub (lukasstra...@web.de) wrote: > Hello Everyone, > These Patches add support for continious replication to colo. > Please review. OK, for those who haven't followed COLO for so long; 'continuous replication' is when after the first primary fails, you can promote the original seconda

[Qemu-devel] [PATCH v2 0/3] colo: Add support for continious replication

2019-08-15 Thread Lukas Straub
Hello Everyone, These Patches add support for continious replication to colo. Please review. Regards, Lukas Straub v2: - fix email formating - fix checkpatch.pl warnings - fix patchew error - clearer commit messages Lukas Straub (3): Replication: Ignore requests after failover net/filter

[Qemu-devel] [PATCH v2 0/3] colo: Add support for continious replication

2019-08-15 Thread Lukas Straub
Hello Everyone, These Patches add support for continious replication to colo. Please review. Regards, Lukas Straub v2: - fix email formating - fix checkpatch.pl warnings - fix patchew error - clearer commit messages Lukas Straub (3): Replication: Ignore requests after failover net/filter

Re: [Qemu-devel] [PATCH v2 0/3] Fix MemoryRegionSection alignment and comparison

2019-08-14 Thread no-reply
Patchew URL: https://patchew.org/QEMU/20190814175535.2023-1-dgilb...@redhat.com/ Hi, This series failed build test on s390x host. Please find the details below. === TEST SCRIPT BEGIN === #!/bin/bash # Testing script will be invoked under the git checkout with # HEAD pointing to a commit that h

[Qemu-devel] [PATCH v2 0/3] Fix MemoryRegionSection alignment and comparison

2019-08-14 Thread Dr. David Alan Gilbert (git)
From: "Dr. David Alan Gilbert" This fixes a symptom I've seen on vhost-user on aarch64 where the daemon would be falsely notified of memory region changes that didn't exist. The underlying problem was me memcmp'ing MemoryRegionSections even though they had padding in. (Discovered while getting v

Re: [Qemu-devel] [PATCH v2 0/3] migration: add speed limit for multifd migration

2019-08-07 Thread Dr. David Alan Gilbert
* Ivan Ren (reny...@gmail.com) wrote: > From: Ivan Ren > > Currently multifd migration has not been limited and it will consume > the whole bandwidth of Nic. These two patches add speed limitation to > it. Queued > > This is the v3 patches: > > v3 VS v2: > Add Reviewed info and Suggested info

Re: [Qemu-devel] [PATCH v2 0/3] block-backend: Queue requests while drained

2019-08-07 Thread no-reply
Patchew URL: https://patchew.org/QEMU/20190807144628.4988-1-kw...@redhat.com/ Hi, This series seems to have some coding style problems. See output below for more information: Type: series Subject: [Qemu-devel] [PATCH v2 0/3] block-backend: Queue requests while drained Message-id

Re: [Qemu-devel] [PATCH v2 0/3] tests/tcg: disentangle makefiles

2019-08-07 Thread no-reply
Patchew URL: https://patchew.org/QEMU/20190807143523.15917-1-pbonz...@redhat.com/ Hi, This series seems to have some coding style problems. See output below for more information: Type: series Subject: [Qemu-devel] [PATCH v2 0/3] tests/tcg: disentangle makefiles Message-id

[Qemu-devel] [PATCH v2 0/3] block-backend: Queue requests while drained

2019-08-07 Thread Kevin Wolf
This series fixes the problem that devices like IDE, which submit requests as a direct result of I/O from the CPU thread, can continue to submit new requests even in a drained section. v2: - Rebased on top of block-next - Replaced patch 2 with draining mirror_top_bs instead [Max] - Removed wait_wh

[Qemu-devel] [PATCH v2 0/3] tests/tcg: disentangle makefiles

2019-08-07 Thread Paolo Bonzini
The tests/tcg rely a lot on per-target informations from the QEMU makefiles, but most of the definitions in there aren't really relevant to TCG tests. This series is just a cleanup, but it could also be a useful start in making it possible to compile tests/tcg out of QEMU's tree, and/or making it

Re: [Qemu-devel] [PATCH v2 0/3] add zstd cluster compression

2019-08-07 Thread Denis Plotnikov
Ping! On Jul 30 2019, at 5:45 pm, Denis Plotnikov wrote: Hi all! Is there any other comments besides Markus's one about adding zlib/zstd links to compressed cluster layout description? On Jul 4 2019, at 4:09 pm, Denis Plotnikov wrote: change log: v2: * relax the compression type setting restr

Re: [Qemu-devel] [PATCH v2 0/3] require newer glib2 to enable autofree'ing of stack variables exiting scope

2019-07-31 Thread Alex Bennée
Daniel P. Berrangé writes: > On Wed, Jul 31, 2019 at 03:04:29PM +0100, Alex Bennée wrote: >> >> Daniel P. Berrangé writes: >> >> > Both GCC and CLang support a C extension attribute((cleanup)) which >> > allows you to define a function that is invoked when a stack variable >> > exits scope. Th

Re: [Qemu-devel] [PATCH v2 0/3] require newer glib2 to enable autofree'ing of stack variables exiting scope

2019-07-31 Thread Daniel P . Berrangé
On Wed, Jul 31, 2019 at 03:04:29PM +0100, Alex Bennée wrote: > > Daniel P. Berrangé writes: > > > Both GCC and CLang support a C extension attribute((cleanup)) which > > allows you to define a function that is invoked when a stack variable > > exits scope. This typically used to free the memory

Re: [Qemu-devel] [PATCH v2 0/3] require newer glib2 to enable autofree'ing of stack variables exiting scope

2019-07-31 Thread Eric Blake
On 7/31/19 9:04 AM, Alex Bennée wrote: > > Daniel P. Berrangé writes: > >> Both GCC and CLang support a C extension attribute((cleanup)) which >> allows you to define a function that is invoked when a stack variable >> exits scope. This typically used to free the memory allocated to it, >> thoug

Re: [Qemu-devel] [PATCH v2 0/3] require newer glib2 to enable autofree'ing of stack variables exiting scope

2019-07-31 Thread Alex Bennée
Daniel P. Berrangé writes: > Both GCC and CLang support a C extension attribute((cleanup)) which > allows you to define a function that is invoked when a stack variable > exits scope. This typically used to free the memory allocated to it, > though you're not restricted to this. For example it

Re: [Qemu-devel] [PATCH v2 0/3] require newer glib2 to enable autofree'ing of stack variables exiting scope

2019-07-31 Thread Marc-André Lureau
On Thu, Jul 25, 2019 at 12:44 PM Daniel P. Berrangé wrote: > > Both GCC and CLang support a C extension attribute((cleanup)) which > allows you to define a function that is invoked when a stack variable > exits scope. This typically used to free the memory allocated to it, > though you're not rest

Re: [Qemu-devel] [PATCH v2 0/3] add zstd cluster compression

2019-07-30 Thread Denis Plotnikov
Hi all! Is there any other comments besides Markus's one about adding zlib/zstd links to compressed cluster layout description? On Jul 4 2019, at 4:09 pm, Denis Plotnikov wrote: change log: v2: * relax the compression type setting restriction in the spec * fix qcow2 header size checking * fix e

[Qemu-devel] [PATCH v2 0/3] migration: add speed limit for multifd migration

2019-07-29 Thread Ivan Ren
From: Ivan Ren Currently multifd migration has not been limited and it will consume the whole bandwidth of Nic. These two patches add speed limitation to it. This is the v3 patches: v3 VS v2: Add Reviewed info and Suggested info. v2 VS v1: 1. change qemu_file_update_rate_transfer interface nam

Re: [Qemu-devel] [PATCH v2 0/3] migration: add speed limit for multifd migration

2019-07-29 Thread Wei Yang
On Mon, Jul 29, 2019 at 04:01:18PM +0800, Ivan Ren wrote: >Currently multifd migration has not been limited and it will consume >the whole bandwidth of Nic. These two patches add speed limitation to >it. > >This is the v2 patches, differences with v1: >1. change qemu_file_update_rate_transfer inter

[Qemu-devel] [PATCH v2 0/3] iotests: use python logging

2019-07-29 Thread John Snow
Based-on: https://github.com/jnsnow/qemu/tree/bitmaps This series uses python logging to enable output conditionally on iotests.log(). We unify an initialization call (which also enables debugging output for those tests with -d) and then make the switch inside of iotests. It will help alleviate t

[Qemu-devel] [PATCH v2 0/3] migration: add speed limit for multifd migration

2019-07-29 Thread Ivan Ren
Currently multifd migration has not been limited and it will consume the whole bandwidth of Nic. These two patches add speed limitation to it. This is the v2 patches, differences with v1: 1. change qemu_file_update_rate_transfer interface name to qemu_file_update_transfer 2. add a new patch to

[Qemu-devel] [PATCH v2 0/3] require newer glib2 to enable autofree'ing of stack variables exiting scope

2019-07-25 Thread Daniel P . Berrangé
Both GCC and CLang support a C extension attribute((cleanup)) which allows you to define a function that is invoked when a stack variable exits scope. This typically used to free the memory allocated to it, though you're not restricted to this. For example it could be used to unlock a mutex. We co

Re: [Qemu-devel] [PATCH v2 0/3] Series to implement suspend for ppc/spapr

2019-07-22 Thread David Gibson
On Mon, Jul 22, 2019 at 01:20:08PM +0200, Paolo Bonzini wrote: > On 22/07/19 10:39, David Gibson wrote: > > On Mon, Jul 22, 2019 at 03:32:12PM +1000, Nicholas Piggin wrote: > >> Hi, this series is rebased on top of the qmp event fix, and takes > >> Paolo's suggestion to implement ->wakeup for i386

Re: [Qemu-devel] [PATCH v2 0/3] Series to implement suspend for ppc/spapr

2019-07-22 Thread David Gibson
On Mon, Jul 22, 2019 at 01:20:08PM +0200, Paolo Bonzini wrote: > On 22/07/19 10:39, David Gibson wrote: > > On Mon, Jul 22, 2019 at 03:32:12PM +1000, Nicholas Piggin wrote: > >> Hi, this series is rebased on top of the qmp event fix, and takes > >> Paolo's suggestion to implement ->wakeup for i386

Re: [Qemu-devel] [PATCH v2 0/3] Series to implement suspend for ppc/spapr

2019-07-22 Thread Paolo Bonzini
On 22/07/19 10:39, David Gibson wrote: > On Mon, Jul 22, 2019 at 03:32:12PM +1000, Nicholas Piggin wrote: >> Hi, this series is rebased on top of the qmp event fix, and takes >> Paolo's suggestion to implement ->wakeup for i386 before adding >> ppc, which makes it much nicer. >> >> If the first two

Re: [Qemu-devel] [PATCH v2 0/3] Series to implement suspend for ppc/spapr

2019-07-22 Thread David Gibson
On Mon, Jul 22, 2019 at 03:32:12PM +1000, Nicholas Piggin wrote: > Hi, this series is rebased on top of the qmp event fix, and takes > Paolo's suggestion to implement ->wakeup for i386 before adding > ppc, which makes it much nicer. > > If the first two patches can be agreed on initially and merge

[Qemu-devel] [PATCH v2 0/3] Series to implement suspend for ppc/spapr

2019-07-21 Thread Nicholas Piggin
Hi, this series is rebased on top of the qmp event fix, and takes Paolo's suggestion to implement ->wakeup for i386 before adding ppc, which makes it much nicer. If the first two patches can be agreed on initially and merged, I can take the third patch through the ppc list after that. Thanks, Nic

[Qemu-devel] [PATCH v2 0/3] Series to implement suspend for ppc/spapr

2019-07-21 Thread Nicholas Piggin
Hi, this series is rebased on top of the qmp event fix, and takes Paolo's suggestion to implement ->wakeup for i386 before adding ppc, which makes it much nicer. If the first two patches can be agreed on initially and merged, I can take the third patch through the ppc list after that. Thanks, Nic

Re: [Qemu-devel] [PATCH v2 0/3] High downtime with 95+ throttle pct

2019-07-17 Thread no-reply
Patchew URL: https://patchew.org/QEMU/20190716145421.17645-1-yury-ko...@yandex-team.ru/ Hi, This series failed the asan build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. === TEST SCRIPT BEGIN === #!/bin/ba

[Qemu-devel] [PATCH v2 0/3] High downtime with 95+ throttle pct

2019-07-16 Thread Yury Kotov
Hi, V2: * Added a test * Fixed qemu_cond_timedwait for qsp I wrote a test for migration auto converge and found out a strange thing: 1. Enable auto converge 2. Set max-bandwidth 1Gb/s 3. Set downtime-limit 1ms 4. Run standard test (just writes a byte per page) 5. Wait for converge 6. It's converg

[Qemu-devel] [PATCH v2 0/3] Add block size histogram qapi interface

2019-07-08 Thread zhenwei pi
Modify command 'block-latency-histogram-set' to make block histogram interface common to use. And support block size histogram. Thanks to Eric Blake&Vladimir Sementsov-Ogievskiy for the suggestions. This command has been tested for half year on QEMU-2.12, and we found that 3K+ virtual machines wri

[Qemu-devel] [PATCH v2 0/3] add zstd cluster compression

2019-07-04 Thread Denis Plotnikov
change log: v2: * relax the compression type setting restriction in the spec * fix qcow2 header size checking * fix error processing and messaging * fix qcow2 image specific info reporting * set Qcow2CompressionType zstd config dependant * add zstd compressed cluster format

[Qemu-devel] [PATCH v2 0/3] qapi: block-dirty-bitmap-remove transaction action

2019-07-01 Thread John Snow
Hi, this is a proposal based off of Vladimir's patchset: [Qemu-devel] [PATCH 0/4] qapi: block-dirty-bitmap-remove transaction action It replaces patches two and three with a modified patch (now patch 2) that foregoes the need for a hide()/unhide() bitmap API. I think it's suitable as a smaller alt

Re: [Qemu-devel] [PATCH v2 0/3] restrict bridge interface name to IFNAMSIZ

2019-07-01 Thread no-reply
Patchew URL: https://patchew.org/QEMU/20190701090904.31312-1-ppan...@redhat.com/ Hi, This series seems to have some coding style problems. See output below for more information: Message-id: 20190701090904.31312-1-ppan...@redhat.com Subject: [Qemu-devel] [PATCH v2 0/3] restrict bridge

Re: [Qemu-devel] [PATCH v2 0/3] restrict bridge interface name to IFNAMSIZ

2019-07-01 Thread no-reply
Patchew URL: https://patchew.org/QEMU/20190701090904.31312-1-ppan...@redhat.com/ Hi, This series seems to have some coding style problems. See output below for more information: Message-id: 20190701090904.31312-1-ppan...@redhat.com Type: series Subject: [Qemu-devel] [PATCH v2 0/3] restrict

[Qemu-devel] [PATCH v2 0/3] restrict bridge interface name to IFNAMSIZ

2019-07-01 Thread P J P
From: Prasad J Pandit Hello, Linux net_deivce defines network interface name to be of IFNAMSIZE(=16) bytes, including the terminating null('\0') byte. Qemu tap deivce, while invoking 'qemu-bridge-helper' tool to set up the network bridge interface, supplies bridge name of 16 characters, thus al

[Qemu-devel] [PATCH V2 0/3] Add block size histogram qapi interface

2019-06-23 Thread zhenwei pi
Modify command 'block-latency-histogram-set' to make block histogram interface common to use. And support block size histogram. Thanks to Eric Blake&Vladimir Sementsov-Ogievskiy for the suggestions. This command has been tested for half year on QEMU-2.12, and we found that 3K+ virtual machines wri

[Qemu-devel] [PATCH v2 0/3] target/mips: Improve MSA tests

2019-06-20 Thread Aleksandar Markovic
From: Aleksandar Markovic This series contains various improvements and additions of MSA ASE TCG tests. v1-v2: - added some tests from bit move group - improved and updated commit messages Aleksandar Markovic (3): tests/tcg: target/mips: Include isa/ase and group name in test output te

Re: [Qemu-devel] [PATCH v2 0/3] vmdk: Add read-only support for the new seSparse format

2019-06-19 Thread Sam Eiderman
Gentle ping > On 5 Jun 2019, at 15:17, Sam Eiderman wrote: > > v1: > > VMware introduced a new snapshot format in VMFS6 - seSparse (Space > Efficient Sparse) which is the default format available in ESXi 6.7. > Add read-only support for the new snapshot format. > > v2: > > Fixed after Max's r

[Qemu-devel] [PATCH v2 0/3] block: BDRV_REQ_PREFETCH

2019-06-18 Thread Vladimir Sementsov-Ogievskiy
Hi all! Here is small new read flag: BDRV_REQ_PREFETCH, which in combination with BDRV_REQ_COPY_ON_READ does copy-on-read without extra buffer for read data. This means that only parts that needs COR will be actually read and only corresponding buffers allocated, no more. This allows to improve a

Re: [Qemu-devel] [PATCH v2 0/3] vhost-scsi: Support migration

2019-06-12 Thread Paolo Bonzini
On 03/06/19 01:40, Liran Alon wrote: > Any news on when this patch-series is expected to be merged to upstream QEMU? > It was accepted 2 months ago. It was merged on June 6th. Paolo

Re: [Qemu-devel] [PATCH v2 0/3] MAINTAINERS: Clean up and improve section headlines

2019-06-07 Thread Markus Armbruster
Queued with PATCH 1 replaced by a prior patch from Philippe. Actual patch is identical.

[Qemu-devel] [PATCH v2 0/3] MAINTAINERS: Clean up and improve section headlines

2019-06-06 Thread Markus Armbruster
v2: * PATCH 2: - Commit message cleaned up [Eric] - Several headlines improved further [Philippe, Aleksandar, Cornelia] - "Common code" improved, too Markus Armbruster (3): MAINTAINERS: Drop redundant L: qemu-devel@nongnu.org MAINTAINERS: Improve section headlines MAINTAINERS: Polish h

[Qemu-devel] [PATCH v2 0/3] vmdk: Add read-only support for the new seSparse format

2019-06-05 Thread Sam Eiderman
v1: VMware introduced a new snapshot format in VMFS6 - seSparse (Space Efficient Sparse) which is the default format available in ESXi 6.7. Add read-only support for the new snapshot format. v2: Fixed after Max's review: * Removed strict sesparse checks * Reduced maximal L1 table size * Added n

Re: [Qemu-devel] [PATCH v2 0/3] vhost-scsi: Support migration

2019-06-02 Thread Michael S. Tsirkin
On Mon, Jun 03, 2019 at 02:40:04AM +0300, Liran Alon wrote: > Any news on when this patch-series is expected to be merged to upstream QEMU? > It was accepted 2 months ago. > > Thanks, > -Liran > > > On 25 Apr 2019, at 20:53, Michael S. Tsirkin wrote: > > > > On Thu, Apr 25, 2019 at 09:38:19AM

Re: [Qemu-devel] [PATCH v2 0/3] vhost-scsi: Support migration

2019-06-02 Thread Liran Alon
Any news on when this patch-series is expected to be merged to upstream QEMU? It was accepted 2 months ago. Thanks, -Liran > On 25 Apr 2019, at 20:53, Michael S. Tsirkin wrote: > > On Thu, Apr 25, 2019 at 09:38:19AM +0100, Stefan Hajnoczi wrote: >> On Wed, Apr 24, 2019 at 07:38:57PM +0300, Lir

Re: [Qemu-devel] [PATCH v2 0/3] Update documentation and help related to the preallocation parameter

2019-05-29 Thread Markus Armbruster
Stefano Garzarella writes: > Following Markus' advice, I updated the documentation of preallocation > parameter in qapi/block-core.json adding default and allowed values (patch 1). > I also updated the help related to BLOCK_OPT_PREALLOC in the QemuOptsList of > file-posix (patch 2) and gluster (p

Re: [Qemu-devel] [PATCH v2 0/3] Update documentation and help related to the preallocation parameter

2019-05-29 Thread Max Reitz
On 28.05.19 08:15, Markus Armbruster wrote: > Kevin, Max, this series looks ready to me. Feel free to ask me to take > it through my tree. *ask* :-) signature.asc Description: OpenPGP digital signature

Re: [Qemu-devel] [PATCH v2 0/3] Update documentation and help related to the preallocation parameter

2019-05-27 Thread Markus Armbruster
Kevin, Max, this series looks ready to me. Feel free to ask me to take it through my tree.

Re: [Qemu-devel] [PATCH v2 0/3] aspeed: cleanups and extensions

2019-05-24 Thread Eduardo Habkost
On Thu, May 23, 2019 at 03:03:11PM +0200, Cédric Le Goater wrote: > On 5/23/19 2:52 PM, Peter Maydell wrote: > > On Mon, 20 May 2019 at 17:32, Philippe Mathieu-Daudé > > wrote: > >> > >> On 5/20/19 3:32 PM, Cédric Le Goater wrote: > Peter, > > do you want me to resend with only the

[Qemu-devel] [PATCH v2 0/3] Update documentation and help related to the preallocation parameter

2019-05-24 Thread Stefano Garzarella
Following Markus' advice, I updated the documentation of preallocation parameter in qapi/block-core.json adding default and allowed values (patch 1). I also updated the help related to BLOCK_OPT_PREALLOC in the QemuOptsList of file-posix (patch 2) and gluster (patch 3). v2: - Patch 1: removed ref

Re: [Qemu-devel] [PATCH v2 0/3] aspeed: cleanups and extensions

2019-05-23 Thread Cédric Le Goater
On 5/23/19 2:52 PM, Peter Maydell wrote: > On Mon, 20 May 2019 at 17:32, Philippe Mathieu-Daudé > wrote: >> >> On 5/20/19 3:32 PM, Cédric Le Goater wrote: Peter, do you want me to resend with only the two first patches and include Joel's in the same series ? I would leave out

Re: [Qemu-devel] [PATCH v2 0/3] aspeed: cleanups and extensions

2019-05-23 Thread Peter Maydell
On Mon, 20 May 2019 at 17:32, Philippe Mathieu-Daudé wrote: > > On 5/20/19 3:32 PM, Cédric Le Goater wrote: > >> Peter, > >> > >> do you want me to resend with only the two first patches and include > >> Joel's in the same series ? I would leave out the part Philippe is > >> covering in his object

Re: [Qemu-devel] [PATCH v2 0/3] aspeed: cleanups and extensions

2019-05-20 Thread Philippe Mathieu-Daudé
On 5/20/19 3:32 PM, Cédric Le Goater wrote: >> Peter, >> >> do you want me to resend with only the two first patches and include >> Joel's in the same series ? I would leave out the part Philippe is >> covering in his object_initialize_child() patchset. > > Nope, we can not do that, conflicts a

Re: [Qemu-devel] [PATCH v2 0/3] aspeed: cleanups and extensions

2019-05-20 Thread Cédric Le Goater
> Peter, > > do you want me to resend with only the two first patches and include > Joel's in the same series ? I would leave out the part Philippe is > covering in his object_initialize_child() patchset. Nope, we can not do that, conflicts arise. I suppose the easier is wait for Philippe's pa

Re: [Qemu-devel] [PATCH v2 0/3] aspeed: cleanups and extensions

2019-05-20 Thread Cédric Le Goater
Hello, On 5/20/19 1:09 PM, Philippe Mathieu-Daudé wrote: > On 5/20/19 9:47 AM, Cédric Le Goater wrote: >> Hello, >> >> On 5/6/19 4:20 PM, Cédric Le Goater wrote: >>> Hello, >>> >>> Here is a series adding a couple of cleanups to the Aspeed SoCs to >>> prepare ground for extensions and new SoCs. >>

Re: [Qemu-devel] [PATCH v2 0/3] aspeed: cleanups and extensions

2019-05-20 Thread Philippe Mathieu-Daudé
On 5/20/19 9:47 AM, Cédric Le Goater wrote: > Hello, > > On 5/6/19 4:20 PM, Cédric Le Goater wrote: >> Hello, >> >> Here is a series adding a couple of cleanups to the Aspeed SoCs to >> prepare ground for extensions and new SoCs. >> >> Thanks, >> >> C. >> >> Changes since v1: >> >> - moved enum d

Re: [Qemu-devel] [PATCH v2 0/3] aspeed: cleanups and extensions

2019-05-20 Thread Cédric Le Goater
Hello, On 5/6/19 4:20 PM, Cédric Le Goater wrote: > Hello, > > Here is a series adding a couple of cleanups to the Aspeed SoCs to > prepare ground for extensions and new SoCs. > > Thanks, > > C. > > Changes since v1: > > - moved enum defining the Aspeed controller names under aspeed_soc.h >

Re: [Qemu-devel] [PATCH v2 0/3] qemu-img: rebase: Improve/optimize rebase operation

2019-05-19 Thread Sam Eiderman
Gentle ping. Do you want me to resend this patch as a new top-level thread? Thanks, Sam > On 2 May 2019, at 17:21, Eric Blake wrote: > > On 5/2/19 8:58 AM, Sam Eiderman wrote: >> This patch series aims to improve the speed of qemu-img rebase. >> >> 1. Mainly by removing unnecessary reads when

Re: [Qemu-devel] [PATCH v2 0/3] vhost-scsi: Support migration

2019-05-10 Thread Liran Alon
> On 25 Apr 2019, at 20:53, Michael S. Tsirkin wrote: > > On Thu, Apr 25, 2019 at 09:38:19AM +0100, Stefan Hajnoczi wrote: >> On Wed, Apr 24, 2019 at 07:38:57PM +0300, Liran Alon wrote: >>> >>> On 18 Apr 2019, at 12:41, Stefan Hajnoczi wrote: On Tue, Apr 16, 2019 at 03:59:09

Re: [Qemu-devel] [PATCH v2 0/3] qemu-img: Allow rebase with no input base

2019-05-08 Thread Kevin Wolf
Am 08.05.2019 um 16:01 hat Max Reitz geschrieben: > This series allows using qemu-img rebase (without -u) on images that do > not have a backing file. Right now, this fails with the rather cryptic > error message: > > $ qemu-img rebase -b base.qcow2 foo.qcow2 > qemu-img: Could not open old backin

[Qemu-devel] [PATCH v2 0/3] qemu-img: Allow rebase with no input base

2019-05-08 Thread Max Reitz
This series allows using qemu-img rebase (without -u) on images that do not have a backing file. Right now, this fails with the rather cryptic error message: $ qemu-img rebase -b base.qcow2 foo.qcow2 qemu-img: Could not open old backing file '': The 'file' block driver requires a file name Yeah

[Qemu-devel] [PATCH v2 0/3] aspeed: cleanups and extensions

2019-05-06 Thread Cédric Le Goater
Hello, Here is a series adding a couple of cleanups to the Aspeed SoCs to prepare ground for extensions and new SoCs. Thanks, C. Changes since v1: - moved enum defining the Aspeed controller names under aspeed_soc.h - removed AspeedSoCInfo 'sdram_base' field - fixed clang compilation Cédri

[Qemu-devel] [PATCH v2 0/3] Improve 40p, make AIX 5.1 boot

2019-05-04 Thread Artyom Tarasenko
This series makes various fixes for the -M 40p target. Particularly now it's possible to boot AIX 5.1 (both from a cdrom and a hard disk). The OFW image: https://github.com/artyom-tarasenko/openfirmware/releases/download/20190406-AIX-boots/q40pofw-serial.rom The command line: qemu-system-ppc -

Re: [Qemu-devel] [PATCH v2 0/3] Leon3 patches

2019-05-03 Thread KONRAD Frederic
Le 5/3/19 à 10:19 AM, Mark Cave-Ayland a écrit : On 25/04/2019 13:18, KONRAD Frederic wrote: Hi all, Those are some little fixes for the leon3 machine: * The first part initializes the uart and the timer when no bios are provided. * The second part adds AHB and APB plug and play

Re: [Qemu-devel] [PATCH v2 0/3] Leon3 patches

2019-05-03 Thread Mark Cave-Ayland
On 25/04/2019 13:18, KONRAD Frederic wrote: > Hi all, > > Those are some little fixes for the leon3 machine: > * The first part initializes the uart and the timer when no bios are > provided. > * The second part adds AHB and APB plug and play devices to allow to boot > linux. > * Th

Re: [Qemu-devel] [PATCH v2 0/3] qemu-img: rebase: Improve/optimize rebase operation

2019-05-02 Thread Sam
I see, Thanks > On 2 May 2019, at 17:21, Eric Blake wrote: > > On 5/2/19 8:58 AM, Sam Eiderman wrote: >> This patch series aims to improve the speed of qemu-img rebase. >> >> 1. Mainly by removing unnecessary reads when rebasing on the same >> chain. >> 2. But also by minimizing the number o

Re: [Qemu-devel] [PATCH v2 0/3] qemu-img: rebase: Improve/optimize rebase operation

2019-05-02 Thread Eric Blake
On 5/2/19 8:58 AM, Sam Eiderman wrote: > This patch series aims to improve the speed of qemu-img rebase. > > 1. Mainly by removing unnecessary reads when rebasing on the same >chain. > 2. But also by minimizing the number of bdrv_open calls rebase >requires. > When sending a v2 series, i

[Qemu-devel] [PATCH v2 0/3] qemu-img: rebase: Improve/optimize rebase operation

2019-05-02 Thread Sam Eiderman
This patch series aims to improve the speed of qemu-img rebase. 1. Mainly by removing unnecessary reads when rebasing on the same chain. 2. But also by minimizing the number of bdrv_open calls rebase requires. v2: - Added missing g_free in "qemu-img: rebase: Reuse in-chain BlockDriverS

Re: [Qemu-devel] [PATCH v2 0/3] hw/arm/virt: Support firmware configuration with -blockdev

2019-04-30 Thread Peter Maydell
On Tue, 16 Apr 2019 at 10:13, Markus Armbruster wrote: > > László asked for feature parity with the PC machine types. > > v2: > * PATCH 1: Split off PATCH 2 [László] > * PATCH 2: Factor out the loop body, not the whole loop > * PATCH 3: Rebase on previous change >More detailed commit m

Re: [Qemu-devel] [PATCH v2 0/3] vhost-scsi: Support migration

2019-04-25 Thread Michael S. Tsirkin
On Thu, Apr 25, 2019 at 09:38:19AM +0100, Stefan Hajnoczi wrote: > On Wed, Apr 24, 2019 at 07:38:57PM +0300, Liran Alon wrote: > > > > > > > On 18 Apr 2019, at 12:41, Stefan Hajnoczi wrote: > > > > > > On Tue, Apr 16, 2019 at 03:59:09PM +0300, Liran Alon wrote: > > >> Hi, > > >> > > >> This pa

[Qemu-devel] [PATCH v2 0/3] Leon3 patches

2019-04-25 Thread KONRAD Frederic
Hi all, Those are some little fixes for the leon3 machine: * The first part initializes the uart and the timer when no bios are provided. * The second part adds AHB and APB plug and play devices to allow to boot linux. * The third part adds myself to the MAINTAINERS for this board.

Re: [Qemu-devel] [PATCH v2 0/3] vhost-scsi: Support migration

2019-04-25 Thread Stefan Hajnoczi
On Wed, Apr 24, 2019 at 07:38:57PM +0300, Liran Alon wrote: > > > > On 18 Apr 2019, at 12:41, Stefan Hajnoczi wrote: > > > > On Tue, Apr 16, 2019 at 03:59:09PM +0300, Liran Alon wrote: > >> Hi, > >> > >> This patch series aims to add supprot to migrate a VM with a vhost-scsi > >> device. > >>

Re: [Qemu-devel] [PATCH v2 0/3] vhost-scsi: Support migration

2019-04-24 Thread Liran Alon
> On 18 Apr 2019, at 12:41, Stefan Hajnoczi wrote: > > On Tue, Apr 16, 2019 at 03:59:09PM +0300, Liran Alon wrote: >> Hi, >> >> This patch series aims to add supprot to migrate a VM with a vhost-scsi >> device. >> >> The 1st patch fixes a bug of mistakenly not stopping vhost-scsi backend wh

[Qemu-devel] [PATCH v2 0/3] Simplify some not-really-necessary PCI bus callbacks

2019-04-23 Thread David Gibson
c2077e2c "pci: Adjust PCI config limit based on bus topology" introduced checking the availability of extended config space for PCI-E devices which are in a bus topology that doesn't permit extended config space access (e.g. under PCI-E to PCI then PCI to PCI-E bridges). This caused some problems

[Qemu-devel] [PATCH v2 0/3] hw: edu: some fixes

2019-04-20 Thread Li Qiang
Recently I am considering write a driver for edu device. After reading the spec, I found these three small issue. Two first two related the MMIO access and the third is related the DMA operation. Change since v1: Fix format compile error on Windows Li Qiang (3): edu: mmio: set 'max_access_size'

[Qemu-devel] [PATCH v2 0/3] hw: edu: some fixes

2019-04-20 Thread Li Qiang
Recently I am considering write a driver for edu device. After reading the spec, I found these three small issue. Two first two related the MMIO access and the third is related the DMA operation. Change since v1: Fix format compile error on Windows Li Qiang (3): tests: fw_cfg: add splash time t

[Qemu-devel] [PATCH v2 0/3] Fix overflow bug in qcow2 discard

2019-04-19 Thread Vladimir Sementsov-Ogievskiy
v2: [mostly by Eric's review] 01: new 02: point to bug introducing commit in cover letter [Eric] [but I failed to compile it, to check] drop s/INT_MAX/BDRV_REQUEST_MAX_BYTES/ chunk 03: - improve wording - cheating with preallocation=metadata and discards to make test quick and no

Re: [Qemu-devel] [PATCH v2 0/3] vhost-scsi: Support migration

2019-04-18 Thread Stefan Hajnoczi
On Tue, Apr 16, 2019 at 03:59:09PM +0300, Liran Alon wrote: > Hi, > > This patch series aims to add supprot to migrate a VM with a vhost-scsi > device. > > The 1st patch fixes a bug of mistakenly not stopping vhost-scsi backend when a > VM is stopped (As happens on migratino pre-copy completion)

[Qemu-devel] [PATCH v2 0/3] numa: move numa global variables into MachineState

2019-04-17 Thread Tao Xu
The aim of this patch is to add struct NumaState in MachineState and move existing numa global nb_numa_nodes into NumaState. And add variable numa_support into MachineClass to decide which submachines support NUMA. --- Changes in v2: - fix the mistake in numa_complete_configuration in numa.c

[Qemu-devel] [PATCH v2 0/3] vhost-scsi: Support migration

2019-04-16 Thread Liran Alon
Hi, This patch series aims to add supprot to migrate a VM with a vhost-scsi device. The 1st patch fixes a bug of mistakenly not stopping vhost-scsi backend when a VM is stopped (As happens on migratino pre-copy completion). The 2nd patch adds ability to save/load vhost-scsi device state in VMSta

[Qemu-devel] [PATCH v2 0/3] hw/arm/virt: Support firmware configuration with -blockdev

2019-04-16 Thread Markus Armbruster
László asked for feature parity with the PC machine types. v2: * PATCH 1: Split off PATCH 2 [László] * PATCH 2: Factor out the loop body, not the whole loop * PATCH 3: Rebase on previous change More detailed commit message [László] Markus Armbruster (3): pc: Rearrange pc_system_firmw

[Qemu-devel] [PATCH v2 0/3] block/stream: get rid of the base

2019-04-01 Thread Andrey Shinkevich
This series introduces a bottom intermediate node that eliminates the dependency on the base that may change while stream job is running. It happens when stream/commit parallel jobs are running on the same backing chain. The base node of the stream job may be a top node of the parallel commit job a

  1   2   3   4   5   6   7   8   9   10   >