From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH v3 10/10] KVM: MMU: Eliminate pointless temporary 'ac'
Date: Thu, 20 Sep 2012 11:33:17 +0800 [thread overview]
Message-ID: <505A8E7D.1040806@linux.vnet.ibm.com> (raw)
In-Reply-To: <1348072617-23575-11-git-send-email-avi@redhat.com>
On 09/20/2012 12:36 AM, Avi Kivity wrote:
> 'ac' essentially reconstructs the 'access' variable we already
> have, except for the PFERR_PRESENT_MASK and PFERR_RSVD_MASK. As
> these are not used by callees, just use 'access' directly.
>
Reviewed-by: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
prev parent reply other threads:[~2012-09-20 3:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 16:36 [PATCH v3 00/10] Optimize page table walk Avi Kivity
2012-09-19 16:36 ` [PATCH v3 01/10] KVM: MMU: Push clean gpte write protection out of gpte_access() Avi Kivity
2012-09-19 16:36 ` [PATCH v3 02/10] KVM: MMU: Optimize gpte_access() slightly Avi Kivity
2012-09-19 16:36 ` [PATCH v3 03/10] KVM: MMU: Move gpte_access() out of paging_tmpl.h Avi Kivity
2012-09-19 16:36 ` [PATCH v3 04/10] KVM: MMU: Update accessed and dirty bits after guest pagetable walk Avi Kivity
2012-09-19 16:36 ` [PATCH v3 05/10] KVM: MMU: Optimize pte permission checks Avi Kivity
2012-09-19 16:36 ` [PATCH v3 06/10] KVM: MMU: Simplify walk_addr_generic() loop Avi Kivity
2012-09-19 16:36 ` [PATCH v3 07/10] KVM: MMU: Optimize is_last_gpte() Avi Kivity
2012-09-19 16:36 ` [PATCH v3 08/10] KVM: MMU: Eliminate eperm temporary Avi Kivity
2012-09-19 16:36 ` [PATCH v3 09/10] KVM: MMU: Avoid access/dirty update loop if all is well Avi Kivity
2012-09-19 16:36 ` [PATCH v3 10/10] KVM: MMU: Eliminate pointless temporary 'ac' Avi Kivity
2012-09-20 3:33 ` Xiao Guangrong [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=505A8E7D.1040806@linux.vnet.ibm.com \
--to=xiaoguangrong@linux.vnet.ibm.com \
--cc=avi@redhat.com \
--cc=kvm@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.