From: Markus Armbruster <armbru@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: "Denis V. Lunev" <den@openvz.org>,
qemu-devel@nongnu.org,
Anton Nefedov <anton.nefedov@virtuozzo.com>
Subject: Re: [Qemu-devel] [PATCH v4 1/3] i386/cpu: add crash-information QOM property
Date: Mon, 20 Feb 2017 01:53:42 +0100 [thread overview]
Message-ID: <87bmtxvg15.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <f805c30f-47d1-6f79-c01b-ac1155d6859a@redhat.com> (Eric Blake's message of "Wed, 15 Feb 2017 13:41:57 -0600")
Eric Blake <eblake@redhat.com> writes:
> On 02/14/2017 12:25 AM, Denis V. Lunev wrote:
>> From: Anton Nefedov <anton.nefedov@virtuozzo.com>
>>
>> Windows reports BSOD parameters through Hyper-V crash MSRs. This
>> information is very useful for initial crash analysis and thus
>> it would be nice to have a way to fetch it.
>>
>> Signed-off-by: Anton Nefedov <anton.nefedov@virtuozzo.com>
>> Signed-off-by: Denis V. Lunev <den@openvz.org>
>> ---
>
>> +++ b/qapi-schema.json
>> @@ -5846,6 +5846,30 @@
>> 'data': [ 'pause', 'poweroff' ] }
>>
>> ##
>> +# @GuestPanicInformation:
>> +#
>> +# Information about a guest panic
>> +#
>> +# Since: 2.9
>> +##
>> +{'union': 'GuestPanicInformation',
>> + 'data': { 'hyper-v': 'GuestPanicInformationHyperV' } }
>> +
>
> Markus has been trying to eliminate the addition of new "simple unions"
> - while they are syntactically shorter in the .json file, they are
> bulkier over the wire with extra {} nesting, and more verbose in the C
> code, when compared to using a flat union instead. I won't necessarily
> hold up this patch as-is, but if we are going to avoid new simple
> unions, we have to change this before 2.9 bakes in the {} nesting (we
> can convert a simple union to a flat union without breaking QMP
> back-compat, but it's messier than if we avoid the nesting to begin with).
We should not add new simple unions. Please have a look at my
"[PATCH 0/2] Flatten simple unions where we still can".
Message-Id: <1486569864-17005-1-git-send-email-armbru@redhat.com>
https://lists.gnu.org/archive/html/qemu-devel/2017-02/msg01689.html
next prev parent reply other threads:[~2017-02-20 0:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 6:25 [Qemu-devel] [PATCH v3 0/3] kvm: report available guest crash parameters Denis V. Lunev
2017-02-14 6:25 ` [Qemu-devel] [PATCH v4 1/3] i386/cpu: add crash-information QOM property Denis V. Lunev
2017-02-15 19:41 ` Eric Blake
2017-02-20 0:53 ` Markus Armbruster [this message]
2017-02-20 18:32 ` Daniel P. Berrange
2017-02-14 6:25 ` [Qemu-devel] [PATCH v4 2/3] report guest crash information in GUEST_PANICKED event Denis V. Lunev
2017-02-15 19:43 ` Eric Blake
2017-02-14 6:25 ` [Qemu-devel] [PATCH v4 3/3] vl: log available guest crash information Denis V. Lunev
2017-02-15 16:47 ` [Qemu-devel] [PATCH v3 0/3] kvm: report available guest crash parameters Paolo Bonzini
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=87bmtxvg15.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=anton.nefedov@virtuozzo.com \
--cc=den@openvz.org \
--cc=eblake@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.