public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Avi Kivity <avi@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] KVM: API doc enhancements and separate PIT kthread
Date: Fri, 27 Apr 2012 19:41:27 -0300	[thread overview]
Message-ID: <20120427224127.GA19223@amt.cnet> (raw)
In-Reply-To: <cover.1335278373.git.jan.kiszka@siemens.com>

On Tue, Apr 24, 2012 at 04:40:14PM +0200, Jan Kiszka wrote:
> Some cosmetics for the API docs and the documentations for the PIT
> IOCTLs are the foundation. On top comes the previously posted patch for
> a separate PIT interrupt injection kthread, just augmented by some
> documentation.
> 
> This series depends on the application or folding-in of
> http://thread.gmane.org/gmane.comp.emulators.kvm.devel/90002
> 
> Changes in v2:
>  - list obsoleted v1 PIT IOCTLs (missed in v1 due to unfinished rebase)
> 
> Jan Kiszka (3):
>   KVM: Improve readability of KVM API doc
>   KVM: x86: Document in-kernel PIT API
>   KVM: x86: Run PIT work in own kthread
> 
>  Documentation/virtual/kvm/api.txt |  170 +++++++++++++++++++++++++++++++++++--
>  arch/x86/kvm/i8254.c              |   31 ++++---
>  arch/x86/kvm/i8254.h              |    7 +-
>  3 files changed, 187 insertions(+), 21 deletions(-)
> 

Applied, thanks.


      parent reply	other threads:[~2012-04-27 22:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 14:40 [PATCH v2 0/3] KVM: API doc enhancements and separate PIT kthread Jan Kiszka
2012-04-24 14:40 ` [PATCH v2 1/3] KVM: Improve readability of KVM API doc Jan Kiszka
2012-04-24 14:40 ` [PATCH v2 2/3] KVM: x86: Document in-kernel PIT API Jan Kiszka
2012-04-24 14:40 ` [PATCH v2 3/3] KVM: x86: Run PIT work in own kthread Jan Kiszka
2012-04-27 22:41 ` Marcelo Tosatti [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=20120427224127.GA19223@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --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