Hi -- not sure what's happened with this patchset, but
can we at least get the first patch (which fixes some
coverity errors) in, even if the other two need more
consideration?
(cc'ing Gerd as audio maintainer.)
thanks
-- PMM
On Wed, 11 Sep 2019 at 00:27, Kővágó, Zoltán wrote:
>
> Hi,
>
> This
* Wei Yang (richardw.y...@linux.intel.com) wrote:
> Three patches to cleanup postcopy:
>
> [1]: split canonicalize bitmap and discard page
> [2]: remove unsentmap since it is not necessary
> [3]: cleanup the get_queued_page_not_dirty
Queued
>
> Wei Yang (3):
> migration/postcopy: not necessar
Add new test for migration that bringup vm with different machine types
and migrate it, introduce new API in avocado_qemu to query all the machine
types supported by qemu.
Test run:
# avocado run migration.py
JOB ID : ef54f57a073eb267d2347e32225f2adbe27969de
JOB LOG:
/home/bala/avocado-f
Hi, Dave and Juan
Would you mind taking a look at this one?
On Mon, Aug 19, 2019 at 02:18:40PM +0800, Wei Yang wrote:
>Three patches to cleanup postcopy:
>
>[1]: split canonicalize bitmap and discard page
>[2]: remove unsentmap since it is not necessary
>[3]: cleanup the get_queued_page_not_dirty
12.09.2019 0:46, John Snow wrote:
>
>
> On 9/11/19 10:09 AM, Vladimir Sementsov-Ogievskiy wrote:
>> 10.09.2019 23:37, no-re...@patchew.org wrote:
>>> Patchew URL:
>>> https://patchew.org/QEMU/20190910162724.79574-1-vsement...@virtuozzo.com/
>>>
>>>
>>>
>>> Hi,
>>>
>>> This series failed the dock
On 9/11/19 10:09 AM, Vladimir Sementsov-Ogievskiy wrote:
> 10.09.2019 23:37, no-re...@patchew.org wrote:
>> Patchew URL:
>> https://patchew.org/QEMU/20190910162724.79574-1-vsement...@virtuozzo.com/
>>
>>
>>
>> Hi,
>>
>> This series failed the docker-quick@centos7 build test. Please find the
>>
Patchew URL:
https://patchew.org/QEMU/20190911164202.31136-1-dgilb...@redhat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH 0/3] Automatic RCU read unlock
Message-id: 20190911164202.31136-1-dgilb
* Daniel P. Berrangé (berra...@redhat.com) wrote:
> On Wed, Sep 11, 2019 at 05:41:59PM +0100, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert"
> >
> > This patch uses glib's g_auto mechanism to automatically free
> > rcu_read_lock's at the end of the block. Given that human
On Wed, Sep 11, 2019 at 05:41:59PM +0100, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert"
>
> This patch uses glib's g_auto mechanism to automatically free
> rcu_read_lock's at the end of the block. Given that humans
> have a habit of forgetting an error path somewhere it's
From: "Dr. David Alan Gilbert"
This patch uses glib's g_auto mechanism to automatically free
rcu_read_lock's at the end of the block. Given that humans
have a habit of forgetting an error path somewhere it's
best to leave it to the compiler.
In particular:
https://bugzilla.redhat.com/show_bug
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
10.09.2019 23:37, no-re...@patchew.org wrote:
> Patchew URL:
> https://patchew.org/QEMU/20190910162724.79574-1-vsement...@virtuozzo.com/
>
>
>
> Hi,
>
> This series failed the docker-quick@centos7 build test. Please find the
> testing commands and
> their output below. If you have Docker inst
Patchew URL:
https://patchew.org/QEMU/20190911014353.5926-1-richard.hender...@linaro.org/
Hi,
This series failed the docker-quick@centos7 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT
Patchew URL:
https://patchew.org/QEMU/20190911014353.5926-1-richard.hender...@linaro.org/
Hi,
This series failed the docker-quick@centos7 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT
02.08.2019. 18.29, "Philippe Mathieu-Daudé" је
написао/ла:
>
> Cc'ing broader MIPS audience.
>
> On 8/2/19 6:04 PM, Peter Maydell wrote:
> > This patchset converts the MIPS target away from the
> > old broken do_unassigned_access hook to the new (added in
> > 2017...) do_transaction_failed hook.
>
Patchew URL:
https://patchew.org/QEMU/20190911014353.5926-1-richard.hender...@linaro.org/
Hi,
This series failed the docker-quick@centos7 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT
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 was
the root cause for
https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg00036.html
I tried a couple of different approaches in load/store_helper, but
this i
Hi,
This series contains some random fixes for the "Audio 20190821 patches":
a coverity bugfix and pulseaudio connection/stream names fix.
Since there wasn't a clear consensus about naming the pa streams, I've
split it into two commits: the first time just uses the audiodev id
unconditionally, wh
Patchew URL:
https://patchew.org/QEMU/20190910120927.1669283-1-maozhon...@cmss.chinamobile.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH 0/3] some fix in tests/migration
Message-id: 20190910120927.1669283-1
Patchew URL:
https://patchew.org/QEMU/20190910162724.79574-1-vsement...@virtuozzo.com/
Hi,
This series failed the docker-quick@centos7 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEG
We need to lock qcow2 mutex on accessing in-image metadata, especially
on updating this metadata. Let's implement it.
Vladimir Sementsov-Ogievskiy (3):
block: move bdrv_can_store_new_dirty_bitmap to block/dirty-bitmap.c
block/dirty-bitmap: return int from
bdrv_remove_persistent_dirty_bitma
Patchew URL:
https://patchew.org/QEMU/20190910120927.1669283-1-maozhon...@cmss.chinamobile.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH 0/3] some fix in tests/migration
Message-id: 20190910120927.1669283-1
This patchset mainly fixes memory leak, typo and return
value of stress function in stress test.
Cc: arm...@redhat.com
Cc: laur...@vivier.eu
Cc: tony.ngu...@bt.com
Mao Zhongyi (3):
tests/migration: mem leak fix
tests/migration: fix a typo in comment
tests/migration：fix unreachable path in s
ping for Hervé.
22.08.2019. 20.16, "Aleksandar Markovic" је
написао/ла:
>
>
> 02.08.2019. 18.05, "Peter Maydell" је
написао/ла:
> >
> > This patchset converts the MIPS target away from the
> > old broken do_unassigned_access hook to the new (added in
> > 2017...) do_transaction_failed hook.
> >
On Fri, 2019-09-06 at 20:31 +0300, Maxim Levitsky wrote:
> 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 beeing encrypted with
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 beeing encrypted with wrong
sector address, which render it corrupted.
Bugzilla: http
On Tue, Sep 03, 2019 at 12:21:40PM +0100, Dr. David Alan Gilbert wrote:
> * Yury Kotov (yury-ko...@yandex-team.ru) wrote:
> > Hi,
> >
> > 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 cas
* Yury Kotov (yury-ko...@yandex-team.ru) wrote:
> Hi,
>
> 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: A, B and C
> 2. Server A has a VM 1, server B
On Wed, Aug 28, 2019 at 03:36:25PM -0400, Cleber Rosa wrote:
> This corrects some of the messages given on failures (aligning them to
> the test code), and splits a larger test into smaller and more
> manageable pieces.
Thanks!
I'm queueing this on python-next.
--
Eduardo
Patchew URL: https://patchew.org/QEMU/20190828193628.7687-1-cr...@redhat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH 0/3] Acceptance test x86_cpu_model_versions: fixes
and minor improvements
Message-id
This corrects some of the messages given on failures (aligning them to
the test code), and splits a larger test into smaller and more
manageable pieces.
Cleber Rosa (3):
Acceptance test x86_cpu_model_versions: shutdown VMs
Acceptance test x86_cpu_model_versions: fix mismatches between test
Hi,
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: A, B and C
2. Server A has a VM 1, server B has a VM 2
3. VM 1 and VM 2 want to migrate to the server C
4. T
Hi,
This series fixes two problems reported by Maxim Levitsky in relation of
my multiple audio backend patch series, and a small feature request.
Unfortunately I don't really use PulseAudio nowadays, so I haven't
tested it other than making sure it compiles and connects to pa.
Regards,
Zoltan
K
Aleksandar Markovic writes:
> 23.08.2019. 08.13, "Markus Armbruster" је написао/ла:
>>
>> Philippe Mathieu-Daudé writes:
>>
>> > Trivial cleanup of .mailmap to have a nice 'git shortlog' output.
>> >
>> > Philippe Mathieu-Daudé (3):
>> > mailmap: Reorder by sections
>> > mailmap: Update p
23.08.2019. 08.13, "Markus Armbruster" је написао/ла:
>
> Philippe Mathieu-Daudé writes:
>
> > Trivial cleanup of .mailmap to have a nice 'git shortlog' output.
> >
> > Philippe Mathieu-Daudé (3):
> > mailmap: Reorder by sections
> > mailmap: Update philmd email address
> > mailmap: Add man
Philippe Mathieu-Daudé writes:
> Trivial cleanup of .mailmap to have a nice 'git shortlog' output.
>
> Philippe Mathieu-Daudé (3):
> mailmap: Reorder by sections
> mailmap: Update philmd email address
> mailmap: Add many entries to improve 'git shortlog' statistics
>
> .mailmap | 123 +
Trivial cleanup of .mailmap to have a nice 'git shortlog' output.
Philippe Mathieu-Daudé (3):
mailmap: Reorder by sections
mailmap: Update philmd email address
mailmap: Add many entries to improve 'git shortlog' statistics
.mailmap | 123 +++-
02.08.2019. 18.05, "Peter Maydell" је написао/ла:
>
> This patchset converts the MIPS target away from the
> old broken do_unassigned_access hook to the new (added in
> 2017...) do_transaction_failed hook.
>
Herve, bonjour.
As far as I can see these changes are fine. May I ask you for your opini
On Thu, Aug 15, 2019 at 03:38:00PM -0300, Eduardo Habkost wrote:
> Currently, if die-id is omitted on -device for CPUs, we get a
> very confusing error message:
>
> $ qemu-system-x86_64 -smp 1,sockets=6,maxcpus=6 \
> -device qemu64-x86_64-cpu,socket-id=1,core-id=0,thread-id=0
> qemu-system
Three patches to cleanup postcopy:
[1]: split canonicalize bitmap and discard page
[2]: remove unsentmap since it is not necessary
[3]: cleanup the get_queued_page_not_dirty
Wei Yang (3):
migration/postcopy: not necessary to do discard when canonicalizing
bitmap
migration/postcopy: unsent
Hello,
These are some fixes to get MacOS driver closer to working. Patch 1
adds a simple VBlank interrupt (this could be refined later as MacOS
seems to poll it frequently enough to get 100% CPU usage when
enabled). Patch 2 fixes problems with mouse pointer color and movement
due to byte and word
Currently, if die-id is omitted on -device for CPUs, we get a
very confusing error message:
$ qemu-system-x86_64 -smp 1,sockets=6,maxcpus=6 \
-device qemu64-x86_64-cpu,socket-id=1,core-id=0,thread-id=0
qemu-system-x86_64: -device
qemu64-x86_64-cpu,socket-id=1,core-id=0,thread-id=0: \
On 25.07.19 17:55, Max Reitz wrote:
> Hi,
>
> 69f47505ee66afaa513305de0c1895a224e52c45 changed block_status so that it
> would only go down to the protocol layer if the format layer returned
> BDRV_BLOCK_RECURSE, thus indicating that it has no sufficient
> information whether a given range in the
evel@nongnu.org
> Subject: Re: [Qemu-devel] [PATCH 0/3] colo: Add support for continious
> replication
>
> Patchew URL:
> https://patchew.org/QEMU/cover.1565814686.git.lukasstra...@web.de/
>
>
>
> Hi,
>
> This series failed build test on s390x host. Please fi
Patchew URL: https://patchew.org/QEMU/cover.1565814686.git.lukasstra...@web.de/
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 ha
Hello Everyone,
These Patches add support for continious replication to colo.
Please review.
Regards,
Lukas Straub
Lukas Straub (3):
Replication: Ignore requests after failover
net/filter.c: Add Options to insert filters anywhere in the filter list
Document the qmp commands for continious r
On 13/08/2019 15:05, Paolo Bonzini wrote:
> On 13/08/19 14:02, Andrey Shinkevich wrote:
>> PINGING...
>
> I thought I had already said I queued the series?
>
> Paolo
>
Thank you Paolo.
I am clear now.
Andrey
>> On 30/07/2019 19:01, Andrey Shinkevich wrote:
>>> Running unit tests under the V
On 13/08/19 14:02, Andrey Shinkevich wrote:
> PINGING...
I thought I had already said I queued the series?
Paolo
> On 30/07/2019 19:01, Andrey Shinkevich wrote:
>> Running unit tests under the Valgrind may help to detect QEMU memory issues
>> (suggested by Denis V. Lunev). Some of the Valgrind r
PINGING...
On 30/07/2019 19:01, Andrey Shinkevich wrote:
> Running unit tests under the Valgrind may help to detect QEMU memory issues
> (suggested by Denis V. Lunev). Some of the Valgrind reports relate to the
> unit test code itself. Let's eliminate the detected memory issues to ease
> locating
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
diagnose nonsense fields containing no bits. I eliminated the
unused integer argument passed to the named function. I improved
the documentation.
On 7/31/19 6:29 AM, Vladimir Sementsov-Ogievskiy wrote:
> 30.07.2019 21:41, John Snow wrote:
>>
>>
>> On 7/30/19 12:32 PM, Vladimir Sementsov-Ogievskiy wrote:
>>> Hi all!
>>>
>>> Here are two small fixes.
>>>
>>> 01 is not a degradation at all, so it's OK for 4.2
>>> 02 is degradation of 3.0, so
* Wei Yang (richardw.y...@linux.intel.com) wrote:
> qemu_savevm_state_complete_precopy() iterates SaveStateEntry and does proper
> tasks for migration.
>
> For each iteration, in_postcopy and iterable_only would be checked to see
> whether it should skip. Since these two conditions are not SaveSta
* Wei Yang (richardw.y...@linux.intel.com) wrote:
> Some cleanup of function postcopy_send_discard_bm_ram:
>
> * use a more restrict check for discard page
> * break the loop when no more page to discard
> * it is for sure discard_length is not 0
>
> No functional change.
>
Queued
> Wei Yang (
On 07/08/19 18:38, Alex Bennée wrote:
>>> Rather, we use '#!/usr/bin/env bash' to find bash anywhere.
>> Nevermind - this script is pure Bourne shell. The only fix needed
>> should be
> I thought we wanted to use pure POSIX shell and not rely on bash-ism's
> creeping in?
>
There are uses of bash
Paolo Bonzini writes:
> On 07/08/19 15:33, Eric Blake wrote:
>> On 8/7/19 8:06 AM, Paolo Bonzini wrote:
>>> On 07/08/19 14:40, Alex Bennée wrote:
Paolo Bonzini writes:
> The tests/tcg rely a lot on per-target informations from
> the QEMU makefiles, but most of the defini
On 07/08/19 15:33, Eric Blake wrote:
> On 8/7/19 8:06 AM, Paolo Bonzini wrote:
>> On 07/08/19 14:40, Alex Bennée wrote:
>>>
>>> Paolo Bonzini writes:
>>>
The tests/tcg rely a lot on per-target informations from
the QEMU makefiles, but most of the definitions in there
aren't really r
On 8/7/19 8:06 AM, Paolo Bonzini wrote:
> On 07/08/19 14:40, Alex Bennée wrote:
>>
>> Paolo Bonzini writes:
>>
>>> 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 j
On 07/08/19 14:40, Alex Bennée wrote:
>
> Paolo Bonzini writes:
>
>> 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
Paolo Bonzini writes:
> 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
Improve coverage for modules: add a test that asks QEMU to check that
no symbols are missing from any of the modules.
Markus, is using qtest ok or should it use an x- qmp command instead?
Paolo
Marc-André Lureau (3):
module: use g_hash_table_add()
module: return success on module load
test
Add new test for migration that bringup vm with different machine types and
migrate it, introduce new API in avocado_qemu to query all the machine
types supported by qemu.
Test run:
# avocado run migration.py
JOB ID : ef54f57a073eb267d2347e32225f2adbe27969de
JOB LOG:
/home/bala/avocado-f
Cc'ing broader MIPS audience.
On 8/2/19 6:04 PM, Peter Maydell wrote:
> This patchset converts the MIPS target away from the
> old broken do_unassigned_access hook to the new (added in
> 2017...) do_transaction_failed hook.
>
> The motivation here is:
> * do_unassigned_access is broken because:
This patchset converts the MIPS target away from the
old broken do_unassigned_access hook to the new (added in
2017...) do_transaction_failed hook.
The motivation here is:
* do_unassigned_access is broken because:
+ it will be called for any kind of access to physical addresses
where th
This is the testcase for the copy-on-read fix I merged in a hurry for
4.1.0-rc3.
Kevin Wolf (3):
iotests: Move migration helpers to iotests.py
iotests: Enable -d for Python non-unittest tests
iotests: Test migration with all kinds of filter nodes
tests/qemu-iotests/194| 1 +
tests
This series is motivated by the bug fixed in commit 7cef3d1290
('scsi-cd: Fix inserting read-only media in empty drive'). After the
series is applied, media change is tested for all combinations of
floppy/ide-cd/scsi-cd with -drive/-blockdev and initially empty
drive/inserted media.
Kevin Wolf (3)
On 7/31/19 6:29 AM, Vladimir Sementsov-Ogievskiy wrote:
> 30.07.2019 21:41, John Snow wrote:
>>
>>
>> On 7/30/19 12:32 PM, Vladimir Sementsov-Ogievskiy wrote:
>>> Hi all!
>>>
>>> Here are two small fixes.
>>>
>>> 01 is not a degradation at all, so it's OK for 4.2
>>> 02 is degradation of 3.0, so
30.07.2019 21:41, John Snow wrote:
>
>
> On 7/30/19 12:32 PM, Vladimir Sementsov-Ogievskiy wrote:
>> Hi all!
>>
>> Here are two small fixes.
>>
>> 01 is not a degradation at all, so it's OK for 4.2
>> 02 is degradation of 3.0, so it's possibly OK for 4.2 too,
>> but it seems to be real bug an
On 7/30/19 12:32 PM, Vladimir Sementsov-Ogievskiy wrote:
> Hi all!
>
> Here are two small fixes.
>
> 01 is not a degradation at all, so it's OK for 4.2
> 02 is degradation of 3.0, so it's possibly OK for 4.2 too,
>but it seems to be real bug and fix is very simple, so,
>may be 4.1 is b
Hi all!
Here are two small fixes.
01 is not a degradation at all, so it's OK for 4.2
02 is degradation of 3.0, so it's possibly OK for 4.2 too,
but it seems to be real bug and fix is very simple, so,
may be 4.1 is better
Or you may take the whole series to 4.1 if you want.
Vladimir Sement
Running unit tests under the Valgrind may help to detect QEMU memory issues
(suggested by Denis V. Lunev). Some of the Valgrind reports relate to the
unit test code itself. Let's eliminate the detected memory issues to ease
locating critical ones.
Andrey Shinkevich (3):
test-throttle: Fix uninit
Patchew URL:
https://patchew.org/QEMU/20190730123759.21723-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 0/3] tests/tcg: disentangle makefiles
Message-id: 20190730123759.21723
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
* Stefan Hajnoczi (stefa...@redhat.com) wrote:
> The client must know the server's alignment constraints for FUSE_SETUPMAPPING
> and FUSE_REMOVEMAPPING. This is necessary because mmap(2)/munmap(2) have
> alignment constraints and the guest may have a different page size from the
> host. The new F
When we iterate the memory-device list to get the available range, it is not
necessary to iterate the whole list.
1) the first non-overlap range is the proper one if no hint is provided
2) no more overlap for hinted range if tmp exceed it
Wei Yang (3):
memory-device: not necessary to use goto f
On Fri, Jul 26, 2019 at 04:44:33PM +0200, Greg Kurz wrote:
> Some recent tests with AIX guests showed that we don't tear down
> MSIs that were allocated with the "change-msi" RTAS call, when
> the guest is rebooted. This series teach PHBs to do the cleanup
> at reset time.
>
> This bug has always
Some recent tests with AIX guests showed that we don't tear down
MSIs that were allocated with the "change-msi" RTAS call, when
the guest is rebooted. This series teach PHBs to do the cleanup
at reset time.
This bug has always been there. Not sure it is worth the pain to
have this fixed in 4.1.
-
The client must know the server's alignment constraints for FUSE_SETUPMAPPING
and FUSE_REMOVEMAPPING. This is necessary because mmap(2)/munmap(2) have
alignment constraints and the guest may have a different page size from the
host. The new FUSE_INIT map_alignment field communicates this informat
Hi,
69f47505ee66afaa513305de0c1895a224e52c45 changed block_status so that it
would only go down to the protocol layer if the format layer returned
BDRV_BLOCK_RECURSE, thus indicating that it has no sufficient
information whether a given range in the image is zero or not.
Generally, this is because
Paolo Bonzini's on July 18, 2019 9:08 pm:
> On 18/07/19 12:39, Nicholas Piggin wrote:
>> Any comments on this series would be welcome. Hopefully someone who
>> knows i386 can give some feedback on the possible bug fix, and
>> whether the new wakeup method will suit i386.
>
> Looks good, though onl
On 18/07/19 12:39, Nicholas Piggin wrote:
> Any comments on this series would be welcome. Hopefully someone who
> knows i386 can give some feedback on the possible bug fix, and
> whether the new wakeup method will suit i386.
Looks good, though only i386 supports wakeup so perhaps it's better to
DT
Any comments on this series would be welcome. Hopefully someone who
knows i386 can give some feedback on the possible bug fix, and
whether the new wakeup method will suit i386.
Thanks,
Nick
Nicholas Piggin (3):
qmp: don't emit the RESET event on wakeup
machine: Add wakeup method to MachineCla
Patchew URL:
https://patchew.org/QEMU/20190715142304.215018-1-borntrae...@de.ibm.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20190715142304.215018-1-borntrae...@de.ibm.com
Type: series
Subject: [Qemu-devel] [PATCH 0/3
On Mon, 15 Jul 2019 16:23:01 +0200
Christian Borntraeger wrote:
> Some fallout of the gen15 cpu model. As this is new in 4.1
> it is still time to fixup some aspects.
>
> Christian Borntraeger (3):
> s390x/cpumodel: remove esort from the default model
> s390x/cpumodel: also change name of vx
Short reads are possible with cache=writeback (see Patch 3 for details).
Handle this by resubmitting requests until the read is completed.
Patch 1 adds trace events useful for debugging io_uring.
Patch 2 fixes EINTR. This lays the groundwork for resubmitting requests in
Patch 3.
Aarushi: Feel f
Some fallout of the gen15 cpu model. As this is new in 4.1
it is still time to fixup some aspects.
Christian Borntraeger (3):
s390x/cpumodel: remove esort from the default model
s390x/cpumodel: also change name of vxbeh
s390x/cpumodel: change internal name of vxp to make description
target
On 15/07/19 11:55, Philippe Mathieu-Daudé wrote:
> I actually wanted to clean the USB devices (i.e. to not have
> USB3 devices appear on OHCI buses) but this is too late for
> the next release, so let's post the patches accumulated.
>
> Philippe Mathieu-Daudé (3):
> hw/Kconfig: PCI bus implies P
I actually wanted to clean the USB devices (i.e. to not have
USB3 devices appear on OHCI buses) but this is too late for
the next release, so let's post the patches accumulated.
Philippe Mathieu-Daudé (3):
hw/Kconfig: PCI bus implies PCI_DEVICES
hw/usb/Kconfig: Add CONFIG_USB_EHCI_PCI
hw/usb
The problem still exists in mainline, Ping for review
On Tue, Jun 25, 2019 at 9:18 PM Ivan Ren wrote:
> The patches fix the problems encountered in multifd migration when try
> to cancel the migration by migrate_cancel.
>
> Ivan Ren (3):
> migration: fix migrate_cancel leads live_migration thr
Few more patches to be able to MXE-build the NSIS installers,
however it is still failing due to:
https://bugs.launchpad.net/bugs/1836453
Based-on: 20190712111849.9006-1-alex.ben...@linaro.org
https://lists.gnu.org/archive/html/qemu-devel/2019-07/msg03014.html
Philippe Mathieu-Daudé (3):
tests/
>
> On Fri, 12 Jul 2019 13:05:51 +0530
> Pankaj Gupta wrote:
>
> > This patch series two fixes for coverity and a
> > transactional info removal patch.
> >
> > Pankaj Gupta (3):
> > virtio pmem: fix wrong mem region condition
> > virtio pmem: remove memdev null check
> > virtio pmem: re
On Fri, 12 Jul 2019 13:05:51 +0530
Pankaj Gupta wrote:
> This patch series two fixes for coverity and a
> transactional info removal patch.
>
> Pankaj Gupta (3):
> virtio pmem: fix wrong mem region condition
> virtio pmem: remove memdev null check
> virtio pmem: remove transational device
This patch series two fixes for coverity and a
transactional info removal patch.
Pankaj Gupta (3):
virtio pmem: fix wrong mem region condition
virtio pmem: remove memdev null check
virtio pmem: remove transational device info
hw/virtio/virtio-pmem-pci.c | 4 +---
hw/virtio/virtio-pmem.c
On 10/07/19 11:03, Daniel P. Berrangé wrote:
>> Would it be possible to make QEMU the broker? That is, how hard would it
>> be to embed a minimal DBus broker (which only takes care of connecting
>> servers
>> and clients---stuff like launching servers would be completely out of scope)?
> What wou
On Tue, Jul 09, 2019 at 02:47:32PM +0400, Marc-André Lureau wrote:
> Hi
>
> On Tue, Jul 9, 2019 at 1:02 PM Daniel P. Berrangé wrote:
> >
> > On Tue, Jul 09, 2019 at 12:26:38PM +0400, Marc-André Lureau wrote:
> > > Hi
> > >
> > > On Mon, Jul 8, 2019 at 8:04 PM Daniel P. Berrangé
> > > wrote:
> >
On Wed, Jul 10, 2019 at 10:53:10AM +0200, Paolo Bonzini wrote:
> On 08/07/19 18:04, Daniel P. Berrangé wrote:
> > The downside of using the bus daemon is that we have to spawn a new
> > instance of dbus-daemon for every QEMU VM that's running on the host,
> > which is yet more memory overhead for e
On 08/07/19 18:04, Daniel P. Berrangé wrote:
> The downside of using the bus daemon is that we have to spawn a new
> instance of dbus-daemon for every QEMU VM that's running on the host,
> which is yet more memory overhead for each VM & another process to
> manage, and yet another thing to go wrong
qemu_savevm_state_complete_precopy() iterates SaveStateEntry and does proper
tasks for migration.
For each iteration, in_postcopy and iterable_only would be checked to see
whether it should skip. Since these two conditions are not SaveStateEntry
specific, it is proper to move the check out of iter
Hi
On Tue, Jul 9, 2019 at 1:02 PM Daniel P. Berrangé wrote:
>
> On Tue, Jul 09, 2019 at 12:26:38PM +0400, Marc-André Lureau wrote:
> > Hi
> >
> > On Mon, Jul 8, 2019 at 8:04 PM Daniel P. Berrangé
> > wrote:
> > > > The D-Bus protocol can be made to work peer-to-peer, but the most
> > > > common
On Tue, Jul 09, 2019 at 12:26:38PM +0400, Marc-André Lureau wrote:
> Hi
>
> On Mon, Jul 8, 2019 at 8:04 PM Daniel P. Berrangé wrote:
> > > The D-Bus protocol can be made to work peer-to-peer, but the most
> > > common and practical way is through a bus daemon. This also has the
> > > advantage of
Hi
On Mon, Jul 8, 2019 at 8:04 PM Daniel P. Berrangé wrote:
> > The D-Bus protocol can be made to work peer-to-peer, but the most
> > common and practical way is through a bus daemon. This also has the
> > advantage of increased debuggability (you can eavesdrop on the bus and
> > introspect it).
1 - 100 of 3144 matches
Mail list logo
