Re: [PATCH 05/10] KVM/nVMX: Use kvm_vcpu_map when mapping the L1 MSR bitmap

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH 05/10] KVM/nVMX: Use kvm_vcpu_map when mapping the L1 MSR bitmap
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Fri, 23 Feb 2018 16:36:02 -0500
Cc: x86@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, kvm@xxxxxxxxxxxxxxx, hpa@xxxxxxxxx, jmattson@xxxxxxxxxx, mingo@xxxxxxxxxx, pbonzini@xxxxxxxxxx, rkrcmar@xxxxxxxxxx, tglx@xxxxxxxxxxxxx
In-reply-to: <1519235241-6500-6-git-send-email-karahmed@amazon.de>
References: <1519235241-6500-1-git-send-email-karahmed@amazon.de> <1519235241-6500-6-git-send-email-karahmed@amazon.de>
User-agent: Mutt/1.8.3 (2017-05-23)

On Wed, Feb 21, 2018 at 06:47:16PM +0100, KarimAllah Ahmed wrote:
> ... since using kvm_vcpu_gpa_to_page() and kmap() will only work for guest
> memory that has a "struct page".
> 
> The life-cycle of the mapping also changes to avoid doing map and unmap on

s/also changes/has been changed/ ?

Follow-Ups:
- Re: [PATCH 05/10] KVM/nVMX: Use kvm_vcpu_map when mapping the L1 MSR bitmap
  - From: Raslan, KarimAllah

References:
- [PATCH 00/10] KVM/X86: Handle guest memory that does not have a struct page
  - From: KarimAllah Ahmed
- [PATCH 05/10] KVM/nVMX: Use kvm_vcpu_map when mapping the L1 MSR bitmap
  - From: KarimAllah Ahmed

Prev by Date: [PATCH] KVM: SVM: no need to call access_ok() in LAUNCH_MEASURE command
Next by Date: [PATCH] KVM: x86: move LAPIC initialization after VMCS creation
Previous by thread: [PATCH 05/10] KVM/nVMX: Use kvm_vcpu_map when mapping the L1 MSR bitmap
Next by thread: Re: [PATCH 05/10] KVM/nVMX: Use kvm_vcpu_map when mapping the L1 MSR bitmap
Index(es):
- Date
- Thread

[Index of Archives] [KVM ARM] [KVM ia64] [KVM ppc] [Virtualization Tools] [Spice Development] [Libvirt] [Libvirt Users] [Linux USB Devel] [Linux Audio Users] [Yosemite Questions] [Linux Kernel] [Linux SCSI] [XFree86]