Philippe Mathieu-Daudé writes:
> On 02/02/2018 03:37 PM, Markus Armbruster wrote:
>> From: Alistair Francis
>>
>> Replace a large number of the fprintf(stderr, "*\n" calls with
>> error_report(). The functions were renamed with these commands and
Eric Blake writes:
> On 02/02/2018 12:37 PM, Markus Armbruster wrote:
>> From: Alistair Francis
>>
>> Convert fprintf(stderr, ...) to use qemu_log(). Double prints in
>> target/ppc/translate.c were manually remove. A fprintf() in
>>
The IscsiAIOCB->buf field has not been used since commit
e49ab19fcaa617ad6cdfe1ac401327326b6a2552 ("block/iscsi: bump libiscsi
requirement to 1.9.0"). It used to be a linear buffer for old libiscsi
versions that didn't support scatter-gather. The minimum libiscsi
version supports scatter-gather
v2:
* It was unnecessary to avoid duplicate iscsi_schedule_bh() calls since this
function already protects against duplicate calls internally [Stefan]
Patches 1 & 2 are cleanups.
Patch 3 fixes cancellation of ioctls. Felipe showed me a trace where an acb is
cancelled and then completes
Commit d045c466d9e62b4321fadf586d024d54ddfd8bd4 ("iscsi: do not use
aio_context_acquire/release") introduced iscsilun->mutex but appears to
have overlooked iscsi_timed_check_events() when introducing the mutex.
iscsi_service() and iscsi_set_events() must be called with
iscsilun->mutex held.
iscsi_aio_cancel() does not increment the request's reference count,
causing a use-after-free when ABORT TASK finishes after the request has
already completed.
There are some additional issues with iscsi_aio_cancel():
1. Several ABORT TASKs may be sent for the same task if
iscsi_aio_cancel()
Hi,
This series failed docker-build@min-glib 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: 20180202130336.24719-1-arm...@redhat.com
Subject: [Qemu-devel] [PATCH RFC 00/21]
The patch works for me too. 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/1703795
Title:
Unable to release mouse in SDL2 mode
Status in QEMU:
New
Bug description:
Starting with
On Fri, Feb 2, 2018 at 12:24 PM, Philippe Mathieu-Daudé wrote:
> Hi Alistair,
>
> On 02/02/2018 04:38 PM, Alistair Francis wrote:
>> Ensure that the post write hook is called during reset. This allows us
>> to rely on the post write functions instead of having to call them from
Hi,
This series failed docker-build@min-glib 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: 20180202143746.204851-1-borntrae...@de.ibm.com
Subject: [Qemu-devel] [PATCH v3 0/1]
Hi,
This series failed docker-quick@centos6 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: 20180202143746.204851-1-borntrae...@de.ibm.com
Subject: [Qemu-devel] [PATCH v3 0/1]
On 02/02/2018 07:03 AM, Markus Armbruster wrote:
> Signed-off-by: Markus Armbruster
> ---
> scripts/qapi/common.py | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
Reviewed-by: Eric Blake
--
Eric Blake, Principal Software Engineer
Red
On Fri, Feb 2, 2018 at 1:49 PM, Alistair Francis
wrote:
> On Fri, Feb 2, 2018 at 12:37 PM, Alex Bennée wrote:
>>
>> Alistair Francis writes:
>>
>>> On Thu, Feb 1, 2018 at 9:13 AM, Alistair Francis
>>>
On Fri, Feb 2, 2018 at 10:16 PM, Stefan Hajnoczi wrote:
> The ioctl request cancellation code assumes that requests do not
> complete once TASK ABORT has been sent to the iSCSI target. The request
> completion callback is unconditionally invoked when TASK ABORT finishes.
>
CCing qemu-block and Berto
On 02/02/2018 06:10 AM, Wolfgang Bumiller wrote:
> Summary:
> Rate limit is effectively halved when the size of written chunks adds up to
> exceeding the quota of a slice only slightly. This is surprisingly reliable.
>
> Explanation:
> The ratelimiting code in
On Fri, Feb 2, 2018 at 12:37 PM, Alex Bennée wrote:
>
> Alistair Francis writes:
>
>> On Thu, Feb 1, 2018 at 9:13 AM, Alistair Francis
>> wrote:
>>> On Thu, Feb 1, 2018 at 4:01 AM, Alex Bennée
Hi,
This series failed build test on ppc host. Please find the details below.
Message-id: 20180202143746.204851-1-borntrae...@de.ibm.com
Subject: [Qemu-devel] [PATCH v3 0/1] respin of s390 crash information
Type: series
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoked
Commit d045c466d9e62b4321fadf586d024d54ddfd8bd4 ("iscsi: do not use
aio_context_acquire/release") introduced iscsilun->mutex but appears to
have overlooked iscsi_timed_check_events() when introducing the mutex.
iscsi_service() and iscsi_set_events() must be called with
iscsilun->mutex held.
The ioctl request cancellation code assumes that requests do not
complete once TASK ABORT has been sent to the iSCSI target. The request
completion callback is unconditionally invoked when TASK ABORT finishes.
Therefore the request completion callback is invoked twice if the
request does happen
Patches 1 & 2 are cleanups.
Patch 3 fixes cancellation of ioctls. Felipe showed me a trace where an acb is
cancelled and then completes twice. The second time around crashes QEMU.
Compile-tested only.
Felipe: Please let us know if this fixes the issue you are seeing. Thanks!
Stefan Hajnoczi
The IscsiAIOCB->buf field has not been used since commit
e49ab19fcaa617ad6cdfe1ac401327326b6a2552 ("block/iscsi: bump libiscsi
requirement to 1.9.0"). It used to be a linear buffer for old libiscsi
versions that didn't support scatter-gather. The minimum libiscsi
version supports scatter-gather
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: 20180202143746.204851-1-borntrae...@de.ibm.com
Subject: [Qemu-devel] [PATCH v3 0/1]
Hi,
This series failed docker-quick@centos6 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: 20180202130336.24719-1-arm...@redhat.com
Subject: [Qemu-devel] [PATCH RFC 00/21]
Alistair Francis writes:
> On Thu, Feb 1, 2018 at 9:13 AM, Alistair Francis
> wrote:
>> On Thu, Feb 1, 2018 at 4:01 AM, Alex Bennée wrote:
>>>
>>> Alistair Francis writes:
>>>
Hi Thomas,
On 02/02/2018 05:15 AM, Thomas Huth wrote:
> When compiling with NVRAM_PRINTF enabled, gcc currently bails out with:
>
> CC hw/timer/m48t59.o
> CC hw/timer/m48t59-isa.o
> hw/timer/m48t59.c: In function ‘NVRAM_writeb’:
> hw/timer/m48t59.c:460:5: error: format ‘%x’ expects
Hi Alistair,
On 02/02/2018 04:38 PM, Alistair Francis wrote:
> Ensure that the post write hook is called during reset. This allows us
> to rely on the post write functions instead of having to call them from
> the reset() function.
This makes sens. Can you add a comment about this new behavior
On 02/02/2018 03:37 PM, Markus Armbruster wrote:
> From: Alistair Francis
>
> Replace a large number of the fprintf(stderr, "*\n" calls with
> error_report(). The functions were renamed with these commands and then
> compiler issues where manually fixed.
>
> find
On 02/02/2018 07:03 AM, Markus Armbruster wrote:
> Error messages print absolute filenames of included files even gave a
s/even gave/even when given/
> relative one on the command line:
>
> PYTHONPATH=scripts python -B tests/qapi-schema/test-qapi.py
> tests/qapi-schema/include-cycle.json
On 02/02/2018 03:37 PM, Markus Armbruster wrote:
> This is my attempt to salvage a good part of Alistair's error
> reporting cleanup series
>
> [PATCH v6 00/29] Remove some of the fprintf(stderr, "*
>
> Continue on improving QEMUs logging/error messages by removing more
>
Hi,
This series failed build test on s390x host. Please find the details below.
Type: series
Message-id: 20180202130336.24719-1-arm...@redhat.com
Subject: [Qemu-devel] [PATCH RFC 00/21] Modularize generated QAPI code
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoked under
Hi,
This series failed build test on s390x host. Please find the details below.
Type: series
Message-id: 20180202143746.204851-1-borntrae...@de.ibm.com
Subject: [Qemu-devel] [PATCH v3 0/1] respin of s390 crash information
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoked
On 02/02/2018 12:37 PM, Markus Armbruster wrote:
> From: Alistair Francis
>
> Convert fprintf(stderr, ...) to use qemu_log(). Double prints in
> target/ppc/translate.c were manually remove. A fprintf() in
> target/sh4/translate.c was kept as it's inside a #if 0. The
Hi,
This series failed build test on ppc host. Please find the details below.
Subject: [Qemu-devel] [PATCH RFC 00/21] Modularize generated QAPI code
Type: series
Message-id: 20180202130336.24719-1-arm...@redhat.com
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoked under the
On Fri, Feb 2, 2018 at 10:37 AM, Markus Armbruster wrote:
> This is my attempt to salvage a good part of Alistair's error
> reporting cleanup series
>
> [PATCH v6 00/29] Remove some of the fprintf(stderr, "*
>
> Continue on improving QEMUs logging/error messages by
Ensure that the post write hook is called during reset. This allows us
to rely on the post write functions instead of having to call them from
the reset() function.
Signed-off-by: Alistair Francis
---
hw/core/register.c | 8
1 file changed, 8 insertions(+)
On 02/02/2018 07:03 AM, Markus Armbruster wrote:
> A massive number of objects depends on QAPI-generated headers. In my
> "build everything" tree, it's roughly 4500 out of 4800. This is
> particularly annoying when only some of the generated files change,
> say for a doc fix.
>
> Improve
On Tue, Jan 30, 2018 at 08:09:19PM +0800, Wei Wang wrote:
> On 01/26/2018 10:44 PM, Stefan Hajnoczi wrote:
> > On Thu, Jan 25, 2018 at 06:19:13PM +0800, Wei Wang wrote:
> > > On 01/24/2018 07:40 PM, Stefan Hajnoczi wrote:
> > > > On Tue, Jan 23, 2018 at 09:06:49PM +0800, Wei Wang wrote:
> > > > >
This should primarily go to the qemu devel list. I've Cc'd it, but
reposting would be safer, thanks.
2018-02-02 10:21+0530, P J P:
> From: Prasad J Pandit
>
> When updating message signalled interrupt(MSI) route in routine
> kvm_irqchip_update_msi_route, device
On 02/02/2018 12:37 PM, Markus Armbruster wrote:
> From: Alistair Francis
>
> Replace a large number of the fprintf(stderr, "*\n" calls with
> error_report(). The functions were renamed with these commands and then
> compiler issues where manually fixed.
>
>
>
I can confirm that the patch from comment #9 appears to fix the original
problem.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1703795
Title:
Unable to release mouse in SDL2 mode
Status in QEMU:
On 02/02/2018 07:03 AM, Markus Armbruster wrote:
> Signed-off-by: Markus Armbruster
> ---
> scripts/qapi-gen.py| 52 +++-
> scripts/qapi/common.py | 54
> --
> 2 files changed, 51
On 02/02/2018 07:03 AM, Markus Armbruster wrote:
> Whenever qapi-schema.json changes, we run six programs eleven times to
> update eleven files. This is silly. Replace the six programs by a
> single program that spits out all eleven files.
Yay, about time!
One program, but still invoked
From: Alistair Francis
Replace a large number of the fprintf(stderr, "*\n" calls with
error_report(). The functions were renamed with these commands and then
compiler issues where manually fixed.
find ./* -type f -exec sed -i \
'N;N;N;N;N;N;N;N;N;N;N;N;
From: Alistair Francis
Replace a large number of the fprintf(stderr, "*\n" calls with
error_report(). The functions were renamed with these commands and then
compiler issues where manually fixed.
find ./* -type f -exec sed -i \
'N;N;N;N;N;N;N;N;N;N;N;N;
From: Alistair Francis
Replace a large number of the fprintf(stderr, "*\n" calls with
error_report(). The functions were renamed with these commands and then
compiler issues where manually fixed.
find ./* -type f -exec sed -i \
'N;N;N;N;N;N;N;N;N;N;N;N;
From: Alistair Francis
Replace a large number of the fprintf(stderr, "*\n" calls with
error_report(). The functions were renamed with these commands and then
compiler issues where manually fixed.
find ./* -type f -exec sed -i \
'N;N;N;N;N;N;N;N;N;N;N;N;
From: Alistair Francis
Replace a large number of the fprintf(stderr, "*\n" calls with
error_report(). The functions were renamed with these commands and then
compiler issues where manually fixed.
find ./* -type f -exec sed -i \
'N;N;N;N;N;N;N;N;N;N;N;N;
From: Alistair Francis
Replace a large number of the fprintf(stderr, "*\n" calls with
error_report(). The functions were renamed with these commands and then
compiler issues where manually fixed.
find ./* -type f -exec sed -i \
'N;N;N;N;N;N;N;N;N;N;N;N;
Signed-off-by: Daniel P. Berrangé
---
.mailmap | 4
1 file changed, 4 insertions(+)
diff --git a/.mailmap b/.mailmap
index ee81ac801e..cf689b9ec9 100644
--- a/.mailmap
+++ b/.mailmap
@@ -18,3 +18,7 @@ malc malc
are available in the git repository at:
>
> git://git.kraxel.org/qemu tags/vga-20180202-pull-request
>
> for you to fetch changes up to 34e304e97576a9e17680c868c00ff524a981007b:
>
> virtio-gpu: disallow vIOMMU (2018-02-02 08:53:22 +0100)
>
> -
From: Alistair Francis
Convert fprintf(stderr, ...) to use qemu_log(). Double prints in
target/ppc/translate.c were manually remove. A fprintf() in
target/sh4/translate.c was kept as it's inside a #if 0. The #if 0 and
fflush() was removed around the unimplemented log
From: Alistair Francis
Replace a large number of the fprintf(stderr, "*\n" calls with
error_report(). The functions were renamed with these commands and then
compiler issues where manually fixed.
find ./* -type f -exec sed -i \
'N;N;N;N;N;N;N;N;N;N;N;N;
the git repository at:
>
> git://git.kraxel.org/qemu tags/ui-20180202-pull-request
>
> for you to fetch changes up to 627ebec208a8809818589e17f4fce55a59420ad2:
>
> ui: correctly advance output buffer when writing SAS
From: Alistair Francis
Replace a large number of the fprintf(stderr, "*\n" calls with
error_report(). The functions were renamed with these commands and then
compiler issues where manually fixed.
find ./* -type f -exec sed -i \
'N;N;N;N;N;N;N;N;N;N;N;N;
From: Alistair Francis
Replace a large number of the fprintf(stderr, "*\n" calls with
error_report(). The functions were renamed with these commands and then
compiler issues where manually fixed.
find ./* -type f -exec sed -i \
'N;N;N;N;N;N;N;N;N;N;N;N;
From: Alistair Francis
Apparently we don't use __MSC_VER as a compiler anymore and we always
require a C99 compiler (which means we always have __func__) so we don't
need a special AUDIO_FUNC macro. We can just replace AUDIO_FUNC with
__func__ instead.
Checkpatch
On Fri, Feb 02, 2018 at 05:23:59PM +, Dr. David Alan Gilbert wrote:
> * Eduardo Habkost (ehabk...@redhat.com) wrote:
> > (CCing qemu-devel)
> >
> > On Fri, Feb 02, 2018 at 09:21:59AM -0500, Luiz Capitulino wrote:
> > > On Fri, 2 Feb 2018 14:19:38 +
> > > Daniel P. Berrangé
From: Alistair Francis
Replace a large number of the fprintf(stderr, "*\n" calls with
error_report(). The functions were renamed with these commands and then
compiler issues where manually fixed.
find ./* -type f -exec sed -i \
'N;N;N;N;N;N;N;N;N;N;N;N;
From: Alistair Francis
Replace a large number of the fprintf(stderr, "*\n" calls with
error_report(). The functions were renamed with these commands and then
compiler issues where manually fixed.
find ./* -type f -exec sed -i \
'N;N;N;N;N;N;N;N;N;N;N;N;
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: 20180202130336.24719-1-arm...@redhat.com
Subject: [Qemu-devel] [PATCH RFC 00/21]
From: Alistair Francis
Replace a large number of the fprintf(stderr, "*\n" calls with
error_report(). The functions were renamed with these commands and then
compiler issues where manually fixed.
find ./* -type f -exec sed -i \
'N;N;N;N;N;N;N;N;N;N;N;N;
This is my attempt to salvage a good part of Alistair's error
reporting cleanup series
[PATCH v6 00/29] Remove some of the fprintf(stderr, "*
Continue on improving QEMUs logging/error messages by removing more
fprintf()'s.
Unfortunatley my Coccinelle skills aren't that great so
Public bug reported:
I was installing MS-Dos 6.22 + Windows 3.11 in preparation for running
Microsoft Bob, and noticed that when they try to perform a reboot, they
just get stuck. The console cursor stays flashing on/off, but the DOS
prompt no longer responds to input.
It is fairly easy to
From: Alistair Francis
Replace a large number of the fprintf(stderr, "*\n" calls with
error_report(). The functions were renamed with these commands and then
compiler issues where manually fixed.
find ./* -type f -exec sed -i \
'N;N;N;N;N;N;N;N;N;N;N;N;
gt; > into staging (2018-01-30 09:47:51 +)
> >
> > are available in the git repository at:
> >
> > git://git.kraxel.org/qemu tags/ui-20180202-pull-request
> >
> > for you to fetch changes up to 627ebec208a8809818589e17f4fce55a59420ad2:
> >
> &g
The purpose of virtio-9p-test is to test the virtio-9p device, especially
the 9p server state machine. We don't really care what fsdev backend we're
using. Moreover, if we want to be able to test the flush request or a
device reset with in-flights I/O, it is close to impossible to achieve
with a
On Thu, Feb 01, 2018 at 04:42:05PM -0800, Alistair Francis wrote:
> As cpu_type is not a user visible string let's convert the
> valid_cpu_types to compare against cpu_model instead. This way we have a
> user friendly string to report back.
>
> Once we have a cpu_type to cpu_model conversion this
Summary:
Rate limit is effectively halved when the size of written chunks adds up to
exceeding the quota of a slice only slightly. This is surprisingly reliable.
Explanation:
The ratelimiting code in include/qemu/ratelimit.h currently uses slices with
quotas. Finishing up the quota for one slice
On 26 January 2018 at 15:44, Philippe Mathieu-Daudé wrote:
> On 01/26/2018 11:33 AM, Peter Maydell wrote:
>> On 26 January 2018 at 14:29, Philippe Mathieu-Daudé wrote:
>>> Why not use arm_any_initfn() here?
>>
>> That function (and the 'any' cpu) are
It doesn't really makes sense to hide the request tag from the test
functions. It prevents to test the 9p server behavior when passed
a wrong tag (ie, still in use or different from P9_NOTAG for a
version request). Also the spec says that a tag is reusable as soon
as the corresponding request was
If netdev_add tap,id=net0,...,vhost=on failed in net_init_tap_one(),
the followed up device_add virtio-net-pci,netdev=net0 will fail
too, prints:
TUNSETOFFLOAD ioctl() failed: Bad file descriptor TUNSETOFFLOAD
ioctl() failed: Bad file descriptor
The reason is that the fd of tap is closed
On Wed, Jan 31, 2018 at 6:06 PM, Marc-André Lureau
wrote:
> Hi
>
> On Wed, Jan 31, 2018 at 6:33 AM, Fam Zheng wrote:
>> git-publish [1] is a convenient tool to send patches and has been
>> popular among QEMU developers. Recently it has been made
On 2017-12-04 19:25, Max Reitz wrote:
> On 2017-12-04 17:37, Alberto Garcia wrote:
>> On Mon 20 Nov 2017 09:10:00 PM CET, Max Reitz wrote:
>>> -static void blkdebug_refresh_filename(BlockDriverState *bs, QDict *options)
>>> +static void blkdebug_refresh_filename(BlockDriverState *bs)
>>> {
>>>
On 02/02/2018 07:03 AM, Markus Armbruster wrote:
> The next commit will introduce a common driver program for all
> generators. The generators need to be modules for that. qapi2texi.py
> already is. Make the other generators follow suit.
>
> The changes are actually trivial. Obvious in the
This patch is the s390 implementation of guest crash information,
similar to commit d187e08dc4 ("i386/cpu: add crash-information QOM
property") and the related commits. We will detect several crash
reasons, with the "disabled wait" being the most important one, since
this is used by all s390
On 01/31/2018 02:16 PM, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert"
>
> The boot block used in the migration test is currently only
> shipped as a hex (with the source in the git commit message),
> change this to actually include the source.
>
> A
On Fri, Feb 02, 2018 at 02:03:15PM +0100, Markus Armbruster wrote:
> Our qapi-schema.json is composed of modules connected by include
> directives, but the generated code is monolithic all the same: one
> qapi-types.h with all the types, one qapi-visit.h with all the
> visitors, and so forth.
* Eduardo Habkost (ehabk...@redhat.com) wrote:
> (CCing qemu-devel)
>
> On Fri, Feb 02, 2018 at 09:21:59AM -0500, Luiz Capitulino wrote:
> > On Fri, 2 Feb 2018 14:19:38 +
> > Daniel P. Berrangé wrote:
> > > On Fri, Feb 02, 2018 at 12:15:54PM -0200, Eduardo Habkost wrote:
The following changes since commit b05631954d6dfe93340d516660397e2c1a2a5dd6:
Merge remote-tracking branch 'remotes/rth/tags/pull-hppa-20180131' into
staging (2018-01-31 15:50:29 +)
are available in the git repository at:
https://github.com/gkurz/qemu.git tags/for-upstream
for you to
On 2 February 2018 at 16:19, Greg Kurz wrote:
> The following changes since commit b05631954d6dfe93340d516660397e2c1a2a5dd6:
>
> Merge remote-tracking branch 'remotes/rth/tags/pull-hppa-20180131' into
> staging (2018-01-31 15:50:29 +)
>
> are available in the git repository
On Thu, Feb 01, 2018 at 06:46:46PM -0200, Eduardo Habkost wrote:
> On Tue, Jan 16, 2018 at 01:42:14PM +, Daniel P. Berrange wrote:
> > From: Miika S
> >
> > keycodemapdb updated to add the QKeyCodes muhenkan and katakanahiragana
> >
> > Signed-off-by: Miika S
On 2018-02-02 17:18, Eric Blake wrote:
> On 02/02/2018 10:07 AM, Vladimir Sementsov-Ogievskiy wrote:
>> To maintain load/store disabled bitmap there is new approach:
>>
>> - deprecate @autoload flag of block-dirty-bitmap-add, make it ignored
>> - store enabled bitmaps as "auto" to qcow2
>> -
This patch - originally from Jing Liu - was still on my disk and
somehow dropped of my attention. Here is a fixed up version.
It probably still needs some review and polish.
One open aspect is migration. Right now QEMU switches from crashed
back into running state after migration (even without
No good reasons to do this outside of v9fs_device_realize_common().
Signed-off-by: Greg Kurz
Reviewed-by: Stefano Stabellini
---
hw/9pfs/9p.c | 6 +-
hw/9pfs/9p.h | 10 ++
hw/9pfs/virtio-9p-device.c | 8 ++--
From: Peter Xu
virtio-gpu has special code path that bypassed vIOMMU protection. So
for now let's disable iommu_platform for the device until we fully
support that (if needed).
After the patch, both virtio-vga and virtio-gpu won't allow to boot with
iommu_platform parameter
On 02/02/2018 09:25 AM, Eduardo Habkost wrote:
>>> Markus, Eric: from the QAPI point of view, is it OK to remove
>>> fields between QEMU versions, as long as we follow our
>>> deprecation policy?
>>
>> I would expect that to not be OK. A fully backwards compatible way to
>> deal with this would
02.02.2018 19:18, Eric Blake wrote:
On 02/02/2018 10:07 AM, Vladimir Sementsov-Ogievskiy wrote:
To maintain load/store disabled bitmap there is new approach:
- deprecate @autoload flag of block-dirty-bitmap-add, make it ignored
- store enabled bitmaps as "auto" to qcow2
- store disabled
On Thu, Feb 1, 2018 at 6:46 PM, Stefan Hajnoczi wrote:
> On Wed, Jan 31, 2018 at 11:06:05AM +0100, Marc-André Lureau wrote:
>> Hi
>>
>> On Wed, Jan 31, 2018 at 6:33 AM, Fam Zheng wrote:
>> > git-publish [1] is a convenient tool to send patches and has been
Signed-off-by: Greg Kurz
Reviewed-by: Eric Blake
Reviewed-by: Stefan Hajnoczi
---
tests/virtio-9p-test.c | 31 +--
1 file changed, 21 insertions(+), 10 deletions(-)
diff --git a/tests/virtio-9p-test.c
On 2018-02-02 14:48, Vladimir Sementsov-Ogievskiy wrote:
> 02.02.2018 16:00, Max Reitz wrote:
>> On 2018-02-02 13:07, Vladimir Sementsov-Ogievskiy wrote:
>>> 29.01.2018 18:34, Max Reitz wrote:
On 2017-11-30 17:47, Vladimir Sementsov-Ogievskiy wrote:
> Signed-off-by: Vladimir
are available in the git repository at:
>
> git://git.kraxel.org/qemu tags/audio-20180202-pull-request
>
> for you to fetch changes up to 8ec660b80ed511fa333679e38bf0cf714799d6fa:
>
> hw/audio/sb16.c: change dolog() to qem
On 02/02/2018 05:10 AM, Gerd Hoffmann wrote:
> Not used any more, delete it.
>
> Signed-off-by: Gerd Hoffmann
> ---
> vl.c | 2 --
> 1 file changed, 2 deletions(-)
Reviewed-by: Eric Blake
--
Eric Blake, Principal Software Engineer
Red Hat, Inc.
On 02/02/2018 10:07 AM, Vladimir Sementsov-Ogievskiy wrote:
> To maintain load/store disabled bitmap there is new approach:
>
> - deprecate @autoload flag of block-dirty-bitmap-add, make it ignored
> - store enabled bitmaps as "auto" to qcow2
> - store disabled bitmaps without "auto" flag to
On 02/02/2018 07:03 AM, Markus Armbruster wrote:
> In preparation of the next commit, which will turn the generators into
> modules. These global variables will become local to main() then.
>
> Signed-off-by: Markus Armbruster
> ---
Reviewed-by: Eric Blake
On Thu, 1 Feb 2018 19:10:06 -0500
Paolo Bonzini wrote:
> On 01/02/2018 19:00, Alex Williamson wrote:
> > On Tue, 16 Jan 2018 15:16:59 +0100
> > Paolo Bonzini wrote:
> >
> >> From: Marc-André Lureau
> >>
> >> Fixes leaks
In order to test request cancellation, we will need to send multiple
requests and wait for the associated replies. Since we poll the ISR
to know if a request completed, we may have several replies to parse
when we detect ISR was set to 1.
This patch moves the waiting out of the reply parsing
When a 9p request is flushed (ie, cancelled) by the guest, the device
is expected to simply mark the request as used, without sending a 9p
reply (ie, without writing anything into the used buffer).
To be able to test this, we need access to the length written by the
device into the used
22.01.2018 22:56, John Snow wrote:
On 01/22/2018 02:51 PM, Eric Blake wrote:
On 01/22/2018 03:09 AM, Vladimir Sementsov-Ogievskiy wrote:
I have to admit exposing this interface still makes me nervous, but :)
Mechanically correct, and with suggesting phrasing changes:
Reviewed-by: John Snow
Public bug reported:
In a docker container created from an aarch64 image, injects
qemu-aarch64-static (in /usr/bin)
run ps/top cmd inside this container
reports "qemu: uncaught target signal 11 (Segmentation fault)"
Tried qemu-aarch64-static from fedora 27 / ubuntu artful / debian
On Thu, Feb 01, 2018 at 02:24:15PM +0200, Marcel Apfelbaum wrote:
> Hi Peter,
>
> On 01/02/2018 13:20, Peter Xu wrote:
> > In the past, we prioritized IOMMU migration so that we have such a
> > priority order:
> >
> > IOMMU > PCI Devices
> >
> > When migrating a guest with both vIOMMU and
1 - 100 of 243 matches
Mail list logo