From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MHfAA-0008Tb-7u for qemu-devel@nongnu.org; Fri, 19 Jun 2009 10:33:54 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MHfA6-0008Rd-22 for qemu-devel@nongnu.org; Fri, 19 Jun 2009 10:33:53 -0400 Received: from [199.232.76.173] (port=42202 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MHfA5-0008RR-Fq for qemu-devel@nongnu.org; Fri, 19 Jun 2009 10:33:49 -0400 Received: from mx2.redhat.com ([66.187.237.31]:46149) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MHfA4-000299-Pe for qemu-devel@nongnu.org; Fri, 19 Jun 2009 10:33:49 -0400 Message-ID: <4A3BA1C6.6040701@redhat.com> Date: Fri, 19 Jun 2009 16:33:42 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] sending pci information over the wire References: <20090618193946.GH3517@poweredge.glommer> <4A3A9D89.5000305@codemonkey.ws> <20090618201227.GI3517@poweredge.glommer> <4A3AA5D8.8050303@codemonkey.ws> <4A3B527C.2010203@redhat.com> <4A3B8E56.3040903@codemonkey.ws> In-Reply-To: <4A3B8E56.3040903@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Glauber Costa , qemu-devel@nongnu.org, armbru@redhat.com On 06/19/09 15:10, Anthony Liguori wrote: > My plan for your qdev series is to give a little more time for feedback, > then ask you to rebase/resubmit so they can be applied. Give it a couple > more days to give people a chance to review. Good. >> Likewise devtree: Paul posted the patches, got a number of reviews >> comments. No discussion of the concerns happened though. There is also >> no activity in Pauls git tree. > > I think we're all just waiting for Paul to commit something. Looking forward to that. >> (1) How will we handle fdt and hotplug? We can keep the qdev tree >> and the fdt in sync all the time. Or we generate a fresh fdt >> from the qdev tree when needed (i.e. for savevm, migration and >> maybe the ppc kernel). > > I'd lean toward the later. It is probably easier to handle that way. >> I really like to see some progress here, otherwise 2017 wouldn't be >> just a running gag. > > I agree. Not every patch is reasonable to commit in 24 hours though. Sure. Especially large, non-trivial patches need some more time to review. The oldest patches of the qdev series are out for more than a week now though. The first one ("update pci device registration") is quite invasive and probably conflicts with everybody doing pci-related qdev work. It also fixes the fundamental issue that the code in master right now can't handle pci devices which need config space access handlers. > I think something > we could do better is avoiding losing track of patches though. I'm > working on that. Related issues: Looks like the qemu-commits list is lossy. I havn't seen messages for my two most recent vnc patches. I figured while rebasing the vnc patches because git surprised me with "nothing to do". Also it seems for merges only a message for the merge commit goes to the list, not for the individual patches. cheers, Gerd