|
From: | Gerd Hoffmann |
Subject: | Re: [Qemu-devel] [PATCH v3 4/5] QemuOpts: framework for storing and parsing options. |
Date: | Tue, 21 Jul 2009 09:25:40 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Lightning/1.0pre Thunderbird/3.0b2 |
On 07/17/09 09:03, Kevin Wolf wrote:
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]?
Oh, I didn't see that. I just looked at the (old) parsing code in vl.c uses by almost everybody.
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?
I'll have a closer look. Who uses qemu-options? qemu-io I assume? cheers, Gerd
[Prev in Thread] | Current Thread | [Next in Thread] |