All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH, RFC 0/5] Improve device info handling
Date: Wed, 02 Sep 2009 08:35:51 +0200	[thread overview]
Message-ID: <4A9E1247.9040009@redhat.com> (raw)
In-Reply-To: <f43fc5580909010921y60cc632o637c65cd6e194dd2@mail.gmail.com>

   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	other threads:[~2009-09-02  6:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-29 14:06 [Qemu-devel] [PATCH, RFC 0/5] Improve device info handling Blue Swirl
2009-08-31  8:12 ` Gerd Hoffmann
2009-08-31 15:23   ` Blue Swirl
2009-09-01  7:54     ` Gerd Hoffmann
2009-09-01 16:21       ` Blue Swirl
2009-09-02  6:35         ` Gerd Hoffmann [this message]
2009-09-02 14:41           ` Blue Swirl
2009-09-02 16:42             ` Gerd Hoffmann
2009-09-02 17:53               ` Blue Swirl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A9E1247.9040009@redhat.com \
    --to=kraxel@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.