From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 0/4] KVM: Introduce kvm_memory_slot::arch Date: Mon, 06 Feb 2012 12:10:55 +0200 Message-ID: <4F2FA72F.9000209@redhat.com> References: <20120130124859.6c3bb19f.yoshikawa.takuya@oss.ntt.co.jp> <4F2FA71A.1010102@oss.ntt.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: mtosatti@redhat.com, kvm@vger.kernel.org To: Takuya Yoshikawa Return-path: Received: from mx1.redhat.com ([209.132.183.28]:52526 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752558Ab2BFKK7 (ORCPT ); Mon, 6 Feb 2012 05:10:59 -0500 In-Reply-To: <4F2FA71A.1010102@oss.ntt.co.jp> Sender: kvm-owner@vger.kernel.org List-ID: On 02/06/2012 12:10 PM, Takuya Yoshikawa wrote: > (2012/01/30 12:48), Takuya Yoshikawa wrote: >> This is the first step to separate the architecture specific members. >> The rmap and dirty_bitmap can be treated later based on this. > > > Any further comments? > > > If patch 4 (v3) looks controversial, please consider taking > patch 1 to 3. > No, patch 4 seems fine. I was just waiting for more comments, and now it's Marcelo's turn on kvm.git. > I may use gfn_to_index() for dirty logging. > > -- error compiling committee.c: too many arguments to function