qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hitoshi Mitake <mitake.hitoshi@lab.ntt.co.jp>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Hitoshi Mitake <mitake.hitoshi@lab.ntt.co.jp>,
	Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org, mitake.hitoshi@gmail.com
Subject: Re: [Qemu-devel] [PATCH v2] blkdebug: make the fault injection functionality callable from QMP
Date: Thu, 11 Sep 2014 11:50:39 +0900	[thread overview]
Message-ID: <87r3zij2f4.wl%mitake.hitoshi@lab.ntt.co.jp> (raw)
In-Reply-To: <20140902152914.GM29067@stefanha-thinkpad.redhat.com>


Hi Stefan, Eric, Sorry for my late reply.

At Tue, 2 Sep 2014 16:29:14 +0100,
Stefan Hajnoczi wrote:
> 
> [1  <text/plain; us-ascii (quoted-printable)>]
> On Thu, Aug 28, 2014 at 03:18:48PM +0900, Hitoshi Mitake wrote:
> > At Wed, 27 Aug 2014 06:43:49 -0600,
> > Eric Blake wrote:
> > > 
> > > [1  <text/plain; UTF-8 (quoted-printable)>]
> > > On 08/26/2014 11:34 PM, Hitoshi Mitake wrote:
> > > Actually, if you use a type-safe qapi definition, you may not even need
> > > to do raw qdict operations, but can just directly use the C struct that
> > > gets generated as a result of the qapi.
> > > 
> > > 
> > > > 
> > > > I also like the detailed specification. But, there are bunch of event
> > > > names (the event_names array of block/blkdebug.c). In addition, the
> > > > rule of blkdebug can be extended. So I think defining it in two palces
> > > > (qapi-schema.json and block/blkdebug.c) is hard to maintain. Parsing
> > > > qdict in blkdebug.c would be simpler. How do you think?
> > > 
> > > No, don't do duplication.  Instead, fix blkdebug.c to USE the enum
> > > generated by the .json, and you only have to maintain the list in one
> > > place - the .json file.
> > > 
> > 
> > OK, I understand your opinion. But it requires amount of change in
> > existing blkdebug implementation. So I want to hear opinions from the
> > maintainers. How do you think about this idea (maintaining blkdebug
> > events in .json format for avoiding duplication), Stefan and Kevin?
> 
> It would be nice to specify the rule syntax using qapi JSON.
> 
> I'm not sure if we can eliminate the QemuOptsList but it's probably
> possible to avoid qdict or ini file parsing and instead use qapi
> visitors to convert input to C structs.
> 
> It's worth a try.

OK, I'll do it in v3.

Thanks,
Hitoshi

> 
> Stefan
> [2  <application/pgp-signature (7bit)>]
> 

      reply	other threads:[~2014-09-11  2:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27  1:59 [Qemu-devel] [PATCH v2] blkdebug: make the fault injection functionality callable from QMP Hitoshi Mitake
2014-08-27  2:54 ` Eric Blake
2014-08-27  5:34   ` Hitoshi Mitake
2014-08-27 12:43     ` Eric Blake
2014-08-28  6:18       ` Hitoshi Mitake
2014-09-02 15:29         ` Stefan Hajnoczi
2014-09-11  2:50           ` Hitoshi Mitake [this message]

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=87r3zij2f4.wl%mitake.hitoshi@lab.ntt.co.jp \
    --to=mitake.hitoshi@lab.ntt.co.jp \
    --cc=kwolf@redhat.com \
    --cc=mitake.hitoshi@gmail.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).