qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH, RFC 0/5] Improve device info handling


From: Gerd Hoffmann
Subject: Re: [Qemu-devel] [PATCH, RFC 0/5] Improve device info handling
Date: Wed, 02 Sep 2009 08:35:51 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Lightning/1.0pre Thunderbird/3.0b3

  Hi,

drives are host side state, they don't go into qdev.

My idea was that boards (like pc) should be in the long run
represented by a qdev.

The qdev root is the main_system_bus right now, I don't see a need to change that. All core devices (cpus, memory, pic, ...) can be children of the main system bus.

But shouldn't the drives, network and char devices be qdevs too,
wouldn't it help the metamachine (or "pc" device)?

We have to clearly separate between host state and guest state.
qdev is about guest state.

A disk has two sides: The host side (virtual drive foo is a lvm volume in raw format / a file in qcow2 format / a iso image / whatever else) and the guest side (this virtual drive is a master ide disk / scsi disk with id 3 / virtio disk / ...). Only the later is represented by qdev. The link between the two is a property.

Likewise for chardevs and network.

cheers,
  Gerd




reply via email to

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