From: Liran Alon <liran.alon@oracle.com>
To: <pbonzini@redhat.com>
Cc: <jmattson@google.com>, <konrad.wilk@oracle.com>,
<rkrcmar@redhat.com>, <hofsass@google.com>,
<idan.brown@oracle.com>, <kvm@vger.kernel.org>
Subject: Re: [PATCH v2] KVM: nVMX/nSVM: Don't intercept #UD when running L2
Date: Thu, 11 Jan 2018 05:29:41 -0800 (PST) [thread overview]
Message-ID: <01c24583-6a69-4115-a5bb-fe0fadfc50c6@default> (raw)
----- pbonzini@redhat.com wrote:
> On 11/01/2018 00:01, Liran Alon wrote:
> >
> > ----- jmattson@google.com wrote:
> >
> >> Liran, Are you planning to submit reverts for ae1f57670703 and
> >> ac9b305caa0d?
> >
> > Yes.
> > I just didn't had time to deal with this as I was busy with other
> Oracle Ravello specific issues.
> > I think reverting both commits is the right thing to do.
> >
> > Paolo: Note that the VMware Backdoor support series we have patched
> here (was not yet queued) is based a bit on the code of this commit.
> Do you wish me to first wait that those patches will be queued and
> then I will create the revert for these (and resolve relevant
> conflicts) or that I will create the reverts for these on top of what
> is currently queued and you will resolve the conflicts resulting when
> applying VMware Backdoor support series?
>
> I can take care of the reverts, but you'll have to repost the
> backdoor
> series. Unfortunately due to my involvement with Spectre in Red Hat
> (and Radim's vacation :)) I have fallen short on the review backlog.
>
> Paolo
No problem.
I will wait until you queue the reverts to adjust the VMware backdoor series accordingly.
Thanks,
-Liran
next reply other threads:[~2018-01-11 13:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 13:29 Liran Alon [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-10 23:01 [PATCH v2] KVM: nVMX/nSVM: Don't intercept #UD when running L2 Liran Alon
2018-01-11 10:34 ` Paolo Bonzini
2017-11-06 14:15 Liran Alon
2017-11-06 14:16 ` Paolo Bonzini
2017-11-07 1:23 ` Wanpeng Li
2017-11-10 21:37 ` Radim Krčmář
2017-12-01 23:00 ` Jim Mattson
2017-12-01 23:08 ` Jim Mattson
2017-12-02 0:27 ` Liran Alon
2018-01-10 19:56 ` Jim Mattson
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=01c24583-6a69-4115-a5bb-fe0fadfc50c6@default \
--to=liran.alon@oracle.com \
--cc=hofsass@google.com \
--cc=idan.brown@oracle.com \
--cc=jmattson@google.com \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.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