From: Bandan Das <bsd@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Wanpeng Li <wanpeng.li@hotmail.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Wincy Van <fanwenyi0529@gmail.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: nVMX: emulate the INVVPID instruction
Date: Fri, 25 Sep 2015 10:54:54 -0400 [thread overview]
Message-ID: <jpgbncqpn0h.fsf@linux.bootlegged.copy> (raw)
In-Reply-To: <5604FD7E.3060901@redhat.com> (Paolo Bonzini's message of "Fri, 25 Sep 2015 09:53:34 +0200")
Paolo Bonzini <pbonzini@redhat.com> writes:
> On 24/09/2015 17:45, Bandan Das wrote:
>> > However, I have applied the patch to kvm/queue. Please send the changes
>> > separately, and I will squash them in the existing VPID patch.
>>
>> Please don't do this. It's making it really difficult to review these
>> patches individually :( Why not let them get some review time before
>> applying them all together ?
>
> Ok---I did it because it makes sense to keep this patch separate from
> the others. You can expose VPID even if vpid02 == vpid01 (in fact
> that's what happens if KVM cannot find a vpid02) and in that case this
> patch provides a valid implementation of INVVPID.
>
> Do you think it would help if I posted the whole kvm/queue contents a
> few days before pushing it to kvm/next?
Oh that would be great. Thank you!
> Paolo
prev parent reply other threads:[~2015-09-25 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 7:59 [PATCH] KVM: nVMX: emulate the INVVPID instruction Wanpeng Li
2015-09-23 8:39 ` Paolo Bonzini
2015-09-23 10:30 ` Wanpeng Li
2015-09-24 15:45 ` Bandan Das
2015-09-25 7:53 ` Paolo Bonzini
2015-09-25 14:54 ` Bandan Das [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=jpgbncqpn0h.fsf@linux.bootlegged.copy \
--to=bsd@redhat.com \
--cc=fanwenyi0529@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=wanpeng.li@hotmail.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 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.