qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] Re: RFC qdev path semantics


From: Gerd Hoffmann
Subject: [Qemu-devel] Re: RFC qdev path semantics
Date: Fri, 18 Jun 2010 09:52:46 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100505 Fedora/3.0.4-2.el6 Thunderbird/3.0.4

  Hi,

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.

### Paul proposes to either drop TYPE.NUM (and require drivers to
     provide bus names), or make NUM count separately for each bus type.

I agree, instance numbers are not stable.

NUM in the child bus name has *nothing* to do with the savevm instance number.

cheers,
  Gerd



reply via email to

[Prev in Thread] Current Thread [Next in Thread]