From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org
Subject: [PATCH 2/5] KVM: MMU: use 16 bits for root_count
Date: Mon, 26 Apr 2010 11:48:40 +0300 [thread overview]
Message-ID: <1272271723-9070-3-git-send-email-avi@redhat.com> (raw)
In-Reply-To: <1272271723-9070-1-git-send-email-avi@redhat.com>
This is incremented by a maximum of 4 for every vcpu, so we are far from
overflow. 16 bits improve struct packing.
Signed-off-by: Avi Kivity <avi@redhat.com>
---
arch/x86/include/asm/kvm_host.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h
index cdaaedc..f38007d 100644
--- a/arch/x86/include/asm/kvm_host.h
+++ b/arch/x86/include/asm/kvm_host.h
@@ -192,7 +192,7 @@ struct kvm_mmu_page {
*/
gfn_t gfn;
union kvm_mmu_page_role role;
- int root_count; /* Currently serving as active root */
+ short root_count; /* Currently serving as active root */
bool multimapped; /* More than one parent_pte? */
bool unsync;
union {
--
1.7.0.4
next prev parent reply other threads:[~2010-04-26 8:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 8:48 [PATCH 0/5] mmu root page cleanups Avi Kivity
2010-04-26 8:48 ` [PATCH 1/5] KVM: MMU: Rearrange struct kvm_mmu_page Avi Kivity
2010-04-26 8:48 ` Avi Kivity [this message]
2010-04-26 8:48 ` [PATCH 3/5] KVM: MMU: Unify 32-pae and single-root mmu setup Avi Kivity
2010-04-26 8:48 ` [PATCH 4/5] KVM: MMU: Use correct root gfn for direct maps Avi Kivity
2010-04-26 8:48 ` [PATCH 5/5] KVM: MMU: Fix check for cr3 outside guest memory Avi Kivity
2010-04-26 9:23 ` [PATCH 0/5] mmu root page cleanups 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=1272271723-9070-3-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 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.