From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Cc: blue Swirl <blauwirbel@gmail.com>,
Paul Brook <paul@codesourcery.com>,
Gleb Natapov <gleb@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: [Qemu-devel] [PATCH v4 00/13] HPET cleanups, fixes, enhancements
Date: Sun, 13 Jun 2010 14:15:33 +0200 [thread overview]
Message-ID: <cover.1276431335.git.jan.kiszka@web.de> (raw)
As the discussion around how to extend the IRQ framework /wrt
de-coalescing or message passing support still hasn't settled yet, this
series now skips the related changes, just focusing on the HPET. No
further changes compared to v3. Please merge.
Jan Kiszka (13):
hpet: Catch out-of-bounds timer access
hpet: Coding style cleanups and some refactorings
hpet: Silence warning on write to running main counter
hpet: Move static timer field initialization
hpet: Convert to qdev
hpet: Start/stop timer when HPET_TN_ENABLE is modified
hpet/rtc: Rework RTC IRQ replacement by HPET
hpet: Drop static state
hpet: Add support for level-triggered interrupts
vmstate: Add VMSTATE_STRUCT_VARRAY_UINT8
hpet: Make number of timers configurable
hpet: Add MSI support
monitor/QMP: Drop info hpet / query-hpet
QMP/vm-info | 2 +-
hw/hpet.c | 580 +++++++++++++++++++++++++++++++++--------------------
hw/hpet_emul.h | 46 +----
hw/hw.h | 10 +
hw/mc146818rtc.c | 49 ++----
hw/mc146818rtc.h | 4 +-
hw/mips_jazz.c | 2 +-
hw/mips_malta.c | 2 +-
hw/mips_r4k.c | 2 +-
hw/pc.c | 15 +-
hw/ppc_prep.c | 2 +-
monitor.c | 22 --
qemu-monitor.hx | 21 --
13 files changed, 415 insertions(+), 342 deletions(-)
next reply other threads:[~2010-06-13 12:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-13 12:15 Jan Kiszka [this message]
2010-06-13 12:15 ` [Qemu-devel] [PATCH v4 01/13] hpet: Catch out-of-bounds timer access Jan Kiszka
2010-06-13 12:15 ` [Qemu-devel] [PATCH v4 02/13] hpet: Coding style cleanups and some refactorings Jan Kiszka
2010-06-13 12:15 ` [Qemu-devel] [PATCH v4 03/13] hpet: Silence warning on write to running main counter Jan Kiszka
2010-06-13 12:15 ` [Qemu-devel] [PATCH v4 04/13] hpet: Move static timer field initialization Jan Kiszka
2010-06-13 12:15 ` [Qemu-devel] [PATCH v4 05/13] hpet: Convert to qdev Jan Kiszka
2010-06-13 12:15 ` [Qemu-devel] [PATCH v4 06/13] hpet: Start/stop timer when HPET_TN_ENABLE is modified Jan Kiszka
2010-06-13 12:15 ` [Qemu-devel] [PATCH v4 07/13] hpet/rtc: Rework RTC IRQ replacement by HPET Jan Kiszka
2010-06-13 12:15 ` [Qemu-devel] [PATCH v4 08/13] hpet: Drop static state Jan Kiszka
2010-06-13 12:15 ` [Qemu-devel] [PATCH v4 09/13] hpet: Add support for level-triggered interrupts Jan Kiszka
2010-06-13 12:15 ` [Qemu-devel] [PATCH v4 10/13] vmstate: Add VMSTATE_STRUCT_VARRAY_UINT8 Jan Kiszka
2010-06-13 12:15 ` [Qemu-devel] [PATCH v4 11/13] hpet: Make number of timers configurable Jan Kiszka
2010-06-13 12:15 ` [Qemu-devel] [PATCH v4 12/13] hpet: Add MSI support Jan Kiszka
2010-06-13 12:15 ` [Qemu-devel] [PATCH v4 13/13] monitor/QMP: Drop info hpet / query-hpet Jan Kiszka
2010-06-13 13:21 ` [Qemu-devel] Re: [PATCH v4 00/13] HPET cleanups, fixes, enhancements Blue Swirl
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.1276431335.git.jan.kiszka@web.de \
--to=jan.kiszka@web.de \
--cc=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=gleb@redhat.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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;
as well as URLs for NNTP newsgroup(s).