From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 0/5] mmu root page cleanups
Date: Mon, 26 Apr 2010 12:23:26 +0300 [thread overview]
Message-ID: <4BD55B8E.5080606@redhat.com> (raw)
In-Reply-To: <1272271723-9070-1-git-send-email-avi@redhat.com>
On 04/26/2010 11:48 AM, Avi Kivity wrote:
> I tried to separate direct and indirect page allocation to reduce memory
> usage with tdp, but that turned out too messy (and not much of a win - we
> allocate 8K per page outside the struct kvm_mmu_page). However the cleanups
> on the way are worthwhile.
>
Breaks during testing, please don't apply.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-04-26 9:23 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 ` [PATCH 2/5] KVM: MMU: use 16 bits for root_count Avi Kivity
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 ` 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=4BD55B8E.5080606@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