[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] Re: [PATCHv3 00/14] boot order specification
From: |
Blue Swirl |
Subject: |
[Qemu-devel] Re: [PATCHv3 00/14] boot order specification |
Date: |
Wed, 10 Nov 2010 18:08:56 +0000 |
On Wed, Nov 10, 2010 at 5:14 PM, Gleb Natapov <address@hidden> 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:
> /address@hidden/address@hidden,1/address@hidden/address@hidden
> /address@hidden/address@hidden/address@hidden/address@hidden
> /address@hidden/address@hidden/address@hidden/address@hidden
> /address@hidden/address@hidden,1/address@hidden/address@hidden
> /address@hidden/address@hidden,1/address@hidden/address@hidden
> /address@hidden/address@hidden/address@hidden
> /address@hidden/address@hidden/address@hidden
> /address@hidden/address@hidden/address@hidden
> /address@hidden/address@hidden,1/address@hidden/address@hidden
> /address@hidden/address@hidden/address@hidden/address@hidden/address@hidden
> /address@hidden/address@hidden,2/address@hidden/address@hidden
> /address@hidden/address@hidden,2/address@hidden/address@hidden/address@hidden
>
> and on isa machine:
> /isa/address@hidden/address@hidden/address@hidden
> /isa/address@hidden/address@hidden
> /isa/address@hidden/address@hidden
> /isa/address@hidden/address@hidden/address@hidden
>
>
> Instead of using get_dev_path() callback I introduces another one
> get_fw_dev_path. Unfortunately the way get_dev_path() callback is used
> in migration code makes it hard to reuse it for other purposes. First
> of all it is not called recursively so caller expects it to provide
> unique name by itself. Device path though is inherently recursive. Each
> individual element may not be unique, but the whole path will be. On
> the other hand to call get_dev_path() recursively in migration code we
> should implement it for all possible buses first. Other problem is
> compatibility. If we change get_dev_path() output format now we will not
> be able to migrate from old qemu to new one without some additional
> compatibility layer.
>
> Gleb Natapov (14):
> Introduce fw_name field to DeviceInfo structure.
> Introduce new BusInfo callback get_fw_dev_path.
> Keep track of ISA ports ISA device is using in qdev.
> Add get_fw_dev_path callback to ISA bus in qdev.
> Store IDE bus id in IDEBus structure for easy access.
> Add get_fw_dev_path callback to IDE bus.
> Add get_dev_path callback for system bus.
> Add get_fw_dev_path callback for pci bus.
> Record which USBDevice USBPort belongs too.
> Add get_dev_path callback for usb bus.
> Add bootindex parameter to net/block/fd device
> Add bootindex parameter to pci assigned device.
> Add notifier that will be called when machine is fully created.
> Pass boot device list to firmware.
Nice, but the patches don't apply, for example
hw/device-assingment.[ch] do not exist.
- [Qemu-devel] [PATCHv3 14/14] Pass boot device list to firmware., (continued)
[Qemu-devel] [PATCHv3 13/14] Add notifier that will be called when machine is fully created., Gleb Natapov, 2010/11/10
[Qemu-devel] [PATCHv3 11/14] Add bootindex parameter to net/block/fd device, Gleb Natapov, 2010/11/10
[Qemu-devel] Re: [PATCHv3 00/14] boot order specification,
Blue Swirl <=
[Qemu-devel] Re: [PATCHv3 00/14] boot order specification, Gerd Hoffmann, 2010/11/11