From: Kevin Wolf <kwolf@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 4/5] QemuOpts: framework for storing and parsing options.
Date: Fri, 17 Jul 2009 09:03:16 +0200 [thread overview]
Message-ID: <4A602234.50208@redhat.com> (raw)
In-Reply-To: <1247756224-19219-5-git-send-email-kraxel@redhat.com>
Gerd Hoffmann schrieb:
> This stores device parameters in a better way than unparsed strings.
>
> New types:
> QemuOpt - one key-value pair.
> QemuOpts - group of key-value pairs, belonging to one
> device, i.e. one drive.
> QemuOptsList - list of some kind of devices, i.e. all drives.
What about having the options typed like I did in qemu-option.[ch]?
In general qemu-option seems to do more parsing/checking than QemuOpts
does, on the other hand it's not yet generic enough to suit everything.
Maybe a combination of both would be the right thing?
Kevin
next prev parent reply other threads:[~2009-07-17 7:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 14:56 [Qemu-devel] [PATCH v3 0/5] cleanup drive handling Gerd Hoffmann
2009-07-16 14:57 ` [Qemu-devel] [PATCH v3 1/5] kill drives_table Gerd Hoffmann
2009-07-16 14:57 ` [Qemu-devel] [PATCH v3 2/5] add support for drive ids Gerd Hoffmann
2009-07-16 14:57 ` [Qemu-devel] [PATCH v3 3/5] kill drives_opt Gerd Hoffmann
2009-07-16 14:57 ` [Qemu-devel] [PATCH v3 4/5] QemuOpts: framework for storing and parsing options Gerd Hoffmann
2009-07-16 16:35 ` [Qemu-devel] " Jan Kiszka
2009-07-16 18:50 ` Gerd Hoffmann
2009-07-17 7:03 ` Kevin Wolf [this message]
2009-07-21 7:25 ` [Qemu-devel] " Gerd Hoffmann
2009-07-21 7:42 ` Kevin Wolf
2009-07-21 13:59 ` Gerd Hoffmann
2009-07-21 15:58 ` Kevin Wolf
2009-07-22 6:58 ` Gerd Hoffmann
2009-07-22 7:31 ` Kevin Wolf
2009-07-22 7:55 ` Gerd Hoffmann
2009-07-16 14:57 ` [Qemu-devel] [PATCH v3 5/5] switch -drive to QemuOpts Gerd Hoffmann
2009-07-16 16:07 ` Anthony Liguori
2009-07-16 18:55 ` Gerd Hoffmann
2009-07-16 19:03 ` Anthony Liguori
2009-07-16 19:32 ` Gerd Hoffmann
2009-07-16 20:08 ` Anthony Liguori
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=4A602234.50208@redhat.com \
--to=kwolf@redhat.com \
--cc=kraxel@redhat.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).