From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=39454 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q7NLP-00068E-AK for qemu-devel@nongnu.org; Wed, 06 Apr 2011 03:40:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q7NLN-0001qB-Tq for qemu-devel@nongnu.org; Wed, 06 Apr 2011 03:40:02 -0400 Received: from mx1.redhat.com ([209.132.183.28]:49005) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q7NLN-0001oZ-J6 for qemu-devel@nongnu.org; Wed, 06 Apr 2011 03:40:01 -0400 Message-ID: <4D9C18C8.5010402@redhat.com> Date: Wed, 06 Apr 2011 10:39:52 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH 00/10] pci: pci_register_bar_simple References: <1301930887-20705-1-git-send-email-avi@redhat.com> <20110404155917.GA13423@redhat.com> <4D99F061.1090208@codemonkey.ws> <4D99F34D.3060804@redhat.com> <4D9AC719.8090301@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" On 04/05/2011 09:06 PM, Blue Swirl wrote: > > > > The more complicated BARs cannot be described declaratively (at least > > without a lot of complicated infrastructure). They can switch from RAM to > > MMIO mappings at runtime, and have different sub-regions. > > Subregions should be possible, but I agree run time switch will not. > Those should be pretty rare, though. Right. I think the first priority is to have a pci specific API instead of calling cpu_register_physical_memory(); moving to a declarative API is nice but less important IMO. -- error compiling committee.c: too many arguments to function