qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Avi Kivity <avi@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: [Qemu-devel] [PATCH v3 0/7] pit, hpet, pcspk: fixes & preparation for KVM
Date: Tue, 31 Jan 2012 18:41:23 +0100	[thread overview]
Message-ID: <cover.1328031687.git.jan.kiszka@siemens.com> (raw)

This is a preparatory series to allow the introduction of the KVM
in-kernel PIT. It also fixes various bugs in the PIT and HPET code,
see patches for details.

Changes in V3:
 - rebased over master
 - tuned pic_init interface to avoid isa_get_irq(NULL, ...)

Jan Kiszka (7):
  i8254: Do not raise IRQ level on reset
  hpet: Save/restore cached RTC IRQ level
  i8254: Factor out interface header
  i8254: Pass alternative IRQ output object on initialization
  i8254: Rework & fix interaction with HPET in legacy mode
  pcspk: Convert to qdev
  i8254: Factor out pit_get_channel_info

 arch_init.c        |    1 +
 hw/alpha_dp264.c   |    3 +-
 hw/hpet.c          |   65 ++++++++++++++++++++++++++----------
 hw/hpet_emul.h     |    3 ++
 hw/i82378.c        |    6 ++-
 hw/i8254.c         |   92 ++++++++++++++++++++++-----------------------------
 hw/i8254.h         |   57 ++++++++++++++++++++++++++++++++
 hw/mips_fulong2e.c |    3 +-
 hw/mips_jazz.c     |    6 ++-
 hw/mips_malta.c    |    3 +-
 hw/mips_r4k.c      |    3 +-
 hw/pc.c            |   19 ++++++++--
 hw/pc.h            |   29 ----------------
 hw/pcspk.c         |   79 ++++++++++++++++++++++++++++++++++++--------
 hw/pcspk.h         |   45 +++++++++++++++++++++++++
 15 files changed, 288 insertions(+), 126 deletions(-)
 create mode 100644 hw/i8254.h
 create mode 100644 hw/pcspk.h

-- 
1.7.3.4

             reply	other threads:[~2012-01-31 17:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31 17:41 Jan Kiszka [this message]
2012-01-31 17:41 ` [Qemu-devel] [PATCH v3 1/7] i8254: Do not raise IRQ level on reset Jan Kiszka
2012-01-31 17:41 ` [Qemu-devel] [PATCH v3 2/7] hpet: Save/restore cached RTC IRQ level Jan Kiszka
2012-01-31 21:02   ` Anthony Liguori
2012-01-31 22:05     ` Jan Kiszka
2012-01-31 22:38       ` Anthony Liguori
2012-01-31 22:39         ` Jan Kiszka
2012-01-31 17:41 ` [Qemu-devel] [PATCH v3 3/7] i8254: Factor out interface header Jan Kiszka
2012-01-31 17:41 ` [Qemu-devel] [PATCH v3 4/7] i8254: Pass alternative IRQ output object on initialization Jan Kiszka
2012-01-31 17:41 ` [Qemu-devel] [PATCH v3 5/7] i8254: Rework & fix interaction with HPET in legacy mode Jan Kiszka
2012-01-31 17:41 ` [Qemu-devel] [PATCH v3 6/7] pcspk: Convert to qdev Jan Kiszka
2012-01-31 20:49   ` Anthony Liguori
2012-01-31 22:00     ` Jan Kiszka
2012-01-31 22:40       ` Anthony Liguori
2012-01-31 22:48         ` Jan Kiszka
2012-01-31 23:23           ` Anthony Liguori
2012-02-01  7:29     ` Paolo Bonzini
2012-02-01  9:18       ` Jan Kiszka
2012-01-31 17:41 ` [Qemu-devel] [PATCH v3 7/7] i8254: Factor out pit_get_channel_info Jan Kiszka

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.1328031687.git.jan.kiszka@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=blauwirbel@gmail.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).