From: "Alex Bennée" <alex.bennee@linaro.org>
To: Dou Liyang <douly.fnst@cn.fujitsu.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, rth@twiddle.net,
sergey.fedorov@linaro.org, izumi.taku@jp.fujitsu.com,
caoj.fnst@cn.fujitsu.com, fanc.fnst@cn.fujitsu.com
Subject: Re: [Qemu-devel] [PATCH v2] vl: Ensure the cpu_synchronize_all_post_init() in the appropriate location
Date: Fri, 27 Jan 2017 14:03:40 +0000 [thread overview]
Message-ID: <87y3xw8urn.fsf@linaro.org> (raw)
In-Reply-To: <1484746795-19523-1-git-send-email-douly.fnst@cn.fujitsu.com>
Dou Liyang <douly.fnst@cn.fujitsu.com> writes:
> At the Qemu initialization, we call the cpu_synchronize_all_post_init()
> to synchronize All CPU states to KVM in the ./vl.c::main().
>
> Currently, it is called before we initialize the CPUs, which created by
> "-device" command, So, these CPUs may be ignored to synchronize.
>
> The patch moves the numa_post_machine_init func in the appropriate
> location to make sure that all the CPUs has already been created
> when it is called.
This doesn't match what the patch does (the function is
cpu_synchronise_all_post_init) but I see another patch is already merged
that moved the NUMA one.
I'm afraid you'll need to re-base anyway because it no longer applies
cleanly.
>
> Signed-off-by: Dou Liyang <douly.fnst@cn.fujitsu.com>
> ---
>
> Change log v1-> v2:
> 1. Split it from
> https://lists.nongnu.org/archive/html/qemu-devel/2017-01/msg03354.html
> 2. Rewrite the log.
>
> vl.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/vl.c b/vl.c
> index c643d3f..38269be 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -4547,8 +4547,6 @@ int main(int argc, char **argv, char **envp)
>
> audio_init();
>
> - cpu_synchronize_all_post_init();
> -
> numa_post_machine_init();
>
> if (qemu_opts_foreach(qemu_find_opts("fw_cfg"),
> @@ -4571,6 +4569,9 @@ int main(int argc, char **argv, char **envp)
> device_init_func, NULL, NULL)) {
> exit(1);
> }
> +
> + cpu_synchronize_all_post_init();
> +
> rom_reset_order_override();
>
> /* Did we create any drives that we failed to create a device for? */
--
Alex Bennée
next prev parent reply other threads:[~2017-01-27 14:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 13:39 [Qemu-devel] [PATCH v2] vl: Ensure the cpu_synchronize_all_post_init() in the appropriate location Dou Liyang
2017-01-27 14:03 ` Alex Bennée [this message]
2017-02-01 1:29 ` Dou Liyang
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=87y3xw8urn.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=caoj.fnst@cn.fujitsu.com \
--cc=douly.fnst@cn.fujitsu.com \
--cc=fanc.fnst@cn.fujitsu.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sergey.fedorov@linaro.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).