From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LQHxY-0005iX-Mh for qemu-devel@nongnu.org; Fri, 23 Jan 2009 04:04:16 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LQHxY-0005iL-1w for qemu-devel@nongnu.org; Fri, 23 Jan 2009 04:04:16 -0500 Received: from [199.232.76.173] (port=35760 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LQHxX-0005iI-UW for qemu-devel@nongnu.org; Fri, 23 Jan 2009 04:04:15 -0500 Received: from mx2.redhat.com ([66.187.237.31]:48771) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LQHxX-0002Tj-Cs for qemu-devel@nongnu.org; Fri, 23 Jan 2009 04:04:15 -0500 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n0N94EWO009897 for ; Fri, 23 Jan 2009 04:04:14 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n0N94Fwt011645 for ; Fri, 23 Jan 2009 04:04:15 -0500 Received: from pike.pond.sub.org (vpn-10-110.str.redhat.com [10.32.10.110]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n0N94ESw032184 for ; Fri, 23 Jan 2009 04:04:15 -0500 Subject: Re: [Qemu-devel] [RFC PATCH 0/9] Configurable PCI device addresses References: <87ocxzrvqb.fsf@pike.pond.sub.org> <4978D1B0.5040500@codemonkey.ws> From: Markus Armbruster Date: Fri, 23 Jan 2009 10:04:12 +0100 In-Reply-To: <4978D1B0.5040500@codemonkey.ws> (Anthony Liguori's message of "Thu\, 22 Jan 2009 14\:06\:08 -0600") Message-ID: <87r62upf5f.fsf@pike.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Anthony Liguori writes: > Markus Armbruster wrote: >> This patch series makes PCI device addresses configurable for a number >> of devices. For now, I just covered the ones I consider important >> and/or where the change is somewhat invasive. >> >> Why is a configurable PCI device address useful? Currently, QEMU >> assigns a few device addresses statically, and the rest dynamically on >> a first come, first serve basis[*]. If you add or remove a device, >> all devices registering later change address. I'm told a certain >> operating system that can't be named in polite company can get rather >> upset about that. >> >> Making the device address configurable looks like the simplest >> solution to this problem. Only users who really mind changing >> addresses have to deal with the new configuration parameter. >> > > I think we're starting to get to the tipping point where we really > just need to introduce a machine config file. Makes sense to me. But considering the idea has been mulled around for so long (half a year?) without obvious progress (obvious to ignorant me!), I chose to scratch my itch right away. Any chance I can get it scratched now, or do I have to wait for the machine description file feature? > Paul, you mentioned you were working on something before? Care to > update us on the status? Yes, please! > I know there was a fair bit of support before for a FDT based machine > config. > > Regards, > > Anthony Liguori