public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: kvm@vger.kernel.org
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-kvm upstreaming: Do we need -no-kvm-pit and -no-kvm-pit-reinjection semantics?
Date: Fri, 20 Jan 2012 13:00:32 +0100	[thread overview]
Message-ID: <jfbl10$3bv$1@dough.gmane.org> (raw)
In-Reply-To: <4F194C57.2030404@siemens.com>

On 01/20/2012 12:13 PM, Jan Kiszka wrote:
> OK, this sounds like a good option: add per-device control but also
> introduce global default. The latter can still be done later on.
>
> The only problem is that we should already come up with the right,
> generic control switch template. "reinject=on|off", as I did it for now
> for the PIT, is definitely not optimal.

What about adding suboptions to -clock (like driftfix we have for -rtc)?


      reply	other threads:[~2012-01-20 12:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-19  8:33 qemu-kvm upstreaming: Do we need -no-kvm-pit and -no-kvm-pit-reinjection semantics? Jan Kiszka
2012-01-19 17:25 ` Marcelo Tosatti
2012-01-19 17:38   ` Jan Kiszka
2012-01-19 17:53     ` Marcelo Tosatti
2012-01-19 18:01       ` Jan Kiszka
2012-01-20 10:14         ` Marcelo Tosatti
2012-01-20 10:22           ` Jan Kiszka
2012-01-20 10:25             ` [Qemu-devel] " Daniel P. Berrange
2012-01-20 11:13               ` Jan Kiszka
2012-01-20 11:45                 ` Daniel P. Berrange
2012-01-20 12:00                   ` Jan Kiszka
2012-01-20 12:42                     ` Daniel P. Berrange
2012-01-20 12:51                       ` Jan Kiszka
2012-01-20 12:54                         ` Daniel P. Berrange
2012-01-20 13:02                           ` Jan Kiszka
2012-01-20 13:06                             ` Daniel P. Berrange
2012-01-20 10:39             ` Jamie Lokier
2012-01-20 11:13               ` [Qemu-devel] " Jan Kiszka
2012-01-20 12:00                 ` Paolo Bonzini [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='jfbl10$3bv$1@dough.gmane.org' \
    --to=pbonzini@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox