From: Stefan Lippers-Hollmann <s.l-h@gmx.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
arei.gonglei@huawei.com, longpeng2@huawei.com,
rkrcmar@redhat.com, wangxinxin.wang@huawei.com,
weidong.huang@huawei.com, stable@vger.kernel.org
Subject: Re: Patch "KVM: VMX: avoid double list add with VT-d posted interrupts" has been added to the 4.13-stable tree
Date: Wed, 4 Oct 2017 00:30:21 +0200 [thread overview]
Message-ID: <20171004003021.11df674e@mir> (raw)
In-Reply-To: <972b2885-4a33-b30f-7fd0-bae0c4fe5aa3@redhat.com>
Hi
On 2017-10-03, Paolo Bonzini wrote:
> On 03/10/2017 09:46, Stefan Lippers-Hollmann wrote:
> > On 2017-10-02, gregkh@linuxfoundation.org wrote:
> >> This is a note to let you know that I've just added the patch titled
> >>
> >> KVM: VMX: avoid double list add with VT-d posted interrupts
> >>
> >> to the 4.13-stable tree which can be found at:
> >> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >>
> >> The filename of the patch is:
> >> kvm-vmx-avoid-double-list-add-with-vt-d-posted-interrupts.patch
> >> and it can be found in the queue-4.13 subdirectory.
> >
> > This patch, as part of the current queue-4.13, breaks the build on
> > i386 (amd64/ x86_64 builds fine):
[...]
> There is another patch in the kvm tree to fix it, I'll send it to stable
> immediately.
Thanks, I can confirm this to work in 4.13.5-rc1 (including
"KVM: VMX: use cmpxchg64") for i386 and x86_64.
Unrelated to this specific, solved, issue I can confirm kernel
4.9.53-rc1 to build and boot on armhf (ipq8065) and 4.4.90-rc1
on mips (ar71xx).
Thanks a lot, regards
Stefan Lippers-Hollmann
next prev parent reply other threads:[~2017-10-03 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1506947409121185@kroah.com>
2017-10-03 7:46 ` Patch "KVM: VMX: avoid double list add with VT-d posted interrupts" has been added to the 4.13-stable tree Stefan Lippers-Hollmann
2017-10-03 8:08 ` Paolo Bonzini
2017-10-03 22:30 ` Stefan Lippers-Hollmann [this message]
2017-10-04 7:56 ` Greg KH
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=20171004003021.11df674e@mir \
--to=s.l-h@gmx.de \
--cc=arei.gonglei@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longpeng2@huawei.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=stable@vger.kernel.org \
--cc=wangxinxin.wang@huawei.com \
--cc=weidong.huang@huawei.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