qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>, Marcelo Tosatti <mtosatti@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	kvm@vger.kernel.org
Subject: [Qemu-devel] [PATCH 0/4] uq/master: Introduce KVM PIT support
Date: Tue, 31 Jan 2012 19:46:09 +0100	[thread overview]
Message-ID: <cover.1328035553.git.jan.kiszka@siemens.com> (raw)

This adds another piece of qemu-kvm to upstream: The accelerated
in-kernel model of the i8254. It does this in the same fashion as the
interrupt controllers were already introduced. And it even has one bug
less than qemu-kvm: PC speaker output still works with KVM acceleration
enabled.

The patches depend on the follow upstream or uq/master patches:
- pit, hpet, pcspk: fixes & preparation for KVM (v7, 7 patches)
  http://thread.gmane.org/gmane.comp.emulators.qemu/134393
- Generic tick reinjection control (2 patches)
  http://thread.gmane.org/gmane.comp.emulators.qemu/133306
- kvm: Implement kvm_irqchip_in_kernel
  http://thread.gmane.org/gmane.comp.emulators.qemu/134399

The series plus dependencies is also available at

    git://git.kiszka.org/qemu-kvm.git queues/kvm-pit

Please review / merge.

Jan Kiszka (4):
  i8254: Factor out base class for KVM reuse
  i8254: Open-code timer restore
  kvm: Add kvm_has_pit_state2 helper
  kvm: x86: Add user space part for in-kernel i8254

 Makefile.objs       |    2 +-
 Makefile.target     |    2 +-
 hw/i8254.c          |  289 ++++++++---------------------------------------
 hw/i8254.h          |   11 ++
 hw/i8254_common.c   |  311 +++++++++++++++++++++++++++++++++++++++++++++++++++
 hw/i8254_internal.h |   87 ++++++++++++++
 hw/kvm/i8254.c      |  237 +++++++++++++++++++++++++++++++++++++++
 hw/pc.c             |   14 ++-
 kvm-all.c           |   10 ++
 kvm-stub.c          |    5 +
 kvm.h               |    1 +
 11 files changed, 723 insertions(+), 246 deletions(-)
 create mode 100644 hw/i8254_common.c
 create mode 100644 hw/i8254_internal.h
 create mode 100644 hw/kvm/i8254.c

-- 
1.7.3.4

             reply	other threads:[~2012-01-31 18:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31 18:46 Jan Kiszka [this message]
2012-01-31 18:46 ` [Qemu-devel] [PATCH 1/4] i8254: Factor out base class for KVM reuse Jan Kiszka
2012-01-31 21:40   ` Anthony Liguori
2012-01-31 21:49     ` Jan Kiszka
2012-01-31 21:59       ` Anthony Liguori
2012-02-01 12:23       ` Paolo Bonzini
2012-02-01 12:43         ` Jan Kiszka
2012-02-01 12:55           ` Paolo Bonzini
2012-02-01 13:10             ` Jan Kiszka
2012-02-01 13:11               ` Jan Kiszka
2012-02-01 13:19           ` Anthony Liguori
2012-01-31 18:46 ` [Qemu-devel] [PATCH 2/4] i8254: Open-code timer restore Jan Kiszka
2012-01-31 18:46 ` [Qemu-devel] [PATCH 3/4] kvm: Add kvm_has_pit_state2 helper Jan Kiszka
2012-01-31 18:46 ` [Qemu-devel] [PATCH 4/4] kvm: x86: Add user space part for in-kernel i8254 Jan Kiszka
  -- strict thread matches above, loose matches on Subject: below --
2012-02-05 10:46 [Qemu-devel] [PATCH 0/4] uq/master: Introduce KVM PIT support Jan Kiszka
2012-02-08 18:24 ` Marcelo Tosatti

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=cover.1328035553.git.jan.kiszka@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).