From: Paul Mackerras <paulus@samba.org>
To: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
Cc: avi@redhat.com, mtosatti@redhat.com, agraf@suse.de,
kvm@vger.kernel.org, kvm-ppc@vger.kernel.org
Subject: Re: [RFC PATCH 3/3] KVM: Push rmap into kvm_arch_memory_slot
Date: Fri, 3 Aug 2012 09:59:15 +1000 [thread overview]
Message-ID: <20120802235915.GA12559@bloggs.ozlabs.ibm.com> (raw)
In-Reply-To: <20120801180328.d5b48ef3.yoshikawa.takuya@oss.ntt.co.jp>
On Wed, Aug 01, 2012 at 06:03:28PM +0900, Takuya Yoshikawa wrote:
> Two reasons:
> - x86 can integrate rmap and rmap_pde and remove heuristics in
> __gfn_to_rmap().
> - Some architectures do not need rmap.
>
> Since rmap is one of the most memory consuming stuff in KVM, ppc'd
> better restrict the allocation to Book3S HV.
>
> Signed-off-by: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
> Cc: Paul Mackerras <paulus@samba.org>
Looks like a worthwhile change. I do have some patches in preparation
that will intersect with this, but I can manage that once these
patches go upstream.
Acked-by: Paul Mackerras <paulus@samba.org>
next prev parent reply other threads:[~2012-08-02 23:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 8:59 [PATCH 0/3] KVM: Integrate rmap and rmap_pde Takuya Yoshikawa
2012-08-01 9:01 ` [PATCH 1/3] KVM: Stop checking rmap to see if slot is being created Takuya Yoshikawa
2012-08-01 9:02 ` [PATCH 2/3] KVM: MMU: Use gfn_to_rmap() instead of directly reading rmap array Takuya Yoshikawa
2012-08-01 9:03 ` [RFC PATCH 3/3] KVM: Push rmap into kvm_arch_memory_slot Takuya Yoshikawa
2012-08-02 23:59 ` Paul Mackerras [this message]
2012-08-02 12:22 ` [PATCH 0/3] KVM: Integrate rmap and rmap_pde Avi Kivity
2012-08-06 9:47 ` 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=20120802235915.GA12559@bloggs.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=yoshikawa.takuya@oss.ntt.co.jp \
/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;
as well as URLs for NNTP newsgroup(s).