From: Heiher <r@hev.cc>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Richard Henderson <rth@twiddle.net>,
Eduardo Habkost <ehabkost@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC v1] i386: hvf: Fix smp boot hangs
Date: Wed, 23 Jan 2019 19:05:36 +0800 [thread overview]
Message-ID: <CAHirt9h89R5gjevChbQdgcsAeFoYFfiLeHUPfYKHxLPVh62Csg@mail.gmail.com> (raw)
In-Reply-To: <f79c9b64-5219-302e-1f0b-750e35ecb1fe@redhat.com>
On Wed, Jan 23, 2019 at 5:45 PM Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> 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?
It looks redundant. I think it is enough to reset vcpu from
x86_cpu_reset, likes kvm.
https://git.qemu.org/?p=qemu.git;a=blob;f=target/i386/cpu.c;h=2f5412592d30ea7a24810f3bf6a8c7d4b035a0f9;hb=952bc8b3c2cbba78261923a1e8ca55cda261dee9#l4732
Do you think it is correct?
>
> > 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
Thank you reply.
--
Best regards!
Hev
https://hev.cc
prev parent reply other threads:[~2019-01-23 11:06 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
2019-01-23 11:05 ` Heiher [this message]
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=CAHirt9h89R5gjevChbQdgcsAeFoYFfiLeHUPfYKHxLPVh62Csg@mail.gmail.com \
--to=r@hev.cc \
--cc=ehabkost@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).