From: Markus Armbruster <armbru@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
qemu-devel@nongnu.org, "Eduardo Habkost" <ehabkost@redhat.com>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] qapi/misc.json is too big, let's bite off a few chunks
Date: Fri, 07 Jun 2019 14:45:01 +0200 [thread overview]
Message-ID: <875zphd0oi.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <3a4ce577-0744-6ff7-9f7e-9239fe5d4333@redhat.com> (Paolo Bonzini's message of "Fri, 7 Jun 2019 13:35:09 +0200")
Paolo Bonzini <pbonzini@redhat.com> writes:
> On 07/06/19 10:25, Markus Armbruster wrote:
>> Paolo Bonzini <pbonzini@redhat.com> writes:
>>
>>> On 23/05/19 18:14, Markus Armbruster wrote:
>>>> * Machine core (Eduardo, Marcel)
>>>>
>>>> query-machines, query-current-machine,
>>>>
>>>> ~60 lines. Hardly worthwhile from a "let's shrink misc.json" point of
>>>> view. Might be worthwhile from a "let's make get_maintainers.pl
>>>> work".
>>>>
>>>> * CPUs (Paolo, Richard)
>>>>
>>>> query-cpus, query-cpus-fast
>>>>
>>>> ~300 lines. The commands are implemented in cpus.c, which MAINTAINERS
>>>> covers both under "Main loop" and under "Guest CPU cores (TCG) /
>>>> Overall". Neither feels right to me for these QMP commands.
>>>>
>>>> * NUMA (Eduardo)
>>>>
>>>> query-memdev, set-numa-node
>>>>
>>>> ~200 lines.
>>>
>>> I would move all three of these and add a new entry to MAINTAINERS.
>>
>> Double-checking: do you propose to move all three to a single new QAPI
>> module, with a new MAINTAINERS entry covering just the new QAPI module?
>> If yes, care to propose a QAPI module file name, a MAINTAINERS head
>> line, and maintainers?
>
> Just one, qapi/machine.json, with a MAINTAINERS patch based on this one.
Okay, I'd like to take care of that.
> We could probably create a new directory hw/machine too.
I'd prefer to leave that to you, because making you explain to me what
exactly you want moved is likely more work for both of us :)
> diff --git a/MAINTAINERS b/MAINTAINERS
> index a96829ea83..9bf3e6b670 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1274,8 +1274,12 @@ S: Supported
> F: hw/core/machine.c
> F: hw/core/null-machine.c
> F: hw/cpu/cluster.c
> +F: numa.c
> +F: qom/cpu.c
> F: include/hw/boards.h
> F: include/hw/cpu/cluster.h
> +F: include/qom/cpu.h
> +F: include/sysemu/numa.h
> T: git https://github.com/ehabkost/qemu.git machine-next
>
> Xtensa Machines
> @@ -1839,12 +1843,6 @@ M: Markus Armbruster <armbru@redhat.com>
> S: Supported
> F: scripts/coverity-model.c
>
> -CPU
> -L: qemu-devel@nongnu.org
> -S: Supported
> -F: qom/cpu.c
> -F: include/qom/cpu.h
> -
> Device Tree
> M: Alistair Francis <alistair.francis@wdc.com>
> R: David Gibson <david@gibson.dropbear.id.au>
> @@ -1947,13 +1945,6 @@ W: http://info.iet.unipi.it/~luigi/netmap/
> S: Maintained
> F: net/netmap.c
>
> -NUMA
> -M: Eduardo Habkost <ehabkost@redhat.com>
> -S: Maintained
> -F: numa.c
> -F: include/sysemu/numa.h
> -T: git https://github.com/ehabkost/qemu.git machine-next
> -
> Host Memory Backends
> M: Eduardo Habkost <ehabkost@redhat.com>
> M: Igor Mammedov <imammedo@redhat.com>
This merges MAINTAINERS section "NUMA" into "Machine core" (with section
"CPU" thrown in for good measure). Moving their QAPI schema bits from
misc.json to new machine.json then makes sense. Good.
The part I'm unsure about is item "CPUs" from my list, i.e. query-cpus
and query-cpus-fast. If I move these QAPI schema bits to machine.json
as well, then the QAPI schema for query-cpus, query-cpus-fast is covered
by section "Machine core", while the C code (in cpus.c) is covered by
"Main loop" and "Guest CPU cores (TCG) / Overall". I hate that. Would
you like me to try moving the C code out of cpus.c so it can be covered
by "Machine core"?
[...]
next prev parent reply other threads:[~2019-06-07 12:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 16:14 [Qemu-devel] qapi/misc.json is too big, let's bite off a few chunks Markus Armbruster
2019-05-24 18:31 ` Paolo Bonzini
2019-06-07 8:25 ` Markus Armbruster
2019-06-07 11:35 ` Paolo Bonzini
2019-06-07 12:45 ` Markus Armbruster [this message]
2019-06-11 21:20 ` Eduardo Habkost
2019-05-24 18:53 ` Eduardo Habkost
2019-05-27 8:00 ` Markus Armbruster
2019-05-27 10:03 ` Paolo Bonzini
2019-05-28 19:37 ` Eduardo Habkost
2019-06-07 6:59 ` Markus Armbruster
2019-06-07 8:33 ` Philippe Mathieu-Daudé
2019-06-07 12:25 ` Markus Armbruster
2019-06-07 9:59 ` Daniel P. Berrangé
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=875zphd0oi.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).