From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
Gleb Natapov <gleb@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [PATCH 0/3] apic: Fixes for userspace model
Date: Tue, 10 Jul 2012 11:32:04 +0300 [thread overview]
Message-ID: <4FFBE884.2010308@redhat.com> (raw)
In-Reply-To: <cover.1341844944.git.jan.kiszka@siemens.com>
On 07/09/2012 05:42 PM, Jan Kiszka wrote:
> 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?
I applied to uq/master, where it can get some extra testing. Thanks.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Gleb Natapov <gleb@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>,
Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 0/3] apic: Fixes for userspace model
Date: Tue, 10 Jul 2012 11:32:04 +0300 [thread overview]
Message-ID: <4FFBE884.2010308@redhat.com> (raw)
In-Reply-To: <cover.1341844944.git.jan.kiszka@siemens.com>
On 07/09/2012 05:42 PM, Jan Kiszka wrote:
> 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?
I applied to uq/master, where it can get some extra testing. Thanks.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2012-07-10 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 14:42 [PATCH 0/3] apic: Fixes for userspace model Jan Kiszka
2012-07-09 14:42 ` [Qemu-devel] " Jan Kiszka
2012-07-09 14:42 ` [PATCH 1/3] apic: Resolve potential endless loop around apic_update_irq Jan Kiszka
2012-07-09 14:42 ` [Qemu-devel] " Jan Kiszka
2012-07-09 14:42 ` [PATCH 2/3] apic: Reevaluate pending interrupts on LVT_LINT0 changes Jan Kiszka
2012-07-09 14:42 ` [Qemu-devel] " Jan Kiszka
2012-07-09 14:42 ` [PATCH 3/3] apic: Defer interrupt updates to VCPU thread Jan Kiszka
2012-07-09 14:42 ` [Qemu-devel] " Jan Kiszka
2012-07-10 8:32 ` Avi Kivity [this message]
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=4FFBE884.2010308@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.