From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Alex Bligh <alex@alex.org.uk>,
Hans de Goede <hdegoede@redhat.com>, malc <av1474@comtv.ru>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-stable] [PATCH 1/2] audio: honor QEMU_AUDIO_TIMER_PERIOD instead of waking up every *nano* second
Date: Tue, 03 Dec 2013 16:00:19 -0600 [thread overview]
Message-ID: <20131203220019.661.8899@loki> (raw)
In-Reply-To: <EA07A9E4FF85FEDC7DF664EB@nimrod.local>
Quoting Alex Bligh (2013-12-03 15:17:11)
> --On 3 December 2013 14:03:04 -0600 Michael Roth
> <mdroth@linux.vnet.ibm.com> wrote:
>
> >> Note this will not apply to 1.5 and 1.6 as is.
> >
> > What needs to be changed? Wouldn't this patch also restore the 250hz
> > frequency for 1.6, as it was pre-0.14?
>
> The function names have changed as have the clock names.
> At a guess (cut and paste diff, completely untested), you
> need something like this:
>
> diff --git a/audio/audio.c b/audio/audio.c
> index 02bb886..45d146e 100644
> --- a/audio/audio.c
> +++ b/audio/audio.c
> @@ -1124,7 +1124,8 @@ static int audio_is_timer_needed (void)
> static void audio_reset_timer (AudioState *s)
> {
> if (audio_is_timer_needed ()) {
> - qemu_mod_timer (s->ts, qemu_get_clock_ns (vm_clock) + 1);
> + qemu_mod_timer (s->ts, qemu_get_clock_ns (vm_clock) +
> + conf.period.ticks);
> }
> else {
> qemu_del_timer (s->ts);
Ah, thanks, this looks correct. Kept staring at 1.6/1.7 versions and wasn't
seeing a difference for some reason...
>
> --
> Alex Bligh
prev parent reply other threads:[~2013-12-03 22:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 19:42 [Qemu-devel] [PATCH 1/2] audio: honor QEMU_AUDIO_TIMER_PERIOD instead of waking up every *nano* second Hans de Goede
2013-10-09 19:42 ` [Qemu-devel] [PATCH 2/2] audio: Lower default wakeup rate to 100 times / second Hans de Goede
2013-10-10 6:31 ` [Qemu-devel] [PATCH 1/2] audio: honor QEMU_AUDIO_TIMER_PERIOD instead of waking up every *nano* second Alex Bligh
2013-10-10 6:58 ` Hans de Goede
2013-10-10 7:02 ` Alex Bligh
2013-10-10 9:23 ` Hans de Goede
2013-10-10 9:35 ` Paolo Bonzini
2013-12-03 20:03 ` [Qemu-devel] [Qemu-stable] " Michael Roth
2013-12-03 21:17 ` Alex Bligh
2013-12-03 22:00 ` Michael Roth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131203220019.661.8899@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=alex@alex.org.uk \
--cc=av1474@comtv.ru \
--cc=hdegoede@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).