From: Marcelo Tosatti <mtosatti@redhat.com>
To: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
Cc: Gleb Natapov <gleb@redhat.com>,
LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH v4 3/5] KVM: x86: clean up reexecute_instruction
Date: Fri, 4 Jan 2013 20:21:35 -0200 [thread overview]
Message-ID: <20130104222135.GA13481@amt.cnet> (raw)
In-Reply-To: <50E6DF5C.2000103@linux.vnet.ibm.com>
On Fri, Jan 04, 2013 at 09:55:40PM +0800, Xiao Guangrong wrote:
> Little cleanup for reexecute_instruction, also use gpa_to_gfn in
> retry_instruction
>
> Signed-off-by: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
> ---
> arch/x86/kvm/x86.c | 13 ++++++-------
> 1 files changed, 6 insertions(+), 7 deletions(-)
>
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 1c9c834..ad39018 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -4761,19 +4761,18 @@ static bool reexecute_instruction(struct kvm_vcpu *vcpu, gva_t gva)
> if (tdp_enabled)
> return false;
>
> + gpa = kvm_mmu_gva_to_gpa_read(vcpu, gva, NULL);
> + if (gpa == UNMAPPED_GVA)
> + return true; /* let cpu generate fault */
> +
Why change from _system to _read here? Purely cleanup patch should
have no logical changes.
BTW, there is not much logic in using reexecute_instruction() at
for x86_decode_insn (checks in reexecute_instruction() assume
write to the cr2, for instance).
Fault propagation for x86_decode_insn seems completly broken
(which is perhaps why reexecute_instruction() there survived).
> /*
> * if emulation was due to access to shadowed page table
> * and it failed try to unshadow page and re-enter the
> * guest to let CPU execute the instruction.
> */
> - if (kvm_mmu_unprotect_page_virt(vcpu, gva))
> + if (kvm_mmu_unprotect_page(vcpu->kvm, gpa_to_gfn(gpa)))
> return true;
>
> - gpa = kvm_mmu_gva_to_gpa_system(vcpu, gva, NULL);
> -
> - if (gpa == UNMAPPED_GVA)
> - return true; /* let cpu generate fault */
> -
> /*
> * Do not retry the unhandleable instruction if it faults on the
> * readonly host memory, otherwise it will goto a infinite loop:
> @@ -4828,7 +4827,7 @@ static bool retry_instruction(struct x86_emulate_ctxt *ctxt,
> if (!vcpu->arch.mmu.direct_map)
> gpa = kvm_mmu_gva_to_gpa_write(vcpu, cr2, NULL);
>
> - kvm_mmu_unprotect_page(vcpu->kvm, gpa >> PAGE_SHIFT);
> + kvm_mmu_unprotect_page(vcpu->kvm, gpa_to_gfn(gpa));
>
> return true;
> }
> --
> 1.7.7.6
next prev parent reply other threads:[~2013-01-04 22:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 13:53 [PATCH v4 0/5] KVM: x86: improve reexecute_instruction Xiao Guangrong
2013-01-04 13:54 ` [PATCH v4 1/5] KVM: MMU: fix Dirty bit missed if CR0.WP = 0 Xiao Guangrong
2013-01-04 13:54 ` [PATCH v4 2/5] KVM: MMU: fix infinite fault access retry Xiao Guangrong
2013-01-04 13:55 ` [PATCH v4 3/5] KVM: x86: clean up reexecute_instruction Xiao Guangrong
2013-01-04 22:21 ` Marcelo Tosatti [this message]
2013-01-05 7:20 ` Xiao Guangrong
2013-01-04 13:56 ` [PATCH v4 4/5] KVM: x86: let reexecute_instruction work for tdp Xiao Guangrong
2013-01-04 13:56 ` [PATCH v4 5/5] KVM: x86: improve reexecute_instruction Xiao Guangrong
2013-01-04 22:44 ` Marcelo Tosatti
2013-01-05 8:16 ` Xiao Guangrong
2013-01-07 20:46 ` 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=20130104222135.GA13481@amt.cnet \
--to=mtosatti@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiaoguangrong@linux.vnet.ibm.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