On 7/5/19 6:04 PM, Alex Bennée wrote:
> We never shipped the reference data in the source tree because it was
> quite big (64M). As a result the only option is to generate it
> locally. Although we have a rule to generate the reference file we
> missed the dependency and location changes, probably
On 7/10/19 1:43 AM, Carlo Marcelo Arenas Belón wrote:
> 9b9c37c364 ("tcg-sparc: Assume v9 cpu always, i.e. force v8plus in
> 32-bit mode.", 2012-09-21) removed the need for this variable and
> most of the references to it, but this one.
>
> Remove defunct code, no effect or functionality change ex
On 08/07/19 09:24, Marc-André Lureau wrote:
> +
> +dstaddr = g_strsplit(g_test_dbus_get_bus_address(dstbus), ",", 2);
> +dst_qemu_args =
> +g_strdup_printf("-object dbus-vmstate,id=dv,addr=%s -incoming %s",
> +dstaddr[0], uri);
> +
Stupid question: what does
Patchew URL:
https://patchew.org/QEMU/20190710060621.16430-1-bhar...@linux.ibm.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20190710060621.16430-1-bhar...@linux.ibm.com
Type: series
Subject: [Qemu-devel] [PATCH v0] ppc/spapr
A pseries guest can be run as a secure guest on Ultravisor-enabled
POWER platforms. When such a secure guest is reset, we need to
release/reset a few resources both on ultravisor and hypervisor side.
This is achieved by invoking this new ioctl KVM_PPC_SVM_OFF from the
machine reset path.
As part o
On 09/07/19 16:39, Peter Maydell wrote:
> Reported-by: Russell King
> Signed-off-by: Peter Maydell
> ---
> I think this is correct, and it makes the "rtc clock should
> not stay still across a save/reload" work, but I feel like
> there might be some subtlety I've missed here. Review
> definitely
Here are two trivial function cleanup.
BTW, I didn't test them since TPS == HPS. How could I setup a guest with
TPS != HPS?
Wei Yang (2):
migration/postcopy: reduce one operation to calculate fixup_start_addr
migration/postcopy: do_fixup is true when host_offset is non-zero
migration/ram.c
Use the same way for run_end to calculate run_start, which saves one
operation.
Signed-off-by: Wei Yang
---
migration/ram.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/migration/ram.c b/migration/ram.c
index 410e0f89fe..c4dc36e525 100644
--- a/migration/ram.c
+
This means it is not necessary to spare an extra variable to hold this
condition. Use host_offset directly is fine.
Signed-off-by: Wei Yang
---
migration/ram.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/migration/ram.c b/migration/ram.c
index c4dc36e525..b0ca0059c4 1
John Snow writes:
> Depending on what a user is trying to accomplish, there might be a few
> bitmap cleanup actions that occur when an operation is finished that
> could be useful.
>
> I am proposing three:
> - NEVER: The bitmap is never synchronized against what was copied.
> - ALWAYS: The bitma
John Snow writes:
> On 7/9/19 7:25 PM, John Snow wrote:
>> drive-backup and blockdev-backup have an awful lot of things in common
>> that are the same. Let's fix that.
>>
>> I don't deduplicate 'target', because the semantics actually did change
>> between each structure. Leave that one alone so
"Kővágó, Zoltán" writes:
> Audio functions no longer access glob_audio_state, instead they get an
> AudioState as a parameter. This is required in order to support
> multiple backends.
>
> glob_audio_state is also gone, and replaced with a tailq so we can store
> more than one states.
>
> Signed
On 2019/7/10 上午11:36, Longpeng (Mike) wrote:
在 2019/7/10 11:25, Jason Wang 写道:
On 2019/7/8 下午5:47, Dr. David Alan Gilbert wrote:
* longpeng (longpe...@huawei.com) wrote:
Hi guys,
We found a qemu core in our testing environment, the assertion
'assert(bus->irq_count[i] == 0)' in pcibus_reset()
On 2019/7/4 下午4:36, Zhang Chen wrote:
From: Zhang Chen
This patch to fix the origin "char *data" menory leak, code style issue
and add necessary check here.
Reported-by: Coverity (CID 1402785)
Signed-off-by: Zhang Chen
---
net/colo-compare.c | 28 +---
1 file chan
在 2019/7/10 11:25, Jason Wang 写道:
>
> On 2019/7/8 下午5:47, Dr. David Alan Gilbert wrote:
>> * longpeng (longpe...@huawei.com) wrote:
>>> Hi guys,
>>>
>>> We found a qemu core in our testing environment, the assertion
>>> 'assert(bus->irq_count[i] == 0)' in pcibus_reset() was triggered and
>>> the b
On 2019/7/8 下午5:47, Dr. David Alan Gilbert wrote:
* longpeng (longpe...@huawei.com) wrote:
Hi guys,
We found a qemu core in our testing environment, the assertion
'assert(bus->irq_count[i] == 0)' in pcibus_reset() was triggered and
the bus->irq_count[i] is '-1'.
Through analysis, it was happ
On Tue, Jul 9, 2019 at 11:32 AM Max Reitz wrote:
>
> On 09.07.19 15:09, Stefano Garzarella wrote:
> > On Tue, Jul 09, 2019 at 08:55:19AM -0400, Jason Dillaman wrote:
> >> On Tue, Jul 9, 2019 at 5:45 AM Max Reitz wrote:
> >>>
> >>> On 09.07.19 10:55, Max Reitz wrote:
> On 09.07.19 05:08, Jaso
On 7/9/19 7:25 PM, John Snow wrote:
> drive-backup and blockdev-backup have an awful lot of things in common
> that are the same. Let's fix that.
>
> I don't deduplicate 'target', because the semantics actually did change
> between each structure. Leave that one alone so it can be documented
>
This test needs support for non-bitmap backups and missing or
unspecified bitmap sync modes, so rewrite the helpers to be a little
more generic.
Signed-off-by: John Snow
---
tests/qemu-iotests/257 | 46 +
tests/qemu-iotests/257.out | 192 ++---
2 file
Accept bitmaps and sync policies for the other backup modes.
This allows us to do things like create a bitmap synced to a full backup
without a transaction, or start a resumable backup process.
Some combinations don't make sense, though:
- NEVER policy combined with any non-BITMAP mode doesn't do
Signed-off-by: John Snow
---
tests/qemu-iotests/257 | 31 +
tests/qemu-iotests/257.out | 3089
2 files changed, 3120 insertions(+)
diff --git a/tests/qemu-iotests/257 b/tests/qemu-iotests/257
index de8707cb19..8de1c4da19 100755
--- a/tests/qemu-iotests/
Represent a bitmap with an object that we can mark and clear bits in.
This makes it easier to manage partial writes when we don't write a
full group's worth of patterns before an error.
Signed-off-by: John Snow
---
tests/qemu-iotests/257 | 125 +
1 file ch
Just kidding, this is easier to manage with a full class instead of a
namedtuple.
Signed-off-by: John Snow
---
tests/qemu-iotests/257 | 58 +++---
1 file changed, 32 insertions(+), 26 deletions(-)
diff --git a/tests/qemu-iotests/257 b/tests/qemu-iotests/257
i
Signed-off-by: John Snow
---
tests/qemu-iotests/257 | 69 +++
tests/qemu-iotests/257.out | 85 ++
2 files changed, 154 insertions(+)
diff --git a/tests/qemu-iotests/257 b/tests/qemu-iotests/257
index 2eb4f26c28..de8707cb19 10075
Requires: <20190709232550.10724-1-js...@redhat.com>
[PATCH v4 00/18] bitmaps: introduce 'bitmap' sync mode
This follows the previous series which adds the 'bitmap' sync mode
and uses it to add interactions with bitmaps to the 'full' and 'top'
modes to blockdev-backup and drive-backup.
Why?
on-su
The way bitmap backups work is by starting at 75% if it needs
to copy just 25% of the disk.
The way sync=top currently works, however, is to start at 0% and then
never update the progress if it doesn't copy a region. If it needs to
copy 25% of the disk, we'll finish at 25%.
Update the progress wh
This is nicer to do in the unified QMP interface that we have now,
because it lets us use the right terminology back at the user.
Signed-off-by: John Snow
---
block/backup.c | 13 -
blockdev.c | 10 ++
2 files changed, 14 insertions(+), 9 deletions(-)
diff --git a/block/
9b9c37c364 ("tcg-sparc: Assume v9 cpu always, i.e. force v8plus in
32-bit mode.", 2012-09-21) removed the need for this variable and
most of the references to it, but this one.
Remove defunct code, no effect or functionality change expected.
Signed-off-by: Carlo Marcelo Arenas Belón
---
configu
Signed-off-by: John Snow
---
tests/qemu-iotests/257 | 416 +++
tests/qemu-iotests/257.out | 2247
tests/qemu-iotests/group |1 +
3 files changed, 2664 insertions(+)
create mode 100755 tests/qemu-iotests/257
create mode 100644 tests/qemu-iotest
This simplifies some interface matters; namely the initialization and
(later) merging the manifest back into the sync_bitmap if it was
provided.
Signed-off-by: John Snow
---
block/backup.c | 81 ++
1 file changed, 42 insertions(+), 39 deletions(-)
Use "FilePaths" instead of "FilePath" to request multiple files be
cleaned up after we leave that object's scope.
This is not crucial; but it saves a little typing.
Signed-off-by: John Snow
Reviewed-by: Max Reitz
---
tests/qemu-iotests/iotests.py | 34 --
1 file
Patchew URL:
https://patchew.org/QEMU/20190709194330.837-1-marcandre.lur...@redhat.com/
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
This adds an "always" policy for bitmap synchronization. Regardless of if
the job succeeds or fails, the bitmap is *always* synchronized. This means
that for backups that fail part-way through, the bitmap retains a record of
which sectors need to be copied out to accomplish a new backup using the
o
With the "never" sync policy, we actually can utilize readonly bitmaps
now. Loosen the check at the QMP level, and tighten it based on
provided arguments down at the job creation level instead.
Signed-off-by: John Snow
Reviewed-by: Max Reitz
---
block/backup.c | 6 ++
blockdev.c | 2 +-
Signed-off-by: John Snow
Reviewed-by: Max Reitz
---
blockdev.c | 65 +-
1 file changed, 6 insertions(+), 59 deletions(-)
diff --git a/blockdev.c b/blockdev.c
index 5bc8ecd087..77365d8166 100644
--- a/blockdev.c
+++ b/blockdev.c
@@ -3624,78 +36
Create a common core that comprises the actual meat of what the backup API
boundary needs to do, and then switch drive-backup to use it.
Signed-off-by: John Snow
Reviewed-by: Max Reitz
---
blockdev.c | 122 +
1 file changed, 67 insertions(+),
I'm surprised it didn't come up sooner, but sometimes we have a +busy
bitmap as a source. This is dangerous from the QMP API, but if we are
the owner that marked the bitmap busy, it's safe to merge it using it as
a read only source.
It is not safe in the general case to allow users to read from in
Depending on what a user is trying to accomplish, there might be a few
bitmap cleanup actions that occur when an operation is finished that
could be useful.
I am proposing three:
- NEVER: The bitmap is never synchronized against what was copied.
- ALWAYS: The bitmap is always synchronized, even on
We don't need or want a new sync mode for simple differences in
semantics. Create a new mode simply named "BITMAP" that is designed to
make use of the new Bitmap Sync Mode field.
Because the only bitmap sync mode is 'on-success', this adds no new
functionality to the backup job (yet). The old inc
Seems that it comes up enough.
Signed-off-by: John Snow
Reviewed-by: Max Reitz
---
tests/qemu-iotests/040| 6 +-
tests/qemu-iotests/093| 6 ++
tests/qemu-iotests/139| 7 ++-
tests/qemu-iotests/238| 5 +
tests/qemu-iotests/iotests.py | 4
5 fi
Because the new-style python tests don't use the iotests.main() test
launcher, we don't turn on the debugger logging for these scripts
when invoked via ./check -d.
Refactor the launcher shim into new and old style shims so that they
share environmental configuration.
Two cleanup notes: debug was
This adds a "never" policy for bitmap synchronization. Regardless of if
the job succeeds or fails, we never update the bitmap. This can be used
to perform differential backups, or simply to avoid the job modifying a
bitmap.
Signed-off-by: John Snow
Reviewed-by: Max Reitz
---
block/backup.c
Add a public interface for get. While we're at it,
rename "bdrv_get_dirty_bitmap_locked" to "bdrv_dirty_bitmap_get_locked".
(There are more functions to rename to the bdrv_dirty_bitmap_VERB form,
but they will wait until the conclusion of this series.)
Signed-off-by: John Snow
Reviewed-by: Max R
run_job can cancel pending jobs to simulate failure. This lets us use
the pending callback to issue test commands while the job is open, but
then still have the job fail in the end.
Signed-off-by: John Snow
Reviewed-by: Max Reitz
---
tests/qemu-iotests/iotests.py | 22 --
1
drive-backup and blockdev-backup have an awful lot of things in common
that are the same. Let's fix that.
I don't deduplicate 'target', because the semantics actually did change
between each structure. Leave that one alone so it can be documented
separately.
Signed-off-by: John Snow
Reviewed-by:
This series adds a new "BITMAP" sync mode that is meant to replace the
existing "INCREMENTAL" sync mode.
This mode can have its behavior modified by issuing any of three bitmap sync
modes, passed as arguments to the job.
The three bitmap sync modes are:
- ON-SUCCESS: This is an alias for the old
Nobody calls the function like this currently, but we neither prohibit
or cope with this behavior. I decided to make the function cope with it.
Signed-off-by: John Snow
Reviewed-by: Max Reitz
---
util/hbitmap.c | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/u
Signed-off-by: John Snow
Reviewed-by: Max Reitz
---
util/hbitmap.c | 36 +++-
1 file changed, 35 insertions(+), 1 deletion(-)
diff --git a/util/hbitmap.c b/util/hbitmap.c
index 3b6acae42b..306bc4876d 100644
--- a/util/hbitmap.c
+++ b/util/hbitmap.c
@@ -777,7 +777
On 7/9/19 2:49 PM, Max Reitz wrote:
> On 05.07.19 22:16, John Snow wrote:
>> Signed-off-by: John Snow
>> ---
>> tests/qemu-iotests/257 | 409 +++
>> tests/qemu-iotests/257.out | 2199
>> tests/qemu-iotests/group |1 +
>> 3 files changed, 2609
On 7/8/19 9:23 AM, Christian Borntraeger wrote:
On 08.07.19 14:54, Cornelia Huck wrote:
According to the comment, the bits are supposed to accumulate.
Reported-by: Stefan Weil
Fixes: 5d1abf234462 ("s390x/pci: enforce zPCI state checking")
Signed-off-by: Cornelia Huck
This patch does not c
Patchew URL:
https://patchew.org/QEMU/cover.1562695780.git.dirty.ice...@gmail.com/
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/bash
ma
Patchew URL:
https://patchew.org/QEMU/cover.1562695780.git.dirty.ice...@gmail.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: cover.1562695780.git.dirty.ice...@gmail.com
Subject: [Qemu-devel] [PATCH 00/11] Multiple
On Jul 3, 2019, at 11:57 AM, Michael S. Tsirkin
mailto:m...@redhat.com>> wrote:
On Tue, Jul 02, 2019 at 10:08:54PM +, Raphael Norwitz wrote:
For background I am trying to work around a ram slot limit imposed by the
vhost-user protocol. We are having trouble reconciling the comment here: htt
Hi Philippe.
I am working on it.
On Tue, Jul 2, 2019 at 6:55 PM Philippe Mathieu-Daudé
wrote:
> Hi Michael,
>
> On 6/28/19 2:01 PM, Michael Rolnik wrote:
> > This series of patches adds 8bit AVR cores to QEMU.
> > All instruction, except BREAK/DES/SPM/SPMX, are implemented. Not fully
> tested y
This includes:
- TCG translations for each instruction
Signed-off-by: Michael Rolnik
---
target/avr/translate.c | 2888
1 file changed, 2888 insertions(+)
create mode 100644 target/avr/translate.c
diff --git a/target/avr/translate.c b/target/avr/transla
From: Sarah Harris
A simple board setup that configures an AVR CPU to run a given firmware image.
This is all that's useful to implement without peripheral emulation as AVR CPUs
include a lot of on-board peripherals.
Signed-off-by: Michael Rolnik
---
hw/Kconfig | 1 +
hw/avr/Kconf
From: Sarah Harris
These were designed to facilitate testing but should provide enough function to
be useful in other contexts.
Only a subset of the functions of each peripheral is implemented, mainly due to
the lack of a standard way to handle electrical connections (like GPIO pins).
Signed-o
From: Sarah Harris
This includes:
- CPU data structures
- object model classes and functions
- migration functions
- GDB hooks
Signed-off-by: Michael Rolnik
---
gdb-xml/avr-cpu.xml| 49
target/avr/cpu-param.h | 37 +++
target/avr/cpu.c | 584 +++
From: Sarah Harris
Stubs for unimplemented instructions and helpers for instructions that need to
interact with QEMU.
SPM and WDR are unimplemented because they require emulation of complex
peripherals.
The implementation of SLEEP is very limited due to the lack of peripherals to
generate wake
From: Sarah Harris
Signed-off-by: Michael Rolnik
---
MAINTAINERS | 6 ++
arch_init.c | 2 ++
configure | 7 +++
default-configs/avr-softmmu.mak | 5 +
hw/avr/sample.c | 2 +-
include/disas/dis-asm.h
This series of patches adds 8bit AVR cores to QEMU.
All instruction, except BREAK/DES/SPM/SPMX, are implemented. Not fully tested
yet.
However I was able to execute simple code with functions. e.g fibonacci
calculation.
This series of patches include a non real, sample board.
No fuses support yet
This includes:
- encoding of all 16 bit instructions
- encoding of all 32 bit instructions
Signed-off-by: Michael Rolnik
---
target/avr/insn.decode | 175 +
1 file changed, 175 insertions(+)
create mode 100644 target/avr/insn.decode
diff --git a/target/a
Richard Henderson writes:
> Turn helper_retaddr into a multi-state flag that may now also
> indicate when we're performing a read on behalf of the translator.
> In this case, release the mmap_lock before the longjmp back to
> the main cpu loop, and thereby avoid a failing assert therein.
>
> Fi
The purpose of this patch is to recognize a zoned block device (ZBD)
when it is opened as a raw file. The new code initializes the zoned
model propery introduced by the previous commit.
This commit is Linux-specific and in essence it checks the Zoned
Block Device Model (None/Host-managed/Host-awar
From: Shin'ichiro Kawasaki
Prevent scsi-hd and scsi-disk drivers from attaching a zoned block device
because it will appear as a regular block device at the guest and will
most certainly cause problems.
The functionality to support ZBDs is not planned for scsi-hd and
scsi-disk legacy drivers. It
This commit adds Zoned Device Model as defined in T10 ZBC and
T13 ZAC standards, along with some useful accessor functions.
Since the default value of zero in the zoned model field corresponds
to a regular (non-zoned) block device, there is no functionality
change with this commit.
Signed-off-by:
Prevent virtio-blk code from attaching a zoned block device because
it will otherwise appear as a reqular block device at the guest and
that will most certainly cause problems.
The functionality to support ZBDs via virtio-blk should be pretty
useful and there are some attempts underway to get it i
Currently, attaching zoned block devices (i.e. storage devices
compliant to ZAC/ZBC standards) using several virtio methods doesn't
work - the zoned devices appear as regular block devices at the guest.
This may cause unexpected i/o errors and, potentially, some data
corruption.
To be more precise
Add a --engine option to select either docker, podman or auto.
Among other advantages, podman allows to run rootless & daemonless
containers, fortunately sharing compatible CLI with docker.
Signed-off-by: Marc-André Lureau
---
tests/docker/docker.py | 43 +---
Signed-off-by: Marc-André Lureau
---
tests/Makefile.include | 2 +-
tests/test-char.c | 17 +
2 files changed, 14 insertions(+), 5 deletions(-)
diff --git a/tests/Makefile.include b/tests/Makefile.include
index a983dd32da..2bddebaf4b 100644
--- a/tests/Makefile.include
+++
Allow to specify the container engine to run with ENGINE variable.
By default, ENGINE=auto and will select either podman or docker.
With current podman, we have to use a uidmap trick in order to be able
to rw-share the ccache directory with the container user.
With a user 1000, the default mappi
Skip the tests if socket_check_protocol_support() failed, but do run
g_test_run() to keep TAP harness happy.
Signed-off-by: Marc-André Lureau
---
tests/test-char.c | 4 +++-
tests/test-io-channel-socket.c | 4 +++-
tests/test-util-sockets.c | 4 +++-
3 files changed, 9 insertio
Hi,
podman allows to run containers in a similar fashion as docker, but
without daemon or root privileges. Thank you podman!
There is a weird issue with getaddrinfo(), that I reported upstream
https://github.com/containers/libpod/issues/3535. For now, it is
worked around with extra socket_check_p
getaddrinfo() may succeed with PF_UNSPEC, but fail when more specific.
(this allows to skip some tests that would fail under podman)
Signed-off-by: Marc-André Lureau
---
tests/socket-helpers.c | 17 +
tests/socket-helpers.h | 11 ---
2 files changed, 13 insertions(+), 15
On 7/9/19 6:58 PM, Lucien Murray-Pitts wrote:
> Any suggestions on how to obtain pc_next from the "m68k_cpu_do_interrupt(
> CPUState *cs)" ?
I did have a suggestion. It was fairly detailed.
https://lists.gnu.org/archive/html/qemu-devel/2019-06/msg06522.html
r~
Hello,
On behalf of the QEMU Team, I'd like to announce the availability of the
first release candidate for the QEMU 4.1 release. This release is meant
for testing purposes and should not be used in a production environment.
http://download.qemu-project.org/qemu-4.1.0-rc0.tar.xz
http://downl
On 05.07.19 22:16, John Snow wrote:
> Signed-off-by: John Snow
> ---
> tests/qemu-iotests/257 | 409 +++
> tests/qemu-iotests/257.out | 2199
> tests/qemu-iotests/group |1 +
> 3 files changed, 2609 insertions(+)
> create mode 100755 tests/qemu
On 05.07.19 22:16, John Snow wrote:
> This adds an "always" policy for bitmap synchronization. Regardless of if
> the job succeeds or fails, the bitmap is *always* synchronized. This means
> that for backups that fail part-way through, the bitmap retains a record of
> which sectors need to be copie
On 7/9/19 7:10 PM, Dr. David Alan Gilbert wrote:
> * Philippe Mathieu-Daudé (phi...@redhat.com) wrote:
>> Hi David,
>>
>> On 7/9/19 12:30 PM, Dr. David Alan Gilbert wrote:
>>> * Philippe Mathieu-Daudé (phi...@redhat.com) wrote:
In the "Read Array Flowchart" the command has a value of 0xFF.
>>>
On 05.07.19 22:16, John Snow wrote:
> We don't need or want a new sync mode for simple differences in
> semantics. Create a new mode simply named "BITMAP" that is designed to
> make use of the new Bitmap Sync Mode field.
>
> Because the only bitmap sync mode is 'on-success', this adds no new
> fu
There's already a MIN and MAX macro in include/qemu/osdep.h, use them
instead.
Signed-off-by: Kővágó, Zoltán
---
audio/audio.h | 17 -
audio/alsaaudio.c | 6 +++---
audio/audio.c | 20 ++--
audio/coreaudio.c | 2 +-
audio/
Signed-off-by: Kővágó, Zoltán
---
audio/audio.h | 4 +-
audio/audio_int.h | 26 +++
audio/audio_template.h | 14 ++--
audio/mixeng.h | 9 +--
audio/rate_template.h | 2 +-
include/sysemu/replay.h | 4 +-
audio/alsaaudio.c | 26 +++
audio/audio.
Audio functions no longer access glob_audio_state, instead they get an
AudioState as a parameter. This is required in order to support
multiple backends.
glob_audio_state is also gone, and replaced with a tailq so we can store
more than one states.
Signed-off-by: Kővágó, Zoltán
---
audio/audio
Move hmp_device_add(), hmp_device_del() from monitor/hmp-cmds.c to
qdev-monitor.c, where they are covered by MAINTAINERS section "QOM",
just like qapi/qdev.json. hmp_info_qtree() and hmp_info_qdm() are
already there.
Signed-off-by: Markus Armbruster
---
This is a follow-up to my "Move QOM, qdev,
This means you should probably stop using -soundhw (as it doesn't allow
you to specify any options) and add the device manually with -device.
The exception is pcspk, it's currently not possible to manually add it.
To use it with audiodev, use something like this:
-audiodev id=foo,... -global i
Finally add audiodev= options to audio frontends so users can specify
which backend to use when multiple backends exist. Not specifying an
audiodev= option currently causes the first audiodev to be used, this is
fixed in the next commit.
Example usage: -audiodev pa,id=foo -device AC97,audiodev=fo
The aarch64 argument ordering for the operands is big-endian,
whereas the tcg argument ordering is little-endian. Use REG0
so that we honor the rZ constraints.
Fixes: 464c2969d5d
Reported-by: Peter Maydell
Signed-off-by: Richard Henderson
---
tcg/aarch64/tcg-target.inc.c | 2 +-
1 file changed
Remove glob_audio_state from functions, where possible without breaking
the API. This means that most static functions in audio.c now take an
AudioState pointer instead of implicitly using glob_audio_state. Also
included a pointer in SWVoice*, HWVoice* structs, so that functions
dealing them can
They just called audio_pcm_sw_read/write anyway, so it makes no sense
to have them too. (The noaudio's read is the only exception, but it
should work with the generic code too.)
Signed-off-by: Kővágó, Zoltán
---
audio/audio_int.h | 5 -
audio/alsaaudio.c | 12
audio/audio.
Unless we disable stream moving, pulseaudio can easily move the stream
on connect, effectively ignoring the source/sink specified by the user.
Signed-off-by: Kővágó, Zoltán
---
audio/paaudio.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/audio/paaudio.c b/audio/paaudio.c
index cc3a34
Currently this needs a workaround due to bug #247 in pulseaudio.
Signed-off-by: Kővágó, Zoltán
---
audio/paaudio.c | 25 +++--
1 file changed, 23 insertions(+), 2 deletions(-)
diff --git a/audio/paaudio.c b/audio/paaudio.c
index 24d98b344a..490bcd770e 100644
--- a/audio/paau
audio_run is called manually by alsa and oss backends when polling.
In this case only the requesting backend should be run, not all of them.
Signed-off-by: Kővágó, Zoltán
---
audio/audio_int.h | 2 +-
audio/alsaaudio.c | 7 +--
audio/audio.c | 14 +-
audio/ossaudio.c | 12
Pulseaudio normally assumes that when the server wants it, the client
can generate the audio samples and send it right away. Unfortunately
this is not the case with QEMU -- it's up to the emulated system when
does it generate the samples. Buffering the samples and sending them
from a background t
On 7/9/19 6:40 PM, Peter Maydell wrote:
> On Tue, 14 May 2019 at 02:11, Richard Henderson
> wrote:
>>
>> This is, after all, how we implement extract2 in tcg/aarch64.
>>
>> Reviewed-by: Peter Maydell
>> Signed-off-by: Richard Henderson
>> ---
>> target/arm/translate-a64.c | 38 +
Hello,
This is my next set of audio patches. This series makes it possible to use
multiple audio backends in a single qemu instance, and contains a few random
cleanup/fix patches.
Regards,
Zoltan
Kővágó, Zoltán (11):
audio: reduce glob_audio_state usage
audio: basic support for multi backend
On 05.07.19 22:16, John Snow wrote:
> This adds a "never" policy for bitmap synchronization. Regardless of if
> the job succeeds or fails, we never update the bitmap. This can be used
> to perform differential backups, or simply to avoid the job modifying a
> bitmap.
>
> Signed-off-by: John Snow
On 05.07.19 22:16, John Snow wrote:
> Depending on what a user is trying to accomplish, there might be a few
> bitmap cleanup actions that occur when an operation is finished that
> could be useful.
>
> I am proposing three:
> - NEVER: The bitmap is never synchronized against what was copied.
> -
On 05.07.19 22:16, John Snow wrote:
> Signed-off-by: John Snow
> ---
> blockdev.c | 65 +-
> 1 file changed, 6 insertions(+), 59 deletions(-)
Reviewed-by: Max Reitz
signature.asc
Description: OpenPGP digital signature
On 05.07.19 22:16, John Snow wrote:
> Create a common core that comprises the actual meat of what the backup API
> boundary needs to do, and then switch drive-backup to use it.
>
> Signed-off-by: John Snow
> ---
> blockdev.c | 122 +
> 1 file c
Patchew URL:
https://patchew.org/QEMU/20190709143912.28905-1-peter.mayd...@linaro.org/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20190709143912.28905-1-peter.mayd...@linaro.org
Subject: [Qemu-devel] [PATCH for-4.1] pl031: Corr
1 - 100 of 277 matches
Mail list logo
