From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>,
LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH v5 5/5] KVM: x86: improve reexecute_instruction
Date: Fri, 11 Jan 2013 02:16:11 +0800 [thread overview]
Message-ID: <50EF056B.4040803@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130110173036.GB24703@amt.cnet>
On 01/11/2013 01:30 AM, Marcelo Tosatti wrote:
> On Tue, Jan 08, 2013 at 02:38:36PM +0800, Xiao Guangrong wrote:
>> The current reexecute_instruction can not well detect the failed instruction
>> emulation. It allows guest to retry all the instructions except it accesses
>> on error pfn
>>
>> For example, some cases are nested-write-protect - if the page we want to
>> write is used as PDE but it chains to itself. Under this case, we should
>> stop the emulation and report the case to userspace
>>
>> Signed-off-by: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
>> ---
>> arch/x86/include/asm/kvm_host.h | 7 +++++++
>> arch/x86/kvm/paging_tmpl.h | 27 ++++++++++++++++++++-------
>> arch/x86/kvm/x86.c | 8 +++++++-
>> 3 files changed, 34 insertions(+), 8 deletions(-)
>>
>> diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h
>> index c431b33..d6ab8d2 100644
>> --- a/arch/x86/include/asm/kvm_host.h
>> +++ b/arch/x86/include/asm/kvm_host.h
>> @@ -502,6 +502,13 @@ struct kvm_vcpu_arch {
>> u64 msr_val;
>> struct gfn_to_hva_cache data;
>> } pv_eoi;
>> +
>> + /*
>> + * Indicate whether the access faults on its page table in guest
>> + * which is set when fix page fault and used to detect unhandeable
>> + * instruction.
>> + */
>> + bool write_fault_to_shadow_pgtable;
>> };
>>
>> struct kvm_lpage_info {
>> diff --git a/arch/x86/kvm/paging_tmpl.h b/arch/x86/kvm/paging_tmpl.h
>> index 67b390d..df50560 100644
>> --- a/arch/x86/kvm/paging_tmpl.h
>> +++ b/arch/x86/kvm/paging_tmpl.h
>> @@ -497,26 +497,34 @@ out_gpte_changed:
>> * created when kvm establishes shadow page table that stop kvm using large
>> * page size. Do it early can avoid unnecessary #PF and emulation.
>> *
>> + * @write_fault_to_shadow_pgtable will return true if the fault gfn is
>> + * currently used as its page table.
>> + *
>> * Note: the PDPT page table is not checked for PAE-32 bit guest. It is ok
>> * since the PDPT is always shadowed, that means, we can not use large page
>> * size to map the gfn which is used as PDPT.
>> */
>> static bool
>> FNAME(is_self_change_mapping)(struct kvm_vcpu *vcpu,
>> - struct guest_walker *walker, int user_fault)
>> + struct guest_walker *walker, int user_fault,
>> + bool *write_fault_to_shadow_pgtable)
>> {
>> int level;
>> gfn_t mask = ~(KVM_PAGES_PER_HPAGE(walker->level) - 1);
>> + bool self_changed = false;
>>
>> if (!(walker->pte_access & ACC_WRITE_MASK ||
>> (!is_write_protection(vcpu) && !user_fault)))
>> return false;
>>
>> - for (level = walker->level; level <= walker->max_level; level++)
>> - if (!((walker->gfn ^ walker->table_gfn[level - 1]) & mask))
>> - return true;
>> + for (level = walker->level; level <= walker->max_level; level++) {
>> + gfn_t gfn = walker->gfn ^ walker->table_gfn[level - 1];
>> +
>> + self_changed |= !(gfn & mask);
>> + *write_fault_to_shadow_pgtable |= !gfn;
>> + }
>>
>> - return false;
>> + return self_changed;
>> }
>>
>> /*
>> @@ -544,7 +552,7 @@ static int FNAME(page_fault)(struct kvm_vcpu *vcpu, gva_t addr, u32 error_code,
>> int level = PT_PAGE_TABLE_LEVEL;
>> int force_pt_level;
>> unsigned long mmu_seq;
>> - bool map_writable;
>> + bool map_writable, is_self_change_mapping;
>>
>> pgprintk("%s: addr %lx err %x\n", __func__, addr, error_code);
>>
>> @@ -572,9 +580,14 @@ static int FNAME(page_fault)(struct kvm_vcpu *vcpu, gva_t addr, u32 error_code,
>> return 0;
>> }
>>
>> + vcpu->arch.write_fault_to_shadow_pgtable = false;
>> +
>> + is_self_change_mapping = FNAME(is_self_change_mapping)(vcpu,
>> + &walker, user_fault, &vcpu->arch.write_fault_to_shadow_pgtable);
>> +
>> if (walker.level >= PT_DIRECTORY_LEVEL)
>> force_pt_level = mapping_level_dirty_bitmap(vcpu, walker.gfn)
>> - || FNAME(is_self_change_mapping)(vcpu, &walker, user_fault);
>> + || is_self_change_mapping;
>> else
>> force_pt_level = 1;
>> if (!force_pt_level) {
>> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
>> index 6f13e03..2957012 100644
>> --- a/arch/x86/kvm/x86.c
>> +++ b/arch/x86/kvm/x86.c
>> @@ -4810,7 +4810,13 @@ static bool reexecute_instruction(struct kvm_vcpu *vcpu, gva_t cr2)
>> * guest to let CPU execute the instruction.
>> */
>> kvm_mmu_unprotect_page(vcpu->kvm, gpa_to_gfn(gpa));
>> - return true;
>> +
>> + /*
>> + * If the access faults on its page table, it can not
>> + * be fixed by unprotecting shadow page and it should
>> + * be reported to userspace.
>> + */
>> + return !vcpu->arch.write_fault_to_shadow_pgtable;
>> }
>>
>> static bool retry_instruction(struct x86_emulate_ctxt *ctxt,
>
> Also should make sure vcpu->arch.write_fault_to_shadow_pgtable is never
> reused. Say, clean when exiting x86_emulate_instruction?
Yes, it is more clear.
But i am thinking if it is really needed because 'cr2' is only valid when it
is called on page fault path, vcpu->arch.write_fault_to_shadow_pgtable is reset
at the beginning of page-fault path.
For other paths, cr2 is always 0 which is always 'NULL' pointer and not mapped
on guest, reexecute_instruction will always return true:
gpa = kvm_mmu_gva_to_gpa_write(vcpu, cr2, NULL);
/*
* If the mapping is invalid in guest, let cpu retry
* it to generate fault.
*/
if (gpa == UNMAPPED_GVA)
return true;
next prev parent reply other threads:[~2013-01-10 18:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 6:36 [PATCH v5 1/5] KVM: MMU: fix Dirty bit missed if CR0.WP = 0 Xiao Guangrong
2013-01-08 6:36 ` [PATCH v5 2/5] KVM: MMU: fix infinite fault access retry Xiao Guangrong
2013-01-08 6:37 ` [PATCH v5 3/5] KVM: x86: clean up reexecute_instruction Xiao Guangrong
2013-01-08 6:37 ` [PATCH v5 4/5] KVM: x86: let reexecute_instruction work for tdp Xiao Guangrong
2013-01-08 6:38 ` [PATCH v5 5/5] KVM: x86: improve reexecute_instruction Xiao Guangrong
2013-01-10 17:26 ` Marcelo Tosatti
2013-01-10 18:05 ` Xiao Guangrong
2013-01-10 19:48 ` Marcelo Tosatti
2013-01-10 20:18 ` Xiao Guangrong
2013-01-11 13:15 ` Marcelo Tosatti
2013-01-10 17:30 ` Marcelo Tosatti
2013-01-10 17:38 ` Gleb Natapov
2013-01-10 18:16 ` Xiao Guangrong [this message]
2013-01-11 13:15 ` Marcelo Tosatti
2013-01-11 14:12 ` [PATCH v5 6/5] KVM: x86: clear write_fault_to_shadow_pgtable explicitly Xiao Guangrong
2013-01-11 19:09 ` Marcelo Tosatti
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=50EF056B.4040803@linux.vnet.ibm.com \
--to=xiaoguangrong@linux.vnet.ibm.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@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