From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Avi Kivity <avi@redhat.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [PATCH] kvm-userspace: Make PC speaker emulation aware of in-kernel PIT
Date: Fri, 24 Apr 2009 21:13:19 -0300 [thread overview]
Message-ID: <20090425001319.GB15144@amt.cnet> (raw)
In-Reply-To: <49F0CE65.4050005@web.de>
Jan,
While the patch itself looks fine, IMO it would be better to move all of
the timer handling to userspace, except the performance critical parts,
since most of it is generic. Either periodic or one-shot timer, with:
- PIO or MMIO region returns remaining time for expiration.
- PIO or MMIO region programs the next event and timer mode.
Oversimplified of course (kvm_timer_ops was the first step in that
direction). I believe there will be a proposed HPET in-kernel driver.
I don't see what is the problem with partial components that Avi talks
about.
On Thu, Apr 23, 2009 at 10:24:05PM +0200, Jan Kiszka wrote:
> When using the in-kernel PIT the speaker emulation has to synchronize
> the PIT state with KVM. Enhance the existing speaker sound device and
> allow it to take over port 0x61 by using KVM_CREATE_PIT_NOSPKR when
> available. This unbreaks -soundhw pcspk in KVM mode.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
next prev parent reply other threads:[~2009-04-25 0:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 20:24 [PATCH] kvm-userspace: Make PC speaker emulation aware of in-kernel PIT Jan Kiszka
2009-04-25 0:13 ` Marcelo Tosatti [this message]
2009-04-25 13:08 ` Anthony Liguori
2009-04-25 16:28 ` Jan Kiszka
2009-04-25 19:59 ` Anthony Liguori
2009-04-27 13:00 ` Sheng Yang
2009-04-28 4:44 ` David S. Ahern
2009-04-28 7:02 ` Dor Laor
2009-04-27 22:32 ` Marcelo Tosatti
2009-05-04 9:34 ` Avi Kivity
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=20090425001319.GB15144@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.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