[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] Re: RFC qdev path semantics
From: |
Markus Armbruster |
Subject: |
[Qemu-devel] Re: RFC qdev path semantics |
Date: |
Wed, 16 Jun 2010 15:05:31 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) |
Markus Armbruster <address@hidden> writes:
[...]
> Bus names are chosen by the system as follows:
>
> * If the driver of the parent device model provides a name, use that.
>
> * Else, if the parent device has id ID, use ID.NUM, where NUM is the bus
> number, counting from zero in creation order.
>
> * Else, use TYPE.NUM, where TYPE is derived from the bus type, and NUM
> is the bus number, as above.
>
> ### Paul proposes to drop ID.NUM.
ABI change: "-device lsi,id=my-scsi -device scsi-disk,bus=my-scsi.0" no
longer works.
> ### Paul proposes to either drop TYPE.NUM (and require drivers to
> provide bus names), or make NUM count separately for each bus type.
Likewise.
I'm not saying we can't do this, just that we need to consider backward
compatibility.
[...]
- Re: [Qemu-devel] Re: [RFC PATCH 0/5] Introduce canonical device hierarchy string, (continued)
RFC qdev path semantics (was: [Qemu-devel] [RFC PATCH 0/5] Introduce canonical device hierarchy string), Markus Armbruster, 2010/06/16
[Qemu-devel] Re: RFC qdev path semantics,
Markus Armbruster <=
[Qemu-devel] Re: RFC qdev path semantics, Alex Williamson, 2010/06/17
[Qemu-devel] Re: RFC qdev path semantics, Gerd Hoffmann, 2010/06/18
[Qemu-devel] Re: RFC qdev path semantics, Markus Armbruster, 2010/06/18
[Qemu-devel] Re: RFC qdev path semantics, Anthony Liguori, 2010/06/22