From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] KVM call agenda for tuesday 31 Date: Mon, 05 Mar 2012 17:10:33 +0200 Message-ID: <4F54D769.5050000@redhat.com> References: <87ehuhrpel.fsf@elfo.elfo> <4F272A92.2010609@suse.de> <4F272D8C.8020608@codemonkey.ws> <4F27E98E.2080501@suse.de> <4F54C1C0.6030803@samsung.com> <4F54CA04.4070804@redhat.com> <4F54CFA3.6080400@samsung.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Peter Maydell , =?UTF-8?B?QW5kcmVhcyBGw6RyYg==?= =?UTF-8?B?ZXI=?= , Anthony Liguori , quintela@redhat.com, Developers qemu-devel , KVM devel mailing list , Dmitry Solodkiy To: i.mitsyanko@samsung.com Return-path: Received: from mx1.redhat.com ([209.132.183.28]:56123 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964934Ab2CEPKp (ORCPT ); Mon, 5 Mar 2012 10:10:45 -0500 In-Reply-To: <4F54CFA3.6080400@samsung.com> Sender: kvm-owner@vger.kernel.org List-ID: On 03/05/2012 04:37 PM, Igor Mitsyanko wrote: >> Well, can't you make sd.c target dependent? It's not so nice, but it >> does solve the problem. >> > > OK, but it will turn qemu from it's "long term path to suppress *all* > target specific code" :) > The other alternative is to s/target_phys_addr_t/uint64_t/ in the memory API. I think 32-on-32 is quite rare these days, so it wouldn't be much of a performance issue. -- error compiling committee.c: too many arguments to function From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:55218) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S4ZZ7-0002BN-7O for qemu-devel@nongnu.org; Mon, 05 Mar 2012 10:11:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S4ZYf-0007rb-6O for qemu-devel@nongnu.org; Mon, 05 Mar 2012 10:11:08 -0500 Received: from mx1.redhat.com ([209.132.183.28]:48419) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S4ZYe-0007rS-UE for qemu-devel@nongnu.org; Mon, 05 Mar 2012 10:10:41 -0500 Message-ID: <4F54D769.5050000@redhat.com> Date: Mon, 05 Mar 2012 17:10:33 +0200 From: Avi Kivity MIME-Version: 1.0 References: <87ehuhrpel.fsf@elfo.elfo> <4F272A92.2010609@suse.de> <4F272D8C.8020608@codemonkey.ws> <4F27E98E.2080501@suse.de> <4F54C1C0.6030803@samsung.com> <4F54CA04.4070804@redhat.com> <4F54CFA3.6080400@samsung.com> In-Reply-To: <4F54CFA3.6080400@samsung.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] KVM call agenda for tuesday 31 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: i.mitsyanko@samsung.com Cc: Peter Maydell , KVM devel mailing list , quintela@redhat.com, Developers qemu-devel , Dmitry Solodkiy , Anthony Liguori , =?UTF-8?B?QW5kcmVhcyBGw6RyYg==?= =?UTF-8?B?ZXI=?= On 03/05/2012 04:37 PM, Igor Mitsyanko wrote: >> Well, can't you make sd.c target dependent? It's not so nice, but it >> does solve the problem. >> > > OK, but it will turn qemu from it's "long term path to suppress *all* > target specific code" :) > The other alternative is to s/target_phys_addr_t/uint64_t/ in the memory API. I think 32-on-32 is quite rare these days, so it wouldn't be much of a performance issue. -- error compiling committee.c: too many arguments to function