From: Stefan Hajnoczi <stefanha@redhat.com>
To: Greg Kurz <groug@kaod.org>
Cc: Eric Blake <eblake@redhat.com>,
Pradeep Jagadeesh <pradeepkiruvale@gmail.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Alberto Garcia <berto@igalia.com>,
Pradeep Jagadeesh <pradeep.jagadeesh@huawei.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2 v16] fsdev: add IO throttle support to fsdev devices
Date: Tue, 14 Feb 2017 13:21:22 +0000 [thread overview]
Message-ID: <20170214132122.GH23310@stefanha-x1.localdomain> (raw)
In-Reply-To: <20170207172933.05574f60@bahia.lan>
[-- Attachment #1: Type: text/plain, Size: 2137 bytes --]
On Tue, Feb 07, 2017 at 05:29:33PM +0100, Greg Kurz wrote:
> Cc'ing Stefan who reviewed patch 2/2.
>
> On Tue, 7 Feb 2017 09:56:08 -0600
> Eric Blake <eblake@redhat.com> wrote:
>
> > On 02/07/2017 04:32 AM, Greg Kurz wrote:
> > >>
> > >> I'm not aware of anything related to fsdev in QMP... and libvirt seems to
> > >> only parse the output of -help to guess fsdev capabilities.
> > >
> > > Oops, reading some more libvirt code I now see that libvirt doesn't parse
> > > -help anymore with QEMU >= 1.2.0... sorry for the noise :)
> > >
> > >> And indeed,
> > >> qemu-options.hx doesn't expose this new feature.
> > >>
> > >>> Please make sure we don't reach 2.9 with only a half-baked feature;
> > >>> whether that means finishing the QMP work or temporarily disabling the
> > >>> cli additions until a later release can finish the work.
> > >>>
> > >>
> > >> Would this be ok to add the missing bits in qemu-options.hx or do you
> > >> expect more ?
> >
> > If it cannot be probed via QMP, then libvirt will most likely assume
> > that it does not exist. I guess we're okay having command line only in
> > 2.9 if you can't get QMP working, because libvirt will just never drive
> > the feature until 2.10 when QMP is available; but then we risk the
> > command line subtly changing and breaking someone else that was using
> > the command line without QMP. Maybe the safest approach is to just use
> > the 'x-' prefix to the command line portion, until the feature is complete.
> >
>
> The semantics here are exactly the same as for block devices. The
> command line options added to -fsdev are the very same already used
> by -drive for years.
>
> Patch 2/2 in this series even factors them out to a common header file
> to be used by fsdev and blockdev. I really don't expect any modification
> at all on the command line (nor the other people who reviewed that patch
> obviously)... are you suggesting that we should put 2/2 on hold and
> use the 'x-' prefix anyway ?
I see these parameter names as stable. There is little risk that they
would change.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-02-14 13:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 11:57 [Qemu-devel] [PATCH 0/2 v16] fsdev: add IO throttle support to fsdev devices Pradeep Jagadeesh
2017-02-03 11:57 ` [Qemu-devel] [PATCH 1/2 " Pradeep Jagadeesh
2017-02-03 12:21 ` Alberto Garcia
2017-02-06 19:36 ` Eric Blake
2017-02-06 23:15 ` Greg Kurz
2017-02-07 10:32 ` Greg Kurz
2017-02-07 15:56 ` Eric Blake
2017-02-07 16:29 ` Greg Kurz
2017-02-14 13:21 ` Stefan Hajnoczi [this message]
2017-02-22 13:41 ` Greg Kurz
2017-02-22 16:01 ` Eric Blake
2017-02-22 16:59 ` Greg Kurz
2017-02-22 17:04 ` Eric Blake
2017-02-07 6:18 ` Fam Zheng
2017-02-07 10:34 ` Pradeep Jagadeesh
2017-02-03 11:57 ` [Qemu-devel] [PATCH 2/2 v16] throttle: factor out duplicate code Pradeep Jagadeesh
2017-02-03 12:22 ` Alberto Garcia
2017-02-03 12:27 ` Pradeep Jagadeesh
2017-02-03 12:44 ` Alberto Garcia
2017-02-03 12:46 ` Pradeep Jagadeesh
2017-02-03 12:53 ` Alberto Garcia
2017-02-03 12:57 ` Pradeep Jagadeesh
2017-02-06 14:58 ` Greg Kurz
2017-02-06 15:19 ` Pradeep Jagadeesh
2017-02-03 12:02 ` [Qemu-devel] [PATCH 0/2 v16] fsdev: add IO throttle support to fsdev devices no-reply
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=20170214132122.GH23310@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=berto@igalia.com \
--cc=eblake@redhat.com \
--cc=groug@kaod.org \
--cc=pradeep.jagadeesh@huawei.com \
--cc=pradeepkiruvale@gmail.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).