From: Paolo Bonzini <pbonzini@redhat.com>
To: Heiher <r@hev.cc>, Richard Henderson <rth@twiddle.net>,
Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC v1] i386: hvf: Fix smp boot hangs
Date: Wed, 23 Jan 2019 10:45:05 +0100 [thread overview]
Message-ID: <f79c9b64-5219-302e-1f0b-750e35ecb1fe@redhat.com> (raw)
In-Reply-To: <20190123073402.28465-1-r@hev.cc>
On 23/01/19 08:34, Heiher wrote:
> The machine that with hvf accelerator and smp sometimes boot hangs
> because all processors are executing instructions at startup,
> including early I/O emulations. We should just allow the bootstrap
> processor to initialize the machine and then to wake up slave
> processors by interrupt.
>
> Signed-off-by: Heiher <r@hev.cc>
> ---
> target/i386/hvf/hvf.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/target/i386/hvf/hvf.c b/target/i386/hvf/hvf.c
> index e193022c03..0921fcba45 100644
> --- a/target/i386/hvf/hvf.c
> +++ b/target/i386/hvf/hvf.c
> @@ -499,7 +499,6 @@ void hvf_reset_vcpu(CPUState *cpu) {
> }
>
> hv_vm_sync_tsc(0);
> - cpu->halted = 0;
> hv_vcpu_invalidate_tlb(cpu->hvf_fd);
> hv_vcpu_flush(cpu->hvf_fd);
> }
> @@ -582,8 +581,6 @@ int hvf_init_vcpu(CPUState *cpu)
>
> wvmcs(cpu->hvf_fd, VMCS_TPR_THRESHOLD, 0);
>
> - hvf_reset_vcpu(cpu);
Why this?
> x86cpu = X86_CPU(cpu);
> x86cpu->env.xsave_buf = qemu_memalign(4096, 4096);
>
> @@ -659,8 +656,6 @@ int hvf_vcpu_exec(CPUState *cpu)
> int ret = 0;
> uint64_t rip = 0;
>
> - cpu->halted = 0;
> -
> if (hvf_process_events(cpu)) {
> return EXCP_HLT;
> }
>
Looks good apart from the question above.
Paoo
next prev parent reply other threads:[~2019-01-23 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 7:34 [Qemu-devel] [PATCH RFC v1] i386: hvf: Fix smp boot hangs Heiher
2019-01-23 9:45 ` Paolo Bonzini [this message]
2019-01-23 11:05 ` Heiher
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=f79c9b64-5219-302e-1f0b-750e35ecb1fe@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=r@hev.cc \
--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).