From: Avi Kivity <avi@redhat.com>
To: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH 2/7] KVM: MMU: cleanup for error mask set while walk guest page table
Date: Mon, 27 Sep 2010 16:30:22 +0200 [thread overview]
Message-ID: <4CA0AA7E.4090901@redhat.com> (raw)
In-Reply-To: <4CA06BEF.7060401@cn.fujitsu.com>
On 09/27/2010 12:03 PM, Xiao Guangrong wrote:
> Small cleanup for set page fault error code
>
> Xiao Guangrong<xiaoguangrong@cn.fujitsu.com>
> ---
> arch/x86/kvm/paging_tmpl.h | 17 +++++++----------
> 1 files changed, 7 insertions(+), 10 deletions(-)
>
> diff --git a/arch/x86/kvm/paging_tmpl.h b/arch/x86/kvm/paging_tmpl.h
> index 2bdd843..a83ff37 100644
> --- a/arch/x86/kvm/paging_tmpl.h
> +++ b/arch/x86/kvm/paging_tmpl.h
> @@ -224,9 +224,7 @@ walk:
> is_cpuid_PSE36())
> gfn += pse36_gfn_delta(pte);
>
> - access |= write_fault ? PFERR_WRITE_MASK : 0;
> - access |= fetch_fault ? PFERR_FETCH_MASK : 0;
> - access |= user_fault ? PFERR_USER_MASK : 0;
> + access |= write_fault | fetch_fault | user_fault;
>
> real_gpa = mmu->translate_gpa(vcpu, gfn_to_gpa(gfn),
> access);
> @@ -268,10 +266,9 @@ error:
> walker->error_code = 0;
> if (present)
> walker->error_code |= PFERR_PRESENT_MASK;
> - if (write_fault)
> - walker->error_code |= PFERR_WRITE_MASK;
> - if (user_fault)
> - walker->error_code |= PFERR_USER_MASK;
> +
> + walker->error_code |= write_fault | user_fault;
> +
> if (fetch_fault&& mmu->nx)
> walker->error_code |= PFERR_FETCH_MASK;
> if (rsvd_fault)
> @@ -673,9 +670,9 @@ static gpa_t FNAME(gva_to_gpa)(struct kvm_vcpu *vcpu, gva_t vaddr, u32 access,
> int r;
>
> r = FNAME(walk_addr)(&walker, vcpu, vaddr,
> - !!(access& PFERR_WRITE_MASK),
> - !!(access& PFERR_USER_MASK),
> - !!(access& PFERR_FETCH_MASK));
> + access& PFERR_WRITE_MASK,
> + access& PFERR_USER_MASK,
> + access& PFERR_FETCH_MASK);
>
> if (r) {
> gpa = gfn_to_gpa(walker.gfn);
Interesting. Maybe a next step is to pass the page-fault error code
instead of the various bits? Not sure how that interacts with nested
ept (which has a different permission model).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-09-27 14:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 10:02 [PATCH 1/7] KVM: MMU: update 'root_hpa' out of loop in PAE shadow path Xiao Guangrong
2010-09-27 10:03 ` [PATCH 2/7] KVM: MMU: cleanup for error mask set while walk guest page table Xiao Guangrong
2010-09-27 14:30 ` Avi Kivity [this message]
2010-09-28 8:58 ` Xiao Guangrong
2010-09-28 9:00 ` Avi Kivity
2010-09-27 10:05 ` [PATCH 3/7] KVM: MMU: set access bit for direct mapping Xiao Guangrong
2010-09-27 10:07 ` [PATCH 5/7] KVM: MMU: audit: unregister audit tracepoints before module unloaded Xiao Guangrong
2010-09-27 10:07 ` [PATCH 6/7] KVM: MMU: audit: introduce audit_printk to cleanup audit code Xiao Guangrong
2010-09-27 10:09 ` [PATCH 7/7] KVM: MMU: audit: check whether have unsync sps after root sync Xiao Guangrong
2010-09-27 10:14 ` [PATCH 1/7] KVM: MMU: update 'root_hpa' out of loop in PAE shadow path Xiao Guangrong
2010-09-27 10:16 ` Avi Kivity
2010-09-27 14:39 ` Avi Kivity
2010-09-28 2:43 ` Xiao Guangrong
2010-09-28 9:03 ` 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=4CA0AA7E.4090901@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=xiaoguangrong@cn.fujitsu.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