qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] Re: [PATCH] Split machine creation from the main loop
Date: Thu, 24 Feb 2011 08:47:28 -0600	[thread overview]
Message-ID: <4D666F80.1040907@codemonkey.ws> (raw)
In-Reply-To: <AANLkTint+s0AsF9zvO=znJyxGyphtXED4i42=78W3RzR@mail.gmail.com>

On 02/24/2011 04:19 AM, Stefan Hajnoczi wrote:
>
> Any chance of reusing info qtree, QemuOpts, or other existing
> infrastructure for the config file?
>    

I'm nowhere near implementation details like that.  I'm still trying to 
understand whether this is a Good Idea at all.

Regards,

Anthony Liguori

> Config file set/get/format code tends to be just toggling variables
> and manipulating strings.  There is similarity here with the option
> parsing and qdev properties.
>
> Stefan
>
>    

  reply	other threads:[~2011-02-24 14:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23 21:38 [Qemu-devel] [PATCH] Split machine creation from the main loop Anthony Liguori
2011-02-23 23:00 ` [Qemu-devel] " Juan Quintela
2011-02-23 23:12   ` Anthony Liguori
2011-02-23 23:38     ` Juan Quintela
2011-02-24  0:36       ` Anthony Liguori
2011-02-24 10:19         ` Stefan Hajnoczi
2011-02-24 14:47           ` Anthony Liguori [this message]
2011-02-24 16:01     ` Avi Kivity
2011-02-24 17:25       ` Anthony Liguori
2011-02-27 11:33         ` Avi Kivity
2011-02-28  4:01           ` Anthony Liguori
2011-02-28  8:20             ` Avi Kivity
2011-02-28  8:57               ` Paolo Bonzini
2011-02-28  9:13                 ` Avi Kivity
2011-02-28 10:08                   ` Paolo Bonzini
2011-02-28 12:08                   ` Anthony Liguori
2011-02-25 17:02 ` [Qemu-devel] " 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=4D666F80.1040907@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=stefanha@gmail.com \
    /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).