From: Jan Kiszka <jan.kiszka@siemens.com>
To: qemu-devel@nongnu.org, Anthony Liguori <aliguori@us.ibm.com>
Cc: kvm@vger.kernel.org, Alexander Graf <agraf@suse.de>,
Gleb Natapov <gleb@redhat.com>, Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: [0.14?][PATCH 0/4] IOAPIC fixes
Date: Thu, 3 Feb 2011 15:55:31 +0100 [thread overview]
Message-ID: <cover.1296744934.git.jan.kiszka@siemens.com> (raw)
This series fixes the re-injection of level-triggered IRQs that are
still raised on APIC EOI, adds a must-have field to the vmstate of the
IOAPIC, and also aligns that vmstate with qemu-kvm.
I would recommend the whole series for 0.14, but at least patch 1 should
be applied.
Jan Kiszka (4):
ioapic: Implement EOI handling for level-triggered IRQs
ioapic: Save/restore irr
ioapic: Prepare for base address relocation
ioapic: Style & magics cleanup
hw/apic.c | 9 ++-
hw/ioapic.c | 244 +++++++++++++++++++++++++++++++++++++++++-----------------
hw/ioapic.h | 24 ++++++
hw/pc_piix.c | 5 +-
4 files changed, 206 insertions(+), 76 deletions(-)
create mode 100644 hw/ioapic.h
next reply other threads:[~2011-02-03 14:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 14:55 Jan Kiszka [this message]
2011-02-03 14:55 ` [0.14?][PATCH 1/4] ioapic: Implement EOI handling for level-triggered IRQs Jan Kiszka
2011-02-03 19:59 ` Anthony Liguori
2011-02-03 14:55 ` [0.14?][PATCH 2/4] ioapic: Save/restore irr Jan Kiszka
2011-02-03 14:55 ` [0.14?][PATCH 3/4] ioapic: Prepare for base address relocation Jan Kiszka
2011-02-03 17:03 ` [Qemu-devel] " Blue Swirl
2011-02-03 17:18 ` Jan Kiszka
2011-02-03 17:36 ` Blue Swirl
2011-02-03 17:43 ` Jan Kiszka
2011-02-03 17:54 ` Blue Swirl
2011-02-03 18:01 ` Jan Kiszka
2011-02-03 19:01 ` Blue Swirl
2011-02-03 19:06 ` Jan Kiszka
2011-02-03 19:11 ` [Qemu-devel] " Blue Swirl
2011-02-03 19:25 ` Jan Kiszka
2011-02-03 19:30 ` Blue Swirl
2011-02-03 19:42 ` Jan Kiszka
2011-02-03 14:55 ` [0.14?][PATCH 4/4] ioapic: Style & magics cleanup 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.1296744934.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=gleb@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).