From: Max Reitz <mreitz@redhat.com>
To: Peter Lieven <pl@kamp.de>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, armbru@redhat.com,
stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] block: add a knob to disable multiwrite_merge
Date: Mon, 20 Oct 2014 15:15:03 +0200 [thread overview]
Message-ID: <54450AD7.8000901@redhat.com> (raw)
In-Reply-To: <54450491.7060506@kamp.de>
On 20.10.2014 at 14:48, Peter Lieven wrote:
> On 20.10.2014 14:19, Max Reitz wrote:
>> On 2014-10-20 at 14:16, Peter Lieven wrote:
>>> On 20.10.2014 13:51, Max Reitz wrote:
>>>> On 2014-10-20 at 12:03, Peter Lieven wrote:
>>>> [...]
>>>
>>> Can you further help here. I think my problem was that I don't have
>>> access to the commandline options in bdrv_open?!
>>
>> You do. It's the "options" QDict. :-)
>
> Maybe I just don't get it.
>
> If I specify
>
> qemu -drive if=virtio,file=image.qcow2,write-merging=off
>
> and check with
>
> qdict_get_try_bool(options, "write-merging", true);
>
> in bdrv_open() directly before bdrv_swap I always get true.
Hm, judging from fprintf(stderr, "%s\n",
qstring_get_str(qobject_to_json_pretty(QOBJECT(options))));, it's there
for me (directly after qdict_del(options, "node-name"). The output is:
Qemu wrote:
> {
> "filename": "image.qcow2"
> }
> {
> "write-merging": "off"
> }
> qemu-system-x86_64: -drive
> if=virtio,file=image.qcow2,write-merging=off: could not open disk
> image image.qcow2: Block format 'qcow2' used by device 'virtio0'
> doesn't support the option 'write-merging'
But as you can see, it's a string and not a bool. So the problem is that
there are (at least) two parameter "types" in qemu: One is just giving a
QDict, and the other are QemuOpts. QDicts are just the raw user input
and the user can only input strings, so everything is just a string. As
far as I know, typing everything correctly is done by converting the
QDict to a QemuOpts object (as you can see in generally every block
driver which supports some options (e.g. qcow2) and also in
blockdev_init(), it's qemu_opts_absorb_qdict()).
Sooo, right, I forgot that. Currently, there are no non-string
non-block-driver-specific options for mid-tree BDS (in contrast to the
root BDS, which are parsed in blockdev_init()), so you now have the
honorable task of introducing such a QemuOptsList along with
qemu_opts_absorb_qdict() and everything to bdrv_open_common(). *cough*
Max
next prev parent reply other threads:[~2014-10-20 13:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 6:14 [Qemu-devel] [PATCH] block: add a knob to disable multiwrite_merge Peter Lieven
2014-10-20 8:59 ` Max Reitz
2014-10-20 9:14 ` Peter Lieven
2014-10-20 9:27 ` Max Reitz
2014-10-20 10:03 ` Peter Lieven
2014-10-20 11:51 ` Max Reitz
2014-10-20 11:53 ` Peter Lieven
2014-10-20 12:56 ` Kevin Wolf
2014-10-20 12:16 ` Peter Lieven
2014-10-20 12:19 ` Max Reitz
2014-10-20 12:48 ` Peter Lieven
2014-10-20 13:15 ` Max Reitz [this message]
2014-10-20 13:19 ` Peter Lieven
2014-10-20 13:22 ` Max Reitz
2014-10-20 13:29 ` Peter Lieven
2014-10-20 13:31 ` Kevin Wolf
2014-10-20 13:47 ` Peter Lieven
2014-10-20 13:55 ` Kevin Wolf
2014-10-20 13:59 ` Peter Lieven
2014-10-20 13:59 ` Max Reitz
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=54450AD7.8000901@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).