From: Avi Kivity <avi@redhat.com>
To: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
Cc: mtosatti@redhat.com, kvm@vger.kernel.org, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 0/4] KVM: Decouple rmap_pde from lpage_info write_count
Date: Tue, 24 Jan 2012 13:24:56 +0200 [thread overview]
Message-ID: <4F1E9508.6010205@redhat.com> (raw)
In-Reply-To: <20120123194204.268410c4.yoshikawa.takuya@oss.ntt.co.jp>
On 01/23/2012 12:42 PM, Takuya Yoshikawa wrote:
> The last one is an RFC patch:
>
> I think it is better to refactor the rmap things, if needed, before
> other architectures than x86 starts large pages support.
>
Not commenting about the meat of the patches (not sufficiently recovered
yet), but other architectures may not want the write_count stuff at all,
or even kvm_memory_slot::rmap. It may make sense to move those members
into a new kvm_memory_slot::arch arch-specific substructure.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-01-24 11:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 10:42 [PATCH 0/4] KVM: Decouple rmap_pde from lpage_info write_count Takuya Yoshikawa
2012-01-23 10:43 ` [PATCH 1/4] KVM: MMU: Use gfn_to_rmap() in audit_write_protection() Takuya Yoshikawa
2012-01-23 10:43 ` [PATCH 2/4] KVM: MMU: Use __gfn_to_rmap() in kvm_handle_hva() Takuya Yoshikawa
2012-01-23 10:44 ` [PATCH 3/4] KVM: Introduce gfn_to_index() which returns the index for a given level Takuya Yoshikawa
2012-01-23 10:45 ` [RFC PATCH 4/4] KVM: Decouple rmap_pde from lpage_info write_count Takuya Yoshikawa
2012-01-23 18:40 ` [PATCH 0/4] " Marcelo Tosatti
2012-01-24 11:24 ` Avi Kivity [this message]
2012-01-24 14:35 ` Takuya Yoshikawa
2012-01-25 6:20 ` Takuya Yoshikawa
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=4F1E9508.6010205@redhat.com \
--to=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