From: Paolo Bonzini <pbonzini@redhat.com>
To: Bandan Das <bsd@redhat.com>, kvm@vger.kernel.org
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Gleb Natapov <gleb@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 2/3] KVM: x86: use memory_prepare in fetch helper function
Date: Tue, 06 May 2014 10:27:52 +0200 [thread overview]
Message-ID: <53689D08.2070801@redhat.com> (raw)
In-Reply-To: <1399336859-7227-3-git-send-email-bsd@redhat.com>
Il 06/05/2014 02:40, Bandan Das ha scritto:
> Insn fetch fastpath function. Not that
> arch.walk_mmu->gva_to_gpa can't be used but let's
> piggyback on top of interface meant for our purpose
>
> Signed-off-by: Bandan Das <bsd@redhat.com>
> ---
> arch/x86/kvm/x86.c | 25 +++++++++++++++++--------
> 1 file changed, 17 insertions(+), 8 deletions(-)
>
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 17e3d661..cf69e3b 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -4065,29 +4065,38 @@ static int kvm_read_guest_virt_helper(gva_t addr, void *val, unsigned int bytes,
> struct x86_exception *exception)
> {
> void *data = val;
> - struct kvm_vcpu *vcpu = emul_to_vcpu(ctxt);
> int r = X86EMUL_CONTINUE;
>
> while (bytes) {
> - gpa_t gpa = vcpu->arch.walk_mmu->gva_to_gpa(vcpu, addr, access,
> - exception);
> unsigned offset = addr & (PAGE_SIZE-1);
> unsigned toread = min(bytes, (unsigned)PAGE_SIZE - offset);
> int ret;
> + unsigned long uaddr;
>
> - if (gpa == UNMAPPED_GVA)
> - return X86EMUL_PROPAGATE_FAULT;
> - ret = kvm_read_guest(vcpu->kvm, gpa, data, toread);
> + ret = ctxt->ops->memory_prepare(ctxt, addr, toread,
> + exception, false,
> + NULL, &uaddr);
You can call the function from x86.c directly, no need to go through
ctxt->ops.
> + if (ret != X86EMUL_CONTINUE)
> + return ret;
> +
> + if (unlikely(kvm_is_error_hva(uaddr))) {
> + r = X86EMUL_PROPAGATE_FAULT;
> + return r;
> + }
> +
> + ret = __copy_from_user(data, (void __user *)uaddr, toread);
> if (ret < 0) {
> r = X86EMUL_IO_NEEDED;
> - goto out;
> + return r;
> }
>
> + ctxt->ops->memory_finish(ctxt, NULL, uaddr);
No need to call memory_finish, since you know the implementation
(perhaps add a comment).
Paolo
> bytes -= toread;
> data += toread;
> addr += toread;
> }
> -out:
> +
> return r;
> }
>
>
next prev parent reply other threads:[~2014-05-06 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 0:40 [RFC PATCH 0/3] Emulator Speedups - Optimize Instruction fetches Bandan Das
2014-05-06 0:40 ` [RFC PATCH 1/3] KVM: x86: pass ctxt to fetch helper function Bandan Das
2014-05-06 0:40 ` [RFC PATCH 2/3] KVM: x86: use memory_prepare in " Bandan Das
2014-05-06 8:27 ` Paolo Bonzini [this message]
2014-05-06 9:46 ` Paolo Bonzini
2014-05-06 0:40 ` [RFC PATCH 3/3] KVM: x86: cache userspace address for faster fetches Bandan Das
2014-05-06 9:40 ` Paolo Bonzini
2014-05-07 4:45 ` Bandan Das
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=53689D08.2070801@redhat.com \
--to=pbonzini@redhat.com \
--cc=bsd@redhat.com \
--cc=gleb@kernel.org \
--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 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.