From: Pradeep Jagadeesh <pradeep.jagadeesh@huawei.com>
To: Eric Blake <eblake@redhat.com>,
Pradeep Jagadeesh <pradeepkiruvale@gmail.com>,
greg kurz <groug@kaod.org>
Cc: alberto garcia <berto@igalia.com>,
jani kokkonen <jani.kokkonen@huawei.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 4/4] fsdev: QMP interface for throttling
Date: Wed, 17 May 2017 16:53:44 +0200 [thread overview]
Message-ID: <57a24e21-0864-16d3-1bce-ad801875ea9f@huawei.com> (raw)
In-Reply-To: <6a035cd9-34f9-c1f5-e986-404daf941641@redhat.com>
On 5/10/2017 10:00 PM, Eric Blake wrote:
> On 05/10/2017 03:41 AM, Pradeep Jagadeesh wrote:
>> This patch enables qmp interfaces for the fsdev
>> devices. This provides two interfaces one
>> for querying info of all the fsdev devices. The second one
>> to set the IO limits for the required fsdev device.
>>
>> Signed-off-by: Pradeep Jagadeesh <pradeep.jagadeesh@huawei.com>
>> ---
>
>> +++ b/qmp.c
>> @@ -130,6 +130,21 @@ void qmp_cpu_add(int64_t id, Error **errp)
>> }
>> }
>>
>> +#ifdef _WIN64
>> +
>> +void qmp_fsdev_set_io_throttle(IOThrottle *arg, Error **errp)
>> +{
>> + return;
>> +}
>> +
>> +IOThrottleList *qmp_query_fsdev_io_throttle(Error **errp)
>> +{
>> + abort();
>> +}
>> +
>> +#endif
>
> I think you're missing an addition to monitor.c
> qmp_unregister_commands_hack() if you intend for this command to be
> available only on non-windows platforms (and is your #ifdef the correct
> name, or is this a Linux-only feature rather than a non-windows feature).
I had to add this one here because, I was getting some error when I
cross compile for Windows. But I do not have any idea about, do I need
to add in monitor.c or not.
Regards,
Pradeep
>
next prev parent reply other threads:[~2017-05-17 14:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 8:41 [Qemu-devel] [PATCH v4 0/4] fsdev: qmp interface for io throttling Pradeep Jagadeesh
2017-05-10 8:41 ` [Qemu-devel] [PATCH v4 1/4] throttle: factor out duplicate code Pradeep Jagadeesh
2017-05-10 14:12 ` Greg Kurz
2017-05-10 15:27 ` Pradeep Jagadeesh
2017-05-10 19:48 ` Eric Blake
2017-05-11 16:12 ` Pradeep Jagadeesh
2017-05-10 8:41 ` [Qemu-devel] [PATCH v4 2/4] qmp: Create IOThrottle structure Pradeep Jagadeesh
2017-05-10 8:41 ` [Qemu-devel] [PATCH v4 3/4] qmp: refactor duplicate code Pradeep Jagadeesh
2017-05-10 19:56 ` Eric Blake
2017-05-11 16:14 ` Pradeep Jagadeesh
2017-05-11 7:50 ` Greg Kurz
2017-05-12 8:03 ` Pradeep Jagadeesh
2017-06-08 14:20 ` Greg Kurz
2017-06-09 8:32 ` Pradeep Jagadeesh
2017-05-10 8:41 ` [Qemu-devel] [PATCH v4 4/4] fsdev: QMP interface for throttling Pradeep Jagadeesh
2017-05-10 20:00 ` Eric Blake
2017-05-17 14:53 ` Pradeep Jagadeesh [this message]
2017-05-17 15:28 ` Eric Blake
2017-05-17 16:29 ` Greg Kurz
2017-05-17 17:09 ` Eric Blake
2017-05-18 13:30 ` Pradeep Jagadeesh
2017-06-08 16:49 ` Greg Kurz
2017-06-09 8:31 ` Pradeep Jagadeesh
2017-06-09 9:07 ` Greg Kurz
2017-06-09 9:13 ` Pradeep Jagadeesh
2017-06-09 9:20 ` Greg Kurz
2017-05-10 10:02 ` [Qemu-devel] [PATCH v4 0/4] fsdev: qmp interface for io throttling 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=57a24e21-0864-16d3-1bce-ad801875ea9f@huawei.com \
--to=pradeep.jagadeesh@huawei.com \
--cc=berto@igalia.com \
--cc=eblake@redhat.com \
--cc=groug@kaod.org \
--cc=jani.kokkonen@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).