[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <505AF6A6.4070106@redhat.com>
Date: Thu, 20 Sep 2012 13:57:42 +0300
From: Avi Kivity <avi@...hat.com>
To: Xiao Guangrong <xiaoguangrong@...ux.vnet.ibm.com>
CC: Marcelo Tosatti <mtosatti@...hat.com>,
LKML <linux-kernel@...r.kernel.org>, KVM <kvm@...r.kernel.org>
Subject: Re: [PATCH v2 4/5] KVM: MMU: introduce page_fault_start and page_fault_end
On 09/14/2012 12:59 PM, Xiao Guangrong wrote:
> Wrap the common operations into these two functions
>
> Signed-off-by: Xiao Guangrong <xiaoguangrong@...ux.vnet.ibm.com>
> ---
> arch/x86/kvm/mmu.c | 53 +++++++++++++++++++++++++++----------------
> arch/x86/kvm/paging_tmpl.h | 16 +++++--------
> 2 files changed, 39 insertions(+), 30 deletions(-)
>
> diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
> index 29ce28b..7e7b8cd 100644
> --- a/arch/x86/kvm/mmu.c
> +++ b/arch/x86/kvm/mmu.c
> @@ -2825,6 +2825,29 @@ exit:
> static bool try_async_pf(struct kvm_vcpu *vcpu, bool prefault, gfn_t gfn,
> gva_t gva, pfn_t *pfn, bool write, bool *writable);
>
> +static bool
> +page_fault_start(struct kvm_vcpu *vcpu, gfn_t *gfnp, pfn_t *pfnp, int *levelp,
> + bool force_pt_level, unsigned long mmu_seq)
> +{
> + spin_lock(&vcpu->kvm->mmu_lock);
> + if (mmu_notifier_retry(vcpu, mmu_seq))
> + return false;
> +
> + kvm_mmu_free_some_pages(vcpu);
> + if (likely(!force_pt_level))
> + transparent_hugepage_adjust(vcpu, gfnp, pfnp, levelp);
> +
> + return true;
> +}
> +
> +static void page_fault_end(struct kvm_vcpu *vcpu, pfn_t pfn)
> +{
> + spin_unlock(&vcpu->kvm->mmu_lock);
> +
> + if (!is_error_pfn(pfn))
> + kvm_release_pfn_clean(pfn);
> +}
Needs sparse annotations (__acquires, __releases).
These code blocks have nothing in common except for being shared. Often
that's not good for maintainability because it means that further
changes can affect one path but not the other. But we can try it out
and see.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists