From: Wei Yang <richardw.yang@linux.intel.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Wei Yang <richard.weiyang@gmail.com>,
pbonzini@redhat.com, Wei Yang <richardw.yang@linux.intel.com>,
ehabkost@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] vl.c: allocate TYPE_MACHINE list once during bootup
Date: Wed, 3 Apr 2019 08:49:07 +0800 [thread overview]
Message-ID: <20190403004907.GA18346@richard> (raw)
In-Reply-To: <875zrw8k28.fsf@dusky.pond.sub.org>
On Tue, Apr 02, 2019 at 06:10:23PM +0200, Markus Armbruster wrote:
>Wei Yang <richard.weiyang@gmail.com> writes:
[...]
>>>>
>>>> @@ -2659,7 +2655,8 @@ static const QEMUOption *lookup_opt(int argc, char **argv,
>>>>
>>>> static MachineClass *select_machine(void)
>>>> {
>>>> - MachineClass *machine_class = find_default_machine();
>>>> + GSList *machines = object_class_get_list(TYPE_MACHINE, false);
>>>> + MachineClass *machine_class = find_default_machine(machines);
>>>> const char *optarg;
>>>> QemuOpts *opts;
>>>> Location loc;
>>>> @@ -2671,7 +2668,7 @@ static MachineClass *select_machine(void)
>>>>
>>>> optarg = qemu_opt_get(opts, "type");
>>>> if (optarg) {
>>>> - machine_class = machine_parse(optarg);
>>>> + machine_class = machine_parse(optarg, machines);
>>>
>>>Could create and destroy @machines here:
>>>
>>> - machine_class = machine_parse(optarg);
>>> + GSList *machines = object_class_get_list(TYPE_MACHINE, false);
>>> + machine_class = machine_parse(optarg, machines);
>>> + g_slist_free(machines);
>>>
>>>Matter of taste.
>
>[*]
>
>Matter of taste means the choice between your version and mine is up to
>the maintainer, or if the maintainer remains silent, up to you.
>
Ok, I get your meaning.
But machines should be used in find_default_machine(), after move the
allocation in "if", would there be a problem?
I may not understand your point here.
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2019-04-03 0:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 6:08 [Qemu-devel] [PATCH 0/2] cleanup select_machine Wei Yang
2019-03-11 6:08 ` [Qemu-devel] [PATCH 1/2] vl.c: make find_default_machine() local Wei Yang
2019-04-02 6:33 ` Markus Armbruster
2019-04-02 15:07 ` Wei Yang
2019-04-02 15:17 ` Markus Armbruster
2019-03-11 6:08 ` [Qemu-devel] [PATCH 2/2] vl.c: allocate TYPE_MACHINE list once during bootup Wei Yang
2019-04-02 13:28 ` Markus Armbruster
2019-04-02 15:16 ` Wei Yang
2019-04-02 16:10 ` Markus Armbruster
2019-04-03 0:49 ` Wei Yang [this message]
2019-04-03 6:15 ` Markus Armbruster
2019-04-02 13:26 ` [Qemu-devel] [PATCH 3/4] vl: Clean up after previous commit Markus Armbruster
2019-04-03 22:10 ` Wei Yang
2019-04-04 15:49 ` Markus Armbruster
2019-04-02 13:26 ` [Qemu-devel] [PATCH 4/4] vl: Simplify machine_parse() Markus Armbruster
2019-04-03 22:32 ` Wei Yang
2019-04-04 16:05 ` Markus Armbruster
2019-04-04 23:15 ` Wei Yang
2019-04-04 23:15 ` Wei Yang
2019-04-05 5:39 ` Markus Armbruster
2019-04-05 5:39 ` 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=20190403004907.GA18346@richard \
--to=richardw.yang@linux.intel.com \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.weiyang@gmail.com \
/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).