Previously, it was suggested to use QAPI unions/enums to declare feature bits. Some of weak parts of my code (such `get_feature_name' callback) went away. But a lot of of dummy code with feature declaration is still here, it just migrated to json file.
So, I would be glad to get a responce if my understanging of using QAPI structures was correct, or there was another way to do that cleaner? v5: Use QAPI enums/unions to declare virtio feature bits v4: http://lists.nongnu.org/archive/html/qemu-devel/2017-10/msg00393.html v3: http://lists.nongnu.org/archive/html/qemu-devel/2017-09/msg07565.html v2: http://lists.nongnu.org/archive/html/qemu-devel/2017-09/msg07527.html v1: http://lists.nongnu.org/archive/html/qemu-devel/2017-09/msg07247.html Jan Dakinevich (2): virtio: introduce `query-virtio' QMP command virtio: add `info virtio' HMP command hmp-commands-info.hx | 14 ++ hmp.c | 122 +++++++++++++ hmp.h | 1 + hw/virtio/Makefile.objs | 3 + hw/virtio/virtio-qmp.c | 223 +++++++++++++++++++++++ hw/virtio/virtio-stub.c | 9 + qapi-schema.json | 466 ++++++++++++++++++++++++++++++++++++++++++++++++ 7 files changed, 838 insertions(+) create mode 100644 hw/virtio/virtio-qmp.c create mode 100644 hw/virtio/virtio-stub.c -- 2.1.4
