qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Stefan Pietsch <stefan.pietsch@lsexperts.de>
Cc: Jan Kiszka <jan.kiszka@web.de>,
	qemu-devel <qemu-devel@nongnu.org>,
	kvm@vger.kernel.org
Subject: [Qemu-devel] Re: KVM: High CPU load with audio enabled
Date: Wed, 10 Nov 2010 13:18:25 +0300	[thread overview]
Message-ID: <4CDA7171.2090002@msgid.tls.msk.ru> (raw)
In-Reply-To: <20101110094445.XhqCITF5qDm7EfMJ9HkUDf@consulting.lsexperts.de>

10.11.2010 12:39, Stefan Pietsch wrote:
> * Michael Tokarev <mjt@tls.msk.ru> [2010-11-09 15:41]:
> 
>> Ok. This is wrong: neither of the two changes went into any
>> stable release.  Hence we've bugs which are long fixed but
>> no one knows about this.  As usual for qemu[-kvm] development.
> 
> I can reproduce the problem with the Debian release 0.12.5+dfsg-4.
> So this is not related to the 0.13.0 release.

It is related to supporting stable releases, or lack thereof.

As you just discovered, the same bug exists in 0.12 stable
version too, also not fixed there.  Earlier today when I
prepared new 0.13 release for debian I also checked if the
same fix should be applied to 0.12, and indeed it should -
and I updated 0.12 debian branch too.

/mjt

      reply	other threads:[~2010-11-10 10:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101108133310.NDW2tl7gaq4uLMdHXOT0UP@consulting.lsexperts.de>
     [not found] ` <4CD88C58.9030501@msgid.tls.msk.ru>
2010-11-09  8:27   ` [Qemu-devel] Re: KVM: High CPU load with audio enabled Jan Kiszka
2010-11-09 13:48     ` malc
2010-11-09 14:33       ` Michael Tokarev
2010-11-09 14:41         ` Michael Tokarev
2010-11-10  9:39           ` Stefan Pietsch
2010-11-10 10:18             ` Michael Tokarev [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=4CDA7171.2090002@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefan.pietsch@lsexperts.de \
    /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).