- 16 Jan, 2013 1 commit
-
-
Stefan Weil authored
sw->name already uses the correct g_free to free the allocated memory. Signed-off-by:
Stefan Weil <sw@weilnetz.de> Signed-off-by:
Anthony Liguori <aliguori@us.ibm.com>
-
- 19 Dec, 2012 3 commits
-
-
Paolo Bonzini authored
Signed-off-by:
Paolo Bonzini <pbonzini@redhat.com>
-
Paolo Bonzini authored
Signed-off-by:
Paolo Bonzini <pbonzini@redhat.com>
-
Paolo Bonzini authored
Signed-off-by:
Paolo Bonzini <pbonzini@redhat.com>
-
- 16 Jul, 2012 1 commit
-
-
malc authored
Signed-off-by:
malc <av1474@comtv.ru>
-
- 24 May, 2012 1 commit
-
-
Jan Kiszka authored
Not only clean up enabled voices but any registered one. Backends like pulsaudio rely on unconditional fini handler invocations. This fixes "Memory pool destroyed but not all memory blocks freed!" warnings on VM shutdowns when pa is used and lockups of QEMU on shutdown as it got stuck on some pa-internal synchronization point. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com> Signed-off-by:
malc <av1474@comtv.ru>
-
- 17 Apr, 2012 2 commits
-
-
Marc-André Lureau authored
If the audio backend is capable of volume control, don't apply software volume (mixeng_volume ()), but instead, rely on backend volume control. This will allow guest to have full range volume control. Signed-off-by:
Marc-Andr? Lureau <marcandre.lureau@redhat.com> Signed-off-by:
malc <av1474@comtv.ru>
-
Marc-André Lureau authored
Add a new PCM control operation to update the stream volume on the audio backend. The argument given is a SWVoiceOut/SWVoiceIn. v4: - verified other backends didn't fail/assert on this new control they randomly return 0 or -1, but we ignore return value. Signed-off-by:
Marc-Andr? Lureau <marcandre.lureau@redhat.com> Signed-off-by:
malc <av1474@comtv.ru>
-
- 25 Feb, 2012 1 commit
-
-
Stefan Weil authored
Static code analysers expect these comments for case statements without a break statement. Signed-off-by:
Stefan Weil <sw@weilnetz.de> Signed-off-by:
malc <av1474@comtv.ru>
-
- 14 Dec, 2011 1 commit
-
-
Stefan Weil authored
accidently->accidentally annother->another choosen->chosen consideres->considers decriptor->descriptor developement->development paramter->parameter preceed->precede preceeding->preceding priviledge->privilege propogation->propagation substraction->subtraction throught->through upto->up to usefull->useful Fix also grammar in posix-aio-compat.c Signed-off-by:
Stefan Weil <sw@weilnetz.de> Signed-off-by:
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
-
- 15 Sep, 2011 1 commit
-
-
Luiz Capitulino authored
Today, when notifying a VM state change with vm_state_notify(), we pass a VMSTOP macro as the 'reason' argument. This is not ideal because the VMSTOP macros tell why qemu stopped and not exactly what the current VM state is. One example to demonstrate this problem is that vm_start() calls vm_state_notify() with reason=0, which turns out to be VMSTOP_USER. This commit fixes that by replacing the VMSTOP macros with a proper state type called RunState. Signed-off-by:
Luiz Capitulino <lcapitulino@redhat.com>
-
- 21 Aug, 2011 1 commit
-
-
Anthony Liguori authored
qemu_malloc/qemu_free no longer exist after this commit. Signed-off-by:
Anthony Liguori <aliguori@us.ibm.com>
-
- 21 Mar, 2011 1 commit
-
-
Paolo Bonzini authored
This was done with: sed -i 's/qemu_get_clock\>/qemu_get_clock_ns/' \ $(git grep -l 'qemu_get_clock\>' ) sed -i 's/qemu_new_timer\>/qemu_new_timer_ns/' \ $(git grep -l 'qemu_new_timer\>' ) after checking that get_clock and new_timer never occur twice on the same line. There were no missed occurrences; however, even if there had been, they would have been caught by the compiler. There was exactly one false positive in qemu_run_timers: - current_time = qemu_get_clock (clock); + current_time = qemu_get_clock_ns (clock); which is of course not in this patch. Signed-off-by:
Paolo Bonzini <pbonzini@redhat.com>
-
- 12 Jan, 2011 1 commit
-
-
Michael Walle authored
Refactor the volume mixing, so it can be reused for capturing devices. Additionally, it removes superfluous multiplications with the nominal volume within the hardware voice code path. Signed-off-by:
Michael Walle <michael@walle.cc> Signed-off-by:
malc <av1474@comtv.ru>
-
- 18 Nov, 2010 1 commit
-
-
malc authored
Originally proposed by Gerd Hoffmann. Signed-off-by:
malc <av1474@comtv.ru> Acked-by:
Gerd Hoffmann <kraxel@redhat.com>
-
- 09 Nov, 2010 1 commit
-
-
Gerd Hoffmann authored
Add support for the spice audio interface. With this patch applied audio can be forwarded over the network from/to the spice client. Both recording and playback is supported. The driver is first in the driver list, but the can_be_default flag is set only in case spice is active. So if you have the spice protocol enabled the spice audio driver is the default one, otherwise whatever comes first after spice in the list. Overriding the default using QEMU_AUDIO_DRV works in any case. [ v2: audio codestyle: add spaces before open parenthesis ] [ v2: add const to silence array ] Signed-off-by:
Gerd Hoffmann <kraxel@redhat.com> Cc: malc <av1474@comtv.ru> Signed-off-by:
malc <av1474@comtv.ru>
-
- 06 Jul, 2010 1 commit
-
-
Alex Williamson authored
When available, we'd like to be able to access the DeviceState when registering a savevm. For buses with a get_dev_path() function, this will allow us to create more unique savevm id strings. Signed-off-by:
Alex Williamson <alex.williamson@redhat.com> Signed-off-by:
Anthony Liguori <aliguori@us.ibm.com>
-
- 16 Mar, 2010 1 commit
-
-
Markus Armbruster authored
Commits 376253ec..731b0364 introduced global variable cur_mon, which points to the "default monitor" (if any), except during execution of monitor_read() or monitor_control_read() it points to the monitor from which we're reading instead (the "current monitor"). Monitor command handlers run within monitor_read() or monitor_control_read(). Default monitor and current monitor are really separate things, and squashing them together is confusing and error-prone. For instance, usb_host_scan() can run both in "info usbhost" and periodically via usb_host_auto_check(). It prints to cur_mon, which is what we want in the former case: the monitor executing "info usbhost". But since that's the default monitor in the latter case, it periodically spams the default monitor there. A few places use cur_mon to log stuff to the default monitor. If we ever log something while cur_mon points to current monitor instead of default monitor, the log temporarily "jumps" to another monitor. Whether that can or cannot happen isn't always obvious. Maybe logging to the default monitor (which may not even exist) is a bad idea, and we should log to stderr or a logfile instead. But that's outside the scope of this commit. Change cur_mon to point to the current monitor. Create new default_mon to point to the default monitor. Update users of cur_mon accordingly. This fixes the periodical spamming of the default monitor by usb_host_scan(). It also stops "log jumping", should that problem exist.
-
- 16 Jan, 2010 1 commit
-
-
malc authored
Signed-off-by:
malc <av1474@comtv.ru>
-
- 03 Dec, 2009 1 commit
-
-
Juan Quintela authored
Signed-off-by:
Juan Quintela <quintela@redhat.com> Signed-off-by:
Anthony Liguori <aliguori@us.ibm.com>
-
- 18 Sep, 2009 4 commits
-
-
malc authored
Signed-off-by:
malc <av1474@comtv.ru>
-
malc authored
pcm_ops.run_out now takes number of live samples (which will be always greater than zero) as a second argument, every driver was calling audio_pcm_hw_get_live_out anyway with exception of fmod which used audio_pcm_hw_get_live_out2 for no good reason. Signed-off-by:
malc <av1474@comtv.ru>
-
malc authored
Signed-off-by:
malc <av1474@comtv.ru>
-
malc authored
Signed-off-by:
malc <av1474@comtv.ru>
-
- 13 Sep, 2009 1 commit
-
-
Jan Kiszka authored
Signed-off-by:
Jan Kiszka <jan.kiszka@web.de> Signed-off-by:
malc <av1474@comtv.ru>
-
- 12 Sep, 2009 1 commit
-
-
Blue Swirl authored
Problem: Our file sys-queue.h is a copy of the BSD file, but there are some additions and it's not entirely compatible. Because of that, there have been conflicts with system headers on BSD systems. Some hacks have been introduced in the commits 15cc9235, f40d7537, 96555a96 and 3990d09a but the fixes were fragile. Solution: Avoid the conflict entirely by renaming the functions and the file. Revert the previous hacks. Signed-off-by:
Blue Swirl <blauwirbel@gmail.com>
-
- 11 Sep, 2009 3 commits
-
-
malc authored
Signed-off-by:
malc <av1474@comtv.ru>
-
malc authored
Signed-off-by:
malc <av1474@comtv.ru>
-
Juan Quintela authored
Signed-off-by:
Juan Quintela <quintela@redhat.com> Signed-off-by:
Anthony Liguori <aliguori@us.ibm.com>
-
- 12 Aug, 2009 1 commit
-
-
malc authored
-
- 11 Aug, 2009 2 commits
-
-
malc authored
Reformat to make item borders more visible Fix cases of stray tabs and vertical misalignments Signed-off-by:
malc <av1474@comtv.ru>
-
Juan Quintela authored
Signed-off-by:
Juan Quintela <quintela@redhat.com>
-
- 27 Jul, 2009 1 commit
-
-
Juan Quintela authored
Generate CONFIG_AUDIO_DRIVERS. Order is important here, because the first driver in the list is the one used by default. Signed-off-by:
Juan Quintela <quintela@redhat.com> Signed-off-by:
Anthony Liguori <aliguori@us.ibm.com>
-
- 24 Jul, 2009 1 commit
-
-
malc authored
Signed-off-by:
malc <av1474@comtv.ru>
-
- 22 Jul, 2009 1 commit
-
-
Juan Quintela authored
Signed-off-by:
Juan Quintela <quintela@redhat.com> Signed-off-by:
Anthony Liguori <aliguori@us.ibm.com>
-
- 13 May, 2009 1 commit
-
-
malc authored
-
- 12 May, 2009 1 commit
-
-
Paul Brook authored
Failure to initialize the audio subsystem is not handled consistently. Where it is handled it has guest visible effects, which is wrong. We already have a "nosound" audio driver as a last resort, so trying to proceed without an audio backend seems pointless. Also protect against multiple calls to AUD_init so that this can be pushed down into individual devices. Signed-off-by:
Paul Brook <paul@codesourcery.com>
-
- 05 Mar, 2009 1 commit
-
-
aliguori authored
Refactor the monitor API and prepare it for decoupled terminals: term_print functions are renamed to monitor_* and all monitor services gain a new parameter (mon) that will once refer to the monitor instance the output is supposed to appear on. However, the argument remains unused for now. All monitor command callbacks are also extended by a mon parameter so that command handlers are able to pass an appropriate reference to monitor output services. For the case that monitor outputs so far happen without clearly identifiable context, the global variable cur_mon is introduced that shall once provide a pointer either to the current active monitor (while processing commands) or to the default one. On the mid or long term, those use case will be obsoleted so that this variable can be removed again. Due to the broad usage of the monitor interface, this patch mostly deals with converting users of the monitor API. A few of them are already extended to pass 'mon' from the command handler further down to internal functions that invoke monitor_printf. At this chance, monitor-related prototypes are moved from console.h to a new monitor.h. The same is done for the readline API. Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com> Signed-off-by:
Anthony Liguori <aliguori@us.ibm.com> git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6711 c046a42c-6fe2-441c-8c8c-71466251a162
-
- 18 Feb, 2009 1 commit
-
-
malc authored
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6627 c046a42c-6fe2-441c-8c8c-71466251a162
-
- 05 Feb, 2009 1 commit
-
-
aliguori authored
Signed-off-by:
Avi Kivity <avi@redhat.com> Signed-off-by:
Anthony Liguori <aliguori@us.ibm.com> git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6528 c046a42c-6fe2-441c-8c8c-71466251a162
-