From: Avi Kivity <avi@redhat.com>
To: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
Cc: mtosatti@redhat.com, kvm@vger.kernel.org,
yoshikawa.takuya@oss.ntt.co.jp, mingo@elte.hu
Subject: Re: [PATCH 3/3] KVM: MMU: Use helpers to clean up walk_addr_generic()
Date: Mon, 20 Jun 2011 15:02:07 +0300 [thread overview]
Message-ID: <4DFF36BF.7030304@redhat.com> (raw)
In-Reply-To: <20110615020343.991f0b86.takuya.yoshikawa@gmail.com>
On 06/14/2011 08:03 PM, Takuya Yoshikawa wrote:
> From: Takuya Yoshikawa<yoshikawa.takuya@oss.ntt.co.jp>
>
> Introduce two new helpers: set_accessed_bit() and is_last_gpte().
>
> These names were suggested by Ingo and Avi.
>
> Cc: Ingo Molnar<mingo@elte.hu>
> Signed-off-by: Takuya Yoshikawa<yoshikawa.takuya@oss.ntt.co.jp>
> ---
> arch/x86/kvm/paging_tmpl.h | 57 ++++++++++++++++++++++++++++++++-----------
> 1 files changed, 42 insertions(+), 15 deletions(-)
>
> diff --git a/arch/x86/kvm/paging_tmpl.h b/arch/x86/kvm/paging_tmpl.h
> index 92fe275..d655a4b6 100644
> --- a/arch/x86/kvm/paging_tmpl.h
> +++ b/arch/x86/kvm/paging_tmpl.h
> @@ -113,6 +113,43 @@ static unsigned FNAME(gpte_access)(struct kvm_vcpu *vcpu, pt_element_t gpte)
> return access;
> }
>
> +static int FNAME(set_accessed_bit)(struct kvm_vcpu *vcpu, struct kvm_mmu *mmu,
> + gfn_t table_gfn, unsigned index,
> + pt_element_t __user *ptep_user,
> + pt_element_t *ptep)
> +{
> + int ret;
> +
> + trace_kvm_mmu_set_accessed_bit(table_gfn, index, sizeof(*ptep));
> + ret = FNAME(cmpxchg_gpte)(vcpu, mmu, ptep_user, index,
> + *ptep, *ptep|PT_ACCESSED_MASK);
> + if (unlikely(ret))
> + return ret;
> +
> + mark_page_dirty(vcpu->kvm, table_gfn);
> + *ptep |= PT_ACCESSED_MASK;
> +
> + return 0;
> +}
I don't think this one is worthwhile, it takes 7 parameters! If there's
so much communication between caller and callee, it means they are too
heavily tied up.
> +
> +static bool FNAME(is_last_gpte)(struct guest_walker *walker,
> + struct kvm_vcpu *vcpu, struct kvm_mmu *mmu,
> + pt_element_t gpte)
> +{
> + if (walker->level == PT_PAGE_TABLE_LEVEL)
> + return true;
> +
> + if ((walker->level == PT_DIRECTORY_LEVEL)&& is_large_pte(gpte)&&
> + (PTTYPE == 64 || is_pse(vcpu)))
> + return true;
> +
> + if ((walker->level == PT_PDPE_LEVEL)&& is_large_pte(gpte)&&
> + (mmu->root_level == PT64_ROOT_LEVEL))
> + return true;
> +
> + return false;
> +}
> +
This one is much better.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-06-20 12:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 17:00 [PATCH v2 1/3] KVM: MMU: Clean up the error handling of walk_addr_generic() Takuya Yoshikawa
2011-06-14 17:02 ` [PATCH 2/3] KVM: MMU: Rename the walk label in walk_addr_generic() Takuya Yoshikawa
2011-06-14 17:03 ` [PATCH 3/3] KVM: MMU: Use helpers to clean up walk_addr_generic() Takuya Yoshikawa
2011-06-20 12:02 ` Avi Kivity [this message]
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=4DFF36BF.7030304@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.com \
--cc=takuya.yoshikawa@gmail.com \
--cc=yoshikawa.takuya@oss.ntt.co.jp \
/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