qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v10 5/6] fsdev: QMP interface for throttling


From: Pradeep Jagadeesh
Subject: Re: [Qemu-devel] [PATCH v10 5/6] fsdev: QMP interface for throttling
Date: Fri, 8 Sep 2017 14:49:31 +0200
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0

On 9/8/2017 2:34 PM, Markus Armbruster wrote:
Pradeep Jagadeesh <address@hidden> writes:

On 9/8/2017 12:02 PM, Markus Armbruster wrote:
Pradeep Jagadeesh <address@hidden> writes:
[...]
diff --git a/qmp.c b/qmp.c
index b86201e..eed91e5 100644
--- a/qmp.c
+++ b/qmp.c
@@ -130,6 +130,20 @@ void qmp_cpu_add(int64_t id, Error **errp)
     }
 }

+#if defined(_WIN64) || defined(_WIN32) || defined(__FreeBSD__)
+
+void qmp_fsdev_set_io_throttle(IOThrottle *arg, Error **errp)
+{
+    return;
+}
+
+IOThrottleList *qmp_query_fsdev_io_throttle(Error **errp)
+{
+    return NULL;
+}
+
+#endif
+
 #ifndef CONFIG_VNC
 /* If VNC support is enabled, the "true" query-vnc command is
    defined in the VNC subsystem */

Why do we need *two* stubs for these functions, one here and one in
fsdev/qemu-fsdev-dummy.c?
At two different platforms the build fails. So, there are needed.

We don't add stubs to random places until the linker succeeds for all
the configurations we happen to test.  We figure out *how* the linker
fails to correct our idea of where a certain stub belongs until we find
the one appropriate home for it.

OK, I will figure it out and send it across. But these were discussed since the v1, now I do not remember on top of my mind. I will have to dig my old emails and send it across or I should reproduce them again.

If you can't figure that out, that's okay, just tell us how exactly the
linker fails for you, and we'll be happy to help.
Thanks for offering help!

-Pradeep





reply via email to

[Prev in Thread] Current Thread [Next in Thread]