public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Marcelo Tosatti <mtosatti@redhat.com>, Avi Kivity <avi@redhat.com>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: [PATCH v4] qemu-kvm: Make PC speaker emulation aware of   in-kernel PIT
Date: Sun, 31 May 2009 12:10:18 +0200	[thread overview]
Message-ID: <4A22578A.3070701@web.de> (raw)
In-Reply-To: <20090515221422.GB12643@amt.cnet>

[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]

Marcelo Tosatti wrote:
> On Thu, May 14, 2009 at 10:43: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_PIT2 where
>> available. This unbreaks -soundhw pcspk in KVM mode.
>>
>> Changes in v4:
>>  - preserve full PIT state across read-modify-write
>>  - update kvm.h
>>
>> Changes in v3:
>>  - re-added incorrectly dropped kvm_enabled checks
>>
>> Changes in v2:
>>  - rebased over qemu-kvm and KVM_CREATE_PIT2
>>  - refactored hooks in pcspk
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> 
> Jan,
> 
> You always attempt to use KVM_CREATE_PIT2, so say on migration if the
> destination does not support the new ioctl you fallback to in-kernel
> dummy naturally. Seems the right thing to do.
> 
> Would be nice to avoid sprinkling KVM details inside hw/pcspk.c though
> but that is another problem.

Does this remark prevent merging the patch ATM? I do not see another way
how to make the pcspk aware of the in-kernel PIT, given that the speaker
is naturally coupled to PIT channel 2.

> 
> Looks good (and v3 kernel patch).
> 

Jan



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2009-05-31 10:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12  7:28 [PATCH v2] qemu-kvm: Make PC speaker emulation aware of in-kernel PIT Jan Kiszka
2009-05-12 21:58 ` [PATCH v3] " Jan Kiszka
2009-05-14 20:43   ` [PATCH v4] " Jan Kiszka
2009-05-15 22:14     ` Marcelo Tosatti
2009-05-31 10:10       ` Jan Kiszka [this message]
2009-05-31 11:09         ` 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=4A22578A.3070701@web.de \
    --to=jan.kiszka@web.de \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /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