public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: kvm@vger.kernel.org
Cc: Marcelo Tosatti <mtosatti@redhat.com>
Subject: [PATCH 0/5] for_each_shadow_entry
Date: Thu, 25 Dec 2008 15:23:34 +0200	[thread overview]
Message-ID: <1230211419-2389-1-git-send-email-avi@redhat.com> (raw)

This patchset replaces walk_shadow(), which calls a callback for each
shadow pte that maps a guest virtal address, by an equivalent for_each style
construct.  Benefits are less thunks and smaller code.

Please review.

Avi Kivity (5):
  KVM: MMU: Add for_each_shadow_entry(), a simpler alternative to
    walk_shadow()
  KVM: MMU: Use for_each_shadow_entry() in __direct_map()
  KVM: MMU: Replace walk_shadow() by for_each_shadow_entry() in fetch()
  KVM: MMU: Replace walk_shadow() by for_each_shadow_entry() in
    invlpg()
  KVM: MMU: Drop walk_shadow()

 arch/x86/kvm/mmu.c         |  150 ++++++++++++++-----------------
 arch/x86/kvm/paging_tmpl.h |  209 +++++++++++++++++++-------------------------
 2 files changed, 157 insertions(+), 202 deletions(-)


             reply	other threads:[~2008-12-25 13:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-25 13:23 Avi Kivity [this message]
2008-12-25 13:23 ` [PATCH 1/5] KVM: MMU: Add for_each_shadow_entry(), a simpler alternative to walk_shadow() Avi Kivity
2008-12-25 13:23 ` [PATCH 2/5] KVM: MMU: Use for_each_shadow_entry() in __direct_map() Avi Kivity
2008-12-25 13:23 ` [PATCH 3/5] KVM: MMU: Replace walk_shadow() by for_each_shadow_entry() in fetch() Avi Kivity
2008-12-25 13:23 ` [PATCH 4/5] KVM: MMU: Replace walk_shadow() by for_each_shadow_entry() in invlpg() Avi Kivity
2008-12-25 13:23 ` [PATCH 5/5] KVM: MMU: Drop walk_shadow() Avi Kivity
2008-12-27 23:25 ` [PATCH 0/5] for_each_shadow_entry Marcelo Tosatti
2008-12-28  9:00   ` 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=1230211419-2389-1-git-send-email-avi@redhat.com \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox