From: Bandan Das <bsd@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] nVMX: Implement emulated Page Modification Logging
Date: Thu, 04 May 2017 14:11:51 -0400 [thread overview]
Message-ID: <jpgbmr8fq54.fsf@linux.bootlegged.copy> (raw)
In-Reply-To: <f832f710-ee4a-a5bd-98c1-ebe8dc0bb735@redhat.com> (Paolo Bonzini's message of "Thu, 4 May 2017 11:21:29 +0200")
Paolo Bonzini <pbonzini@redhat.com> writes:
> On 04/05/2017 00:14, Bandan Das wrote:
>> + if (vmx->nested.pml_full) {
>> + exit_reason = EXIT_REASON_PML_FULL;
>> + vmx->nested.pml_full = false;
>> + } else if (fault->error_code & PFERR_RSVD_MASK)
>> exit_reason = EXIT_REASON_EPT_MISCONFIG;
>> else
>> exit_reason = EXIT_REASON_EPT_VIOLATION;
>> + /*
>> + * The definition of bit 12 for EPT violations and PML
>> + * full event is the same, so pass it through since
>> + * the rest of the bits are undefined.
>> + */
>
> Please zero all other bits instead. It's as easy as adding an "u64
> exit_qualification" local variable.
Will do, thanks for the review.
Bandan
> Paolo
>
>> nested_vmx_vmexit(vcpu, exit_reason, 0, vcpu->arch.exit_qualification);
next prev parent reply other threads:[~2017-05-04 18:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 22:14 [PATCH 0/3] nVMX: Emulated Page Modification Logging for Nested Virtualization Bandan Das
2017-05-03 22:14 ` [PATCH 1/3] kvm: x86: Add a hook for arch specific dirty logging emulation Bandan Das
2017-05-03 22:14 ` [PATCH 2/3] nVMX: Implement emulated Page Modification Logging Bandan Das
2017-05-04 9:21 ` Paolo Bonzini
2017-05-04 18:11 ` Bandan Das [this message]
2017-05-03 22:14 ` [PATCH 3/3] nVMX: Advertise PML to L1 hypervisor Bandan Das
2017-05-04 7:03 ` Paolo Bonzini
2017-05-04 18:22 ` Bandan Das
2017-05-05 7:26 ` Paolo Bonzini
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=jpgbmr8fq54.fsf@linux.bootlegged.copy \
--to=bsd@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox