From: Avi Kivity <avi@qumranet.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [patch 2/5] KVM: hypercall based pte updates and TLB flushes
Date: Sun, 17 Feb 2008 10:32:34 +0200 [thread overview]
Message-ID: <47B7F122.7080005@qumranet.com> (raw)
In-Reply-To: <20080216221220.843135254@redhat.com>>
Marcelo Tosatti wrote:
> Hypercall based pte updates are faster than faults, and also allow use
> of the lazy MMU mode to batch operations.
>
> Don't report the feature if two dimensional paging is enabled.
>
> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
> Cc: Anthony Liguori <aliguori@us.ibm.com>
>
> +static int kvm_hypercall_mmu_write(struct kvm_vcpu *vcpu, gva_t addr,
> + unsigned long size, unsigned long a0,
> + unsigned long a1)
> +{
> + gpa_t gpa;
> + u64 value;
> +
> + if (mmu_topup_memory_caches(vcpu))
> + return -KVM_EFAULT;
> +
> + down_read(&vcpu->kvm->slots_lock);
> + gpa = vcpu->arch.mmu.gva_to_gpa(vcpu, addr);
> + up_read(&vcpu->kvm->slots_lock);
> +
> + if (gpa == UNMAPPED_GVA)
> + return -KVM_EFAULT;
> + if (size == 1) {
> + if (!emulator_write_phys(vcpu, gpa, &a0, sizeof(a0)))
> + return -KVM_EFAULT;
> + } else if (size == 2) {
> + if (!is_long_mode(vcpu) && is_pae(vcpu))
> + value = (u64)a1 << 32 | a0;
> + else
> + value = a0;
> + if (!emulator_write_phys(vcpu, gpa, &value, sizeof(value)))
> + return -KVM_EFAULT;
>
The size logic can be simplified if it is redefined to mean "size in
guest longs". Actually, it can be inferred from the guest mode, and a1
is only required iff the guest is a 32-bit pae.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-02-17 8:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080216220924.733723618@redhat.com>
2008-02-16 22:09 ` [patch 1/5] KVM: add basic paravirt support Marcelo Tosatti
2008-02-16 22:09 ` [patch 2/5] KVM: hypercall based pte updates and TLB flushes Marcelo Tosatti
2008-02-16 22:09 ` [patch 3/5] KVM: hypercall batching Marcelo Tosatti
2008-02-16 22:09 ` [patch 4/5] KVM: ignore zapped root pagetables Marcelo Tosatti
2008-02-16 22:09 ` [patch 5/5] KVM: VMX cr3 cache support Marcelo Tosatti
2008-02-16 23:37 ` [patch 0/5] KVM paravirt MMU updates and cr3 caching Anthony Liguori
2008-02-17 2:24 ` Marcelo Tosatti
[not found] ` <20080216221220.843135254@redhat.com>
2008-02-17 8:28 ` [patch 2/5] KVM: hypercall based pte updates and TLB flushes Avi Kivity
2008-02-17 13:13 ` Avi Kivity
2008-02-17 14:51 ` Marcelo Tosatti
2008-02-17 14:57 ` Avi Kivity
2008-02-18 5:00 ` Marcelo Tosatti
2008-02-17 8:32 ` Avi Kivity [this message]
[not found] ` <20080216221221.002948712@redhat.com>
2008-02-17 8:52 ` [patch 4/5] KVM: ignore zapped root pagetables Avi Kivity
[not found] ` <20080216221220.924823582@redhat.com>
2008-02-17 8:40 ` [patch 3/5] KVM: hypercall batching Avi Kivity
2008-02-18 16:47 ` Marcelo Tosatti
2008-02-17 18:40 ` Hollis Blanchard
2008-02-18 8:06 ` Avi Kivity
2008-02-18 8:43 ` Christian Borntraeger
2008-02-18 8:47 ` Avi Kivity
[not found] ` <1203361276.3428.6.camel@basalt>
2008-02-19 8:30 ` Avi Kivity
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=47B7F122.7080005@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--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