From: Wanpeng Li <kernellwp@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>, kvm <kvm@vger.kernel.org>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"Marc Zyngier" <Marc.Zyngier@arm.com>,
"# v3 . 10+" <stable@vger.kernel.org>
Subject: Re: [PATCH v4 1/6] KVM: Fix leak vCPU's VMCS value into other pCPU
Date: Thu, 22 Aug 2019 16:45:13 +0800 [thread overview]
Message-ID: <CANRm+CwaMDhiCvHX7eL4fL6bcPYd76yYPVL2uuiuKTVW6ZZP4w@mail.gmail.com> (raw)
In-Reply-To: <728bf051-02eb-8fe8-042f-9893f23b4a68@redhat.com>
On Thu, 22 Aug 2019 at 16:35, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> On 22/08/19 02:46, Wanpeng Li wrote:
> > On Tue, 6 Aug 2019 at 14:20, Paolo Bonzini <pbonzini@redhat.com> wrote:
> >>
> >> On 06/08/19 02:35, Wanpeng Li wrote:
> >>> Thank you, Paolo! Btw, how about other 5 patches?
> >>
> >> Queued everything else too.
> >
> > How about patch 4/6~5/6, they are not in kvm/queue. :)
>
> I queued 4.
>
> For patch 5, I don't really see the benefit since the hypercall
> arguments are already traced.
Agreed, thank you.
Regards,
Wanpeng Li
prev parent reply other threads:[~2019-08-22 8:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 2:03 [PATCH v4 1/6] KVM: Fix leak vCPU's VMCS value into other pCPU Wanpeng Li
2019-08-05 2:03 ` [PATCH v4 2/6] KVM: LAPIC: Don't need to wakeup vCPU twice afer timer fire Wanpeng Li
2019-08-05 2:03 ` [PATCH v4 3/6] KVM: Check preempted_in_kernel for involuntary preemption Wanpeng Li
2019-08-05 2:03 ` [PATCH v4 4/6] KVM: X86: Use IPI shorthands in kvm guest when support Wanpeng Li
2019-08-05 2:03 ` [PATCH v4 5/6] KVM: LAPIC: Add pv ipi tracepoint Wanpeng Li
2019-08-05 2:03 ` [PATCH v4 6/6] KVM: X86: Add pv tlb shootdown tracepoint Wanpeng Li
2019-08-05 23:17 ` [PATCH v4 1/6] KVM: Fix leak vCPU's VMCS value into other pCPU Paolo Bonzini
2019-08-06 0:35 ` Wanpeng Li
2019-08-06 6:20 ` Paolo Bonzini
2019-08-22 0:46 ` Wanpeng Li
2019-08-22 8:35 ` Paolo Bonzini
2019-08-22 8:45 ` Wanpeng Li [this message]
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=CANRm+CwaMDhiCvHX7eL4fL6bcPYd76yYPVL2uuiuKTVW6ZZP4w@mail.gmail.com \
--to=kernellwp@gmail.com \
--cc=Marc.Zyngier@arm.com \
--cc=borntraeger@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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;
as well as URLs for NNTP newsgroup(s).