All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: malc <av1474@comtv.ru>,
	"André Weidemann" <Andre.Weidemann@web.de>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: assigned EHCI USB headset not working
Date: Fri, 10 Jun 2011 08:23:13 +0200	[thread overview]
Message-ID: <4DF1B851.10609@redhat.com> (raw)
In-Reply-To: <4DF0FEB4.6010109@siemens.com>

   Hi,

> I've two scenarios at hand now: one involves a Windows 7 guest with
> -soundhw hda, the other is my Musicpal (do you still have a firmware
> image at hand?). Some Linux guest here with identical configuration like
> Win7 does not show any problems in polling mode.

Noteworthy difference between linux and windows 7:  Windows 7 uses a 
pretty small ring buffer (~ one page, where 20ms sound data fit in) 
whereas linux uses *alot* more, 128k or so.

That makes win7 guests quite sensitive to latency issues, be it in the 
audio subsystem or elsewhere.  For example bulky screen updates with the 
non-threaded vnc server are enougth to cause audible glitches in audio 
playback.

HTH,
   Gerd

WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "André Weidemann" <Andre.Weidemann@web.de>,
	qemu-devel <qemu-devel@nongnu.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] assigned EHCI USB headset not working
Date: Fri, 10 Jun 2011 08:23:13 +0200	[thread overview]
Message-ID: <4DF1B851.10609@redhat.com> (raw)
In-Reply-To: <4DF0FEB4.6010109@siemens.com>

   Hi,

> I've two scenarios at hand now: one involves a Windows 7 guest with
> -soundhw hda, the other is my Musicpal (do you still have a firmware
> image at hand?). Some Linux guest here with identical configuration like
> Win7 does not show any problems in polling mode.

Noteworthy difference between linux and windows 7:  Windows 7 uses a 
pretty small ring buffer (~ one page, where 20ms sound data fit in) 
whereas linux uses *alot* more, 128k or so.

That makes win7 guests quite sensitive to latency issues, be it in the 
audio subsystem or elsewhere.  For example bulky screen updates with the 
non-threaded vnc server are enougth to cause audible glitches in audio 
playback.

HTH,
   Gerd

  reply	other threads:[~2011-06-10  6:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08  6:33 assigned EHCI USB headset not working André Weidemann
2011-06-08 12:49 ` Gerd Hoffmann
2011-06-09  6:19   ` André Weidemann
2011-06-09  6:53     ` Jan Kiszka
2011-06-09  7:08       ` André Weidemann
2011-06-09  7:11         ` Jan Kiszka
2011-06-09  7:11           ` [Qemu-devel] " Jan Kiszka
2011-06-09 15:13           ` malc
2011-06-09 15:13             ` [Qemu-devel] " malc
2011-06-09 15:24             ` Jan Kiszka
2011-06-09 15:24               ` [Qemu-devel] " Jan Kiszka
2011-06-09 16:09               ` malc
2011-06-09 16:09                 ` [Qemu-devel] " malc
2011-06-09 17:11                 ` Jan Kiszka
2011-06-09 17:11                   ` [Qemu-devel] " Jan Kiszka
2011-06-10  6:23                   ` Gerd Hoffmann [this message]
2011-06-10  6:23                     ` Gerd Hoffmann

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=4DF1B851.10609@redhat.com \
    --to=kraxel@redhat.com \
    --cc=Andre.Weidemann@web.de \
    --cc=av1474@comtv.ru \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.