From: Eric Blake <eblake@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>, qemu-devel@nongnu.org
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 2/5] qapi: add SysEmuTarget to "common.json"
Date: Fri, 27 Apr 2018 14:53:04 -0500 [thread overview]
Message-ID: <5853853e-fa05-2dcf-0c8e-6b812222c453@redhat.com> (raw)
In-Reply-To: <20180427192852.15013-3-lersek@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]
On 04/27/2018 02:28 PM, Laszlo Ersek wrote:
> We'll soon need an enumeration type that lists all the softmmu targets
> that QEMU (the project) supports. Introduce @SysEmuTarget to
> "common.json".
>
> The enum constant @x86_64 doesn't match the QAPI convention of preferring
> hyphen ("-") over underscore ("_"). This is intentional; the @SysEmuTarget
> constants are supposed to produce QEMU executable names when stringified
> and appended to the "qemu-system-" prefix. Put differently, the
> replacement text of the TARGET_NAME preprocessor macro must be possible to
> look up in the list of (stringified) enum constants.
>
> Like other enum types, @SysEmuTarget too can be used for discriminator
> fields in unions. For the @i386 constant, a C-language union member called
> "i386" would be generated. On mingw build hosts, "i386" is a macro
> however. Add "i386" to "polluted_words" at once.
>
> Cc: "Daniel P. Berrange" <berrange@redhat.com>
> Cc: Eric Blake <eblake@redhat.com>
> Cc: Markus Armbruster <armbru@redhat.com>
> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
> ---
>
> Notes:
> PATCHv3:
>
> - copy the suggested (shorter) Notes: wrt. underscore use in @x86_64 to
> the schema, and move the original (longer) schema Notes: to the commit
> message [Eric]
Thanks; that looks better.
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2018-04-27 19:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 19:28 [Qemu-devel] [PATCH v3 0/5] qapi: introduce the SysEmuTarget enumeration Laszlo Ersek
2018-04-27 19:28 ` [Qemu-devel] [PATCH v3 1/5] qapi: fill in CpuInfoFast.arch in query-cpus-fast Laszlo Ersek
2018-04-27 19:28 ` [Qemu-devel] [PATCH v3 2/5] qapi: add SysEmuTarget to "common.json" Laszlo Ersek
2018-04-27 19:53 ` Eric Blake [this message]
2018-05-02 7:55 ` Markus Armbruster
2018-04-27 19:28 ` [Qemu-devel] [PATCH v3 3/5] qapi: change the type of TargetInfo.arch from string to enum SysEmuTarget Laszlo Ersek
2018-04-27 19:28 ` [Qemu-devel] [PATCH v3 4/5] qapi: discriminate CpuInfoFast on SysEmuTarget, not CpuInfoArch Laszlo Ersek
2018-05-02 7:57 ` Markus Armbruster
2018-04-27 19:28 ` [Qemu-devel] [PATCH v3 5/5] qapi: deprecate CpuInfoFast.arch Laszlo Ersek
2018-04-27 19:55 ` Eric Blake
2018-05-02 7:56 ` Markus Armbruster
2018-05-02 8:31 ` [Qemu-devel] [PATCH v3 0/5] qapi: introduce the SysEmuTarget enumeration Markus Armbruster
2018-05-02 8:49 ` Laszlo Ersek
2018-05-02 9:40 ` Markus Armbruster
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=5853853e-fa05-2dcf-0c8e-6b812222c453@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=lersek@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 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).