From: Paolo Bonzini <pbonzini@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, nikola.ciprich@linuxbox.cz,
Haozhong Zhang <haozhong.zhang@intel.com>
Subject: Re: [PATCH] KVM MMU: check pending exception before injecting APF
Date: Fri, 9 Feb 2018 18:21:13 +0100 [thread overview]
Message-ID: <577e399b-7ca8-3df0-e473-cbac9dbe122d@redhat.com> (raw)
In-Reply-To: <20180209171729.GA20345@kroah.com>
On 09/02/2018 18:17, Greg KH wrote:
> On Fri, Feb 09, 2018 at 06:00:42PM +0100, Paolo Bonzini wrote:
>> From: Haozhong Zhang <haozhong.zhang@intel.com>
>>
>> [ upstream commit 2a266f23550be997d783f27e704b9b40c4010292 Mon Sep 17 00:00:00 2001 ]
>
> Odd date :)
Oops... git's fake mbox "From" line.
>>
>> For example, when two APF's for page ready happen after one exit and
>> the first one becomes pending, the second one will result in #DF.
>> Instead, just handle the second page fault synchronously.
>>
>> Reported-by: Ross Zwisler <zwisler@gmail.com>
>> Message-ID: <CAOxpaSUBf8QoOZQ1p4KfUp0jq76OKfGY4Uxs-Gg8ngReD99xww@mail.gmail.com>
>> Reported-by: Alec Blayne <ab@tevsa.net>
>> Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com>
>> Fixes: 664f8e26b00c7673a8303b0d40853a0c24ca93e1
>
> So this is only needed for 4.14.y?
Yes. 4.13 and 4.15 both work.
Paolo
next prev parent reply other threads:[~2018-02-09 17:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 17:00 [PATCH] KVM MMU: check pending exception before injecting APF Paolo Bonzini
2018-02-09 17:17 ` Greg KH
2018-02-09 17:21 ` Paolo Bonzini [this message]
2018-02-09 17:44 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2018-01-10 13:44 Haozhong Zhang
2018-01-11 10:48 ` Wanpeng Li
2018-01-11 11:07 ` Haozhong Zhang
2018-01-11 11:22 ` Haozhong Zhang
2018-01-11 13:06 ` Paolo Bonzini
2018-01-11 17:00 ` Ross Zwisler
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=577e399b-7ca8-3df0-e473-cbac9dbe122d@redhat.com \
--to=pbonzini@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=haozhong.zhang@intel.com \
--cc=nikola.ciprich@linuxbox.cz \
--cc=stable@vger.kernel.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.