qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/6] blkdebug: Implement bdrv_refresh_filename()
Date: Wed, 20 Aug 2014 21:08:40 +0200	[thread overview]
Message-ID: <53F4F238.2040104@redhat.com> (raw)
In-Reply-To: <20140820151424.GI6122@noname.redhat.com>

On 20.08.2014 17:14, Kevin Wolf wrote:
> Am 18.07.2014 um 20:24 hat Max Reitz geschrieben:
>> Because blkdebug cannot simply create a configuration file, simply
>> refuse to reconstruct a plain filename and only generate an options
>> QDict from the rules instead.
>>
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>> ---
>> Instead of this rather complicated implementation, we could decide to
>> just drop it and let this be handled by the default implementation. The
>> default implementation however cannot generate full_open_options in case
>> a configuration file was given; in that case, it would just return the
>> filename containing the name of the configuration file. On the other
>> hand, blkdebug is just a debug driver anyway, so it probably wouldn't
>> hurt too much.
> I think you really want to have the config file name used here for
> options that were loaded from a config file, and the explicit JSON
> notation only for options explicitly specified on the command line or in
> blockdev-add.
>
> We still only have 1024 characters for bs->filename... ;-)

But who uses blkdebug anyway. *g*

I'll take a look into this, along with whether we can minimize use of 
BDS.filename enough to justify completely removing it.

Max

  reply	other threads:[~2014-08-20 19:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 18:24 [Qemu-devel] [PATCH 0/6] block: Let drivers reconstruct the filename Max Reitz
2014-07-18 18:24 ` [Qemu-devel] [PATCH 1/6] block: Add bdrv_refresh_filename() Max Reitz
2014-08-20 15:07   ` Kevin Wolf
2014-08-20 19:06     ` Max Reitz
2014-08-21  8:26       ` Kevin Wolf
2014-07-18 18:24 ` [Qemu-devel] [PATCH 2/6] blkdebug: Implement bdrv_refresh_filename() Max Reitz
2014-08-20 15:14   ` Kevin Wolf
2014-08-20 19:08     ` Max Reitz [this message]
2014-07-18 18:24 ` [Qemu-devel] [PATCH 3/6] blkverify: " Max Reitz
2014-07-18 18:24 ` [Qemu-devel] [PATCH 4/6] nbd: " Max Reitz
2014-07-18 18:25 ` [Qemu-devel] [PATCH 5/6] quorum: " Max Reitz
2014-07-18 18:25 ` [Qemu-devel] [PATCH 6/6] iotests: Add test for image filename construction Max Reitz
2014-08-15 15:22 ` [Qemu-devel] [PATCH 0/6] block: Let drivers reconstruct the filename Max Reitz
2014-08-20 15:29 ` Kevin Wolf

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=53F4F238.2040104@redhat.com \
    --to=mreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --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).