From: Bandan Das <bsd@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, rkrcmar@redhat.com,
jmattson@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/3] Expose VMFUNC to the nested hypervisor
Date: Fri, 04 Aug 2017 13:58:42 -0400 [thread overview]
Message-ID: <jpgini3dxkd.fsf@linux.bootlegged.copy> (raw)
In-Reply-To: <03583ab4-49e3-3955-3895-aff54e579d7e@redhat.com> (David Hildenbrand's message of "Fri, 4 Aug 2017 17:00:36 +0200")
David Hildenbrand <david@redhat.com> writes:
...
>> v1:
>> https://lkml.org/lkml/2017/6/29/958
>>
>> Bandan Das (3):
>> KVM: vmx: Enable VMFUNCs
>> KVM: nVMX: Enable VMFUNC for the L1 hypervisor
>> KVM: nVMX: Emulate EPTP switching for the L1 hypervisor
>>
>> arch/x86/include/asm/vmx.h | 9 +++
>> arch/x86/kvm/vmx.c | 185 ++++++++++++++++++++++++++++++++++++++++++++-
>> 2 files changed, 192 insertions(+), 2 deletions(-)
>>
>
> Acked-by: David Hildenbrand <david@redhat.com>
>
> (not 100% confident for a r-b, not because of your patches but because
> of the involved complexity (flushes, MMU ...))
You and Radim both constitute to major revisions and changes in these patches.
I would be 100% confident of a R-b tag by you.
Bandan
next prev parent reply other threads:[~2017-08-04 17:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 19:54 [PATCH v7 0/3] Expose VMFUNC to the nested hypervisor Bandan Das
2017-08-03 19:54 ` [PATCH v7 1/3] KVM: vmx: Enable VMFUNCs Bandan Das
2017-08-03 19:54 ` [PATCH v7 2/3] KVM: nVMX: Enable VMFUNC for the L1 hypervisor Bandan Das
2017-08-03 19:54 ` [PATCH v7 3/3] KVM: nVMX: Emulate EPTP switching " Bandan Das
2017-08-04 14:42 ` David Hildenbrand
2017-08-04 15:00 ` [PATCH v7 0/3] Expose VMFUNC to the nested hypervisor David Hildenbrand
2017-08-04 17:58 ` Bandan Das [this message]
2017-08-04 21:56 ` Radim Krčmář
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=jpgini3dxkd.fsf@linux.bootlegged.copy \
--to=bsd@redhat.com \
--cc=david@redhat.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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