qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/3] Modular command line options
Date: Wed, 21 May 2008 22:58:10 +0200	[thread overview]
Message-ID: <48348CE2.80303@bellard.org> (raw)
In-Reply-To: <48336413.2060909@web.de>

Jan Kiszka wrote:
> Following up on my earlier proposal to introduce per-machine command
> line options, this version provides a more generic approach. It should
> also be usable for scenarios like per-arch or per-accelerator.
> 
> To summarize the approach: Command line options are now organized in
> sets. Each set consists of a list of options, a help text, and a pointer
> the a parse handler that can process the options. The base option set of
> QEMU is automatically registered, more sets can be added via
> qemu_register_option_set().
> 
> The patch includes quite some refactoring in order to move the basic
> switches over the new scheme. So you may have a look at the data
> structures in qemu-common.h, but otherwise it is better to apply it and
> then study vl.c. More refactoring of existing switches is likely
> feasible, but first this needs and an OK from (or merging by) the
> maintainers.
> [...]

I am not sure it is the way to follow because soon the configuration
file will be the way to pass elaborated options to QEMU.

Regards,

Fabrice.

  parent reply	other threads:[~2008-05-21 20:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 23:51 [Qemu-devel] [PATCH 1/3] Modular command line options Jan Kiszka
2008-05-21 19:17 ` Glauber Costa
2008-05-21 20:58 ` Fabrice Bellard [this message]
2008-05-22 10:11   ` Ian Jackson
2008-05-22 10:19 ` Ian Jackson
2008-05-22 10:20   ` Ian Jackson
2008-05-22 12:49   ` [Qemu-devel] " Jan Kiszka
2008-05-23 13:29     ` Glauber Costa
2008-05-23 15:12       ` Jan Kiszka

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=48348CE2.80303@bellard.org \
    --to=fabrice@bellard.org \
    --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).