From: Jan Kiszka <jan.kiszka@siemens.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Gleb Natapov <gleb@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Avi Kivity <avi@redhat.com>, kvm <kvm@vger.kernel.org>,
Anthony Liguori <aliguori@us.ibm.com>
Subject: [Qemu-devel] [PATCH 0/3] apic: Fixes for userspace model
Date: Mon, 9 Jul 2012 16:42:29 +0200 [thread overview]
Message-ID: <cover.1341844944.git.jan.kiszka@siemens.com> (raw)
As Avi noted recently, there is a problem in way we inject interrupts
into the userspace APIC under KVM: The TRP check over the iothread may
race with the VCPU raising the TPR value while in KVM mode. Patch 3
addresses this issue.
The other two patches fix problems I came across while thinking about
the first one.
Who would like to process this series, up/master? Or should it go in
directly?
Jan Kiszka (3):
apic: Resolve potential endless loop around apic_update_irq
apic: Reevaluate pending interrupts on LVT_LINT0 changes
apic: Defer interrupt updates to VCPU thread
cpu-exec.c | 6 ++++++
hw/apic.c | 27 ++++++++++++++++++++++-----
hw/apic.h | 1 +
hw/apic_internal.h | 1 -
target-i386/cpu.h | 4 +++-
target-i386/kvm.c | 4 ++++
6 files changed, 36 insertions(+), 7 deletions(-)
--
1.7.3.4
next reply other threads:[~2012-07-09 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 14:42 Jan Kiszka [this message]
2012-07-09 14:42 ` [Qemu-devel] [PATCH 1/3] apic: Resolve potential endless loop around apic_update_irq Jan Kiszka
2012-07-09 14:42 ` [Qemu-devel] [PATCH 2/3] apic: Reevaluate pending interrupts on LVT_LINT0 changes Jan Kiszka
2012-07-09 14:42 ` [Qemu-devel] [PATCH 3/3] apic: Defer interrupt updates to VCPU thread Jan Kiszka
2012-07-10 8:32 ` [Qemu-devel] [PATCH 0/3] apic: Fixes for userspace model Avi Kivity
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.1341844944.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--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).