From: Paolo Bonzini <pbonzini@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Liran Alon <liran.alon@oracle.com>,
Alexander Levin <Alexander.Levin@microsoft.com>,
konrad wilk <konrad.wilk@oracle.com>,
stable@vger.kernel.org, rkrcmar@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH AUTOSEL for 4.14 006/100] KVM: nVMX/nSVM: Don't intercept #UD when running L2
Date: Thu, 25 Jan 2018 11:35:11 -0500 (EST) [thread overview]
Message-ID: <1080098449.2581214.1516898111818.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20180125095019.GB30255@kroah.com>
> > Just wanted stable maintainers to note that Jim, Paolo & myself decided
> > eventually to revert this commit along with commit ae1f57670703 on
> > upstream KVM. However, it is true that this commit makes commit
> > ae1f57670703 more complete. Therefore we have 2 options here:
> > 1) Apply this backport and sometime in the future also apply the reverts of
> > both these commits with Paolo's commit which reverts them.
>
> Being "bug compatible" is good, I like that option :)
It's not even a bug, just different behavior and in the end it turns out to be
less surprising if we revert. So even better. :)
> When is the revert patch going to hit Linus's tree? During the 4.16-rc1
> merge window?
It's already there, commit ac9b305caa. But since this one was not marked
for stable, ac9b305caa wasn't either.
Paolo
next prev parent reply other threads:[~2018-01-25 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 9:25 [PATCH AUTOSEL for 4.14 006/100] KVM: nVMX/nSVM: Don't intercept #UD when running L2 Liran Alon
2018-01-25 9:50 ` Greg KH
2018-01-25 16:35 ` Paolo Bonzini [this message]
2018-01-26 9:34 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2018-01-24 4:14 [PATCH AUTOSEL for 4.14 001/100] drm/vc4: Account for interrupts in flight Sasha Levin
2018-01-24 4:14 ` [PATCH AUTOSEL for 4.14 006/100] KVM: nVMX/nSVM: Don't intercept #UD when running L2 Sasha Levin
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=1080098449.2581214.1516898111818.JavaMail.zimbra@redhat.com \
--to=pbonzini@redhat.com \
--cc=Alexander.Levin@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=rkrcmar@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox