From: Paul Goyette <1693649@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: Re: [Bug 1693649] Re: x86 pause misbehaves with -cpu haswell
Date: Fri, 22 May 2020 12:51:32 -0000 [thread overview]
Message-ID: <Pine.NEB.4.64.2005220550440.14012@speedy.whooppee.com> (raw)
In-Reply-To: 159012475963.7477.6476241369082913120.malone@gac.canonical.com
Seems ok now.
On Fri, 22 May 2020, Thomas Huth wrote:
> Can you still reproduce this issue with the latest version of QEMU
> (currently 5.0)?
>
> ** Changed in: qemu
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1693649
>
> Title:
> x86 pause misbehaves with -cpu haswell
>
> Status in QEMU:
> Incomplete
>
> Bug description:
> Using qemu-2.9.0
>
> When booting NetBSD using '-cpu haswell -smp 4', the system fails to
> initialize the additional CPUs. It appears as though the "application
> processor" enters routine x86_pause() but never returns.
>
> x86_pause() is simply two assembler instructions: 'pause; ret;'
>
> Replacing the routine with 'nop; nop; ret;' allows the system to
> proceed, of course without the benefit of the pause instruction on
> spin-loops!
>
> Additionally, booting with '-cpu phenom -smp 4' also works, although
> the system does seem confused about the type of CPU being used.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/1693649/+subscriptions
>
> !DSPAM:5ec7625658281532840571!
>
>
+--------------------+--------------------------+-----------------------+
| Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
| (Retired) | FA29 0E3B 35AF E8AE 6651 | paul@whooppee.com |
| Software Developer | 0786 F758 55DE 53BA 7731 | pgoyette@netbsd.org |
+--------------------+--------------------------+-----------------------+
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1693649
Title:
x86 pause misbehaves with -cpu haswell
Status in QEMU:
Incomplete
Bug description:
Using qemu-2.9.0
When booting NetBSD using '-cpu haswell -smp 4', the system fails to
initialize the additional CPUs. It appears as though the "application
processor" enters routine x86_pause() but never returns.
x86_pause() is simply two assembler instructions: 'pause; ret;'
Replacing the routine with 'nop; nop; ret;' allows the system to
proceed, of course without the benefit of the pause instruction on
spin-loops!
Additionally, booting with '-cpu phenom -smp 4' also works, although
the system does seem confused about the type of CPU being used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1693649/+subscriptions
next prev parent reply other threads:[~2020-05-22 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 0:44 [Qemu-devel] [Bug 1693649] [NEW] x86 pause misbehaves with -cpu haswell Paul Goyette
2017-05-26 4:40 ` [Qemu-devel] [Bug 1693649] " Paul Goyette
2020-05-22 5:19 ` Thomas Huth
2020-05-22 12:51 ` Paul Goyette [this message]
2020-05-22 19:25 ` Thomas Huth
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=Pine.NEB.4.64.2005220550440.14012@speedy.whooppee.com \
--to=1693649@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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).