From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:47437) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ScC5J-0006T5-01 for qemu-devel@nongnu.org; Wed, 06 Jun 2012 04:59:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ScC5B-0002jF-KS for qemu-devel@nongnu.org; Wed, 06 Jun 2012 04:59:20 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55659) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ScC5B-0002is-Bz for qemu-devel@nongnu.org; Wed, 06 Jun 2012 04:59:13 -0400 Message-ID: <4FCF1BD8.4030307@redhat.com> Date: Wed, 06 Jun 2012 11:59:04 +0300 From: Avi Kivity MIME-Version: 1.0 References: <1338858018-17189-1-git-send-email-mdroth@linux.vnet.ibm.com> <1338858018-17189-2-git-send-email-mdroth@linux.vnet.ibm.com> <4FCDDA12.4040907@redhat.com> <4FCE9B88.2080908@us.ibm.com> <4FCF0AA0.5090105@redhat.com> <4FCF148E.8000104@us.ibm.com> <4FCF16BB.9010804@redhat.com> <4FCF18AC.3080005@us.ibm.com> In-Reply-To: <4FCF18AC.3080005@us.ibm.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 01/17] qidl: add QEMU IDL processor List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: yamahata@valinux.co.jp, quintela@redhat.com, Michael Roth , qemu-devel@nongnu.org, owasserm@redhat.com, pbonzini@redhat.com, akong@redhat.com, afaerber@suse.de On 06/06/2012 11:45 AM, Anthony Liguori wrote: >> Ok. But then the backend pointer is not 'const Backend * const', it's >> 'Backend * const' (if we don't allow retargeting). So we can't say it's >> _immutable (and it isn't). It's _host. > > 'Backend * const' is immutable > > That is, the *pointer* is immutable. What it points to is not. So, is it reasonable to say uint32_t * _immutable irrp; // Interrupt Request Register and allocate it on the heap during initialization? > > If you want to '#define _host _immutable' as a way to improve > readability, I'm not against that. But from a conceptional perspective, > we don't migrate it because nothing the guest does changes it. It's > immutable from the guests PoV. It's not only immutable from the guest point of view, it's unreadable as well. That's what _host means -- it doesn't exist as far as the guest is concerned. IMO that's different than immutable. -- error compiling committee.c: too many arguments to function