From: zhenwei pi <pizhenwei@bytedance.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Markus Armbruster" <armbru@redhat.com>
Cc: Michael Roth <michael.roth@amd.com>,
Konstantin Kostiuk <kkostiuk@redhat.com>,
QEMU <qemu-devel@nongnu.org>
Subject: Re: [PATCH v2 1/1] qga: add command 'guest-get-cpustats'
Date: Wed, 6 Jul 2022 11:04:56 +0800 [thread overview]
Message-ID: <d43a478f-e54b-e624-8c67-2392bf3d3dbb@bytedance.com> (raw)
In-Reply-To: <1b3f926b-9fe6-a3ec-b697-6fa8471510ad@bytedance.com>
On 7/4/22 16:00, zhenwei pi wrote:
>
>
>> +##
>> +# @GuestOsType:
>> +#
>> +# An enumeration of OS type
>> +#
>> +# Since: 7.1
>> +##
>> +{ 'enum': 'GuestOsType',
>> + 'data': [ 'linuxos', 'windowsos' ] }
>>
>>
>> I would rather keep this enum specific to GuestCpuStats,
>> "GuestLinuxCpuStatsType"?
>>
>
> Hi,
>
> 'GuestOsType' may be re-used in the future, not only for the CPU
> statistics case.
>
>> I would also drop the "os" suffix
>>
> I'm afraid we can not drop "os" suffix, build this without "os" suffix:
> qga/qga-qapi-types.h:948:28: error: expected member name or ';' after
> declaration specifiers
> GuestLinuxCpuStats linux;
> ~~~~~~~~~~~~~~~~~~ ^
> <built-in>:336:15: note: expanded from here
> #define linux 1
>
Hi, Marc
Could you please give any hint about this issue?
>> +
>> +
>>
>>
>>
>> Looks good to me otherwise.
>> thanks
>>
>> --
>> Marc-André Lureau
>
--
zhenwei pi
next prev parent reply other threads:[~2022-07-06 3:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 2:36 [PATCH v2 0/1] qga: add command 'guest-get-cpustats' zhenwei pi
2022-07-04 2:36 ` [PATCH v2 1/1] " zhenwei pi
2022-07-04 7:28 ` Marc-André Lureau
2022-07-04 7:29 ` Marc-André Lureau
2022-07-04 8:00 ` zhenwei pi
2022-07-06 3:04 ` zhenwei pi [this message]
2022-07-06 7:20 ` Marc-André Lureau
2022-07-06 7:44 ` zhenwei pi
2022-07-06 8:57 ` Marc-André Lureau
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=d43a478f-e54b-e624-8c67-2392bf3d3dbb@bytedance.com \
--to=pizhenwei@bytedance.com \
--cc=armbru@redhat.com \
--cc=kkostiuk@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=michael.roth@amd.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).