All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bandan Das <bsd@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
	Gleb Natapov <gleb@kernel.org>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Emulate VMXON region correctly
Date: Tue, 29 Apr 2014 12:51:33 -0400	[thread overview]
Message-ID: <jpglhuoxene.fsf@nelium.bos.redhat.com> (raw)
In-Reply-To: <535E3C10.9020403@siemens.com> (Jan Kiszka's message of "Mon, 28 Apr 2014 13:31:28 +0200")

Jan Kiszka <jan.kiszka@siemens.com> writes:

> On 2014-04-28 07:00, Bandan Das wrote:
>> Reference: https://bugzilla.kernel.org/show_bug.cgi?id=54521
>> 
>> The vmxon region is unused by nvmx, but adding these checks
>> are probably harmless and may detect buggy L1 hypervisors in 
>> the future!
>
> Nice and welcome! Will you provide unit tests for these cases as well?

Yeah, this and test cases for ACK_INTR_ON_EXIT are in my todo list :)
I will follow up soon..

> Jan
>
>> 
>> Bandan Das (3):
>>   KVM: nVMX: rearrange get_vmx_mem_address
>>   KVM: nVMX: additional checks on vmxon region
>>   KVM: nVMX: fail on invalid vmclear/vmptrld pointer
>> 
>>  arch/x86/kvm/vmx.c | 171 ++++++++++++++++++++++++++++++++++++-----------------
>>  1 file changed, 118 insertions(+), 53 deletions(-)
>> 

      reply	other threads:[~2014-04-29 16:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28  5:00 [PATCH 0/3] Emulate VMXON region correctly Bandan Das
2014-04-28  5:00 ` [PATCH 1/3] KVM: nVMX: rearrange get_vmx_mem_address Bandan Das
2014-04-28  5:00 ` [PATCH 2/3] KVM: nVMX: additional checks on vmxon region Bandan Das
2014-04-28 11:30   ` Jan Kiszka
2014-04-29 16:54     ` Bandan Das
2014-04-28  5:00 ` [PATCH 3/3] KVM: nVMX: fail on invalid vmclear/vmptrld pointer Bandan Das
2014-04-28 11:31 ` [PATCH 0/3] Emulate VMXON region correctly Jan Kiszka
2014-04-29 16:51   ` 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=jpglhuoxene.fsf@nelium.bos.redhat.com \
    --to=bsd@redhat.com \
    --cc=gleb@kernel.org \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@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 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.