From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: [PATCHv3 00/14] boot order specification Date: Thu, 11 Nov 2010 11:21:39 +0100 Message-ID: <4CDBC3B3.8040007@redhat.com> References: <1289409261-5418-1-git-send-email-gleb@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, blauwirbel@gmail.com, armbru@redhat.com, alex.williamson@redhat.com, mst@redhat.com To: Gleb Natapov Return-path: Received: from mx1.redhat.com ([209.132.183.28]:4258 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754077Ab0KKKVp (ORCPT ); Thu, 11 Nov 2010 05:21:45 -0500 In-Reply-To: <1289409261-5418-1-git-send-email-gleb@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 11/10/10 18:14, Gleb Natapov wrote: > This is current sate of the patch series for people to comment on. > I am using open firmware naming scheme to specify device path names. > > Names look like this on pci machine: > /pci@i0cf8/ide@1,1/drive@1/disk@0 > /pci@i0cf8/isa@1/fdc@03f1/floppy@1 > /pci@i0cf8/isa@1/fdc@03f1/floppy@0 > /pci@i0cf8/ide@1,1/drive@1/disk@1 > /pci@i0cf8/ide@1,1/drive@0/disk@0 > /pci@i0cf8/scsi@3/disk@0 > /pci@i0cf8/ethernet@4/ethernet-phy@0 > /pci@i0cf8/ethernet@5/ethernet-phy@0 > /pci@i0cf8/ide@1,1/drive@0/disk@1 > /pci@i0cf8/isa@1/ide@01e8/drive@0/disk@0 > /pci@i0cf8/usb@1,2/network@0/ethernet@0 > /pci@i0cf8/usb@1,2/hub@1/network@0/ethernet@0 Good stuff overall, but see replies to patches for some nits. IIRC some powerpc (+sparc?) boards pass a device tree to the guest. So with this (and maybe some more bits) we might be able to dynamically generate a device tree from our qdev tree? Any comments from the ppc/sparc folks on this? cheers, Gerd