qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: boddu pavan <boddupavan@yahoo.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QEMU data passing between modules
Date: Wed, 11 Feb 2015 08:42:15 +0000 (UTC)	[thread overview]
Message-ID: <966702586.1872141.1423644135130.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: <1792766588.1651731.1423592418755.JavaMail.yahoo@mail.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 809 bytes --]


 Ping again!
Are there any docs for QOM ?? or the historical parent of QOM , so that it is easy to relate.
Thanks,Sai Pavan

     On Tuesday, February 10, 2015 11:50 PM, boddu pavan <boddupavan@yahoo.com> wrote:
   

 Ok fine.
I always think there should be basic doc for QOM model for the QEMU beginners as this point. Or if we already have some in-mails explanations or any blogs can any one point out here.
Thanks.Sai Pavan
     On Tuesday, February 10, 2015 7:57 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
   

 

On 10/02/2015 15:02, boddu pavan wrote:
> 
> Does all the hw_peripherals has any root node kind of thing. Which makes
> all our nodes connected ?
> 

The common superclass of the devices is DeviceState.

The root object that connects the devices is the QEMUMachine.

Paolo



    

    

[-- Attachment #2: Type: text/html, Size: 4583 bytes --]

  reply	other threads:[~2015-02-11  8:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54DA05BA.4030106@redhat.com>
     [not found] ` <832065415.1546511.1423574820829.JavaMail.yahoo@mail.yahoo.com>
2015-02-10 13:30   ` [Qemu-devel] QEMU data passing between modules Paolo Bonzini
2015-02-10 13:34     ` boddu pavan
2015-02-10 13:39       ` Paolo Bonzini
2015-02-10 14:02         ` boddu pavan
2015-02-10 14:25           ` Paolo Bonzini
2015-02-10 18:20             ` boddu pavan
2015-02-11  8:42               ` boddu pavan [this message]
2015-02-10 13:15 boddu pavan

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=966702586.1872141.1423644135130.JavaMail.yahoo@mail.yahoo.com \
    --to=boddupavan@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).