* Markus Armbruster (arm...@redhat.com) wrote:
> Jan Dakinevich writes:
>
> > On Tue, 19 Dec 2017 15:57:18 +0100
> > Markus Armbruster wrote:
> >
> >> QAPI/QMP interface review only.
> >>
> >> You neglected to cc: the maintainers of qapi-schema.json, so I'm doing
> >> that for you.
> >>
> >
>
On Wed, 20 Dec 2017 11:16:46 +0100
Markus Armbruster wrote:
> Jan Dakinevich writes:
>
> > On Tue, 19 Dec 2017 15:57:18 +0100
> > Markus Armbruster wrote:
> >> Jan Dakinevich writes:
> Taking a step back: what's the intended purpose of query-virtio? The
> cover letter doesn't really say:
>
Jan Dakinevich writes:
> On Tue, 19 Dec 2017 15:57:18 +0100
> Markus Armbruster wrote:
>
>> QAPI/QMP interface review only.
>>
>> You neglected to cc: the maintainers of qapi-schema.json, so I'm doing
>> that for you.
>>
>
> Thank you so much. I screwed up with this patchset at least twice: wi
On Tue, 19 Dec 2017 15:57:18 +0100
Markus Armbruster wrote:
> QAPI/QMP interface review only.
>
> You neglected to cc: the maintainers of qapi-schema.json, so I'm doing
> that for you.
>
Thank you so much. I screwed up with this patchset at least twice: with
list of maintainers and with my own
QAPI/QMP interface review only.
You neglected to cc: the maintainers of qapi-schema.json, so I'm doing
that for you.
Jan Dakinevich writes:
> The command is intended for gathering virtio information such as status,
> feature bits, negotiation status. It is convenient and useful for debug
> purp
The command is intended for gathering virtio information such as status,
feature bits, negotiation status. It is convenient and useful for debug
purpose.
The commands returns generic virtio information for virtio such as
common feature names and status bits names and information for all
attached t