qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1469342] Re: qemu-i386 pentium3/athlon incorrect instruction set
Date: Fri, 18 Sep 2015 13:04:08 -0000	[thread overview]
Message-ID: <20150918130408.3195.54740.malone@wampee.canonical.com> (raw)
In-Reply-To: 20150627003937.6939.65806.malonedeb@gac.canonical.com

QEMU doesn't try to mimic the exact set of instructions for a processor,
unfortunately. Virtualization solutions like KVM also do not allow you
to do that, so the case for this feature is relatively minor.

However, patches are welcome.

** Changed in: qemu
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1469342

Title:
  qemu-i386 pentium3/athlon incorrect instruction set

Status in QEMU:
  Won't Fix

Bug description:
  Running a binary containing a movsd instruction (SSE2) in 32-bit
  qemu-i386 from 20150609 using the -cpu pentium3 switch results in
  flawless execution whereas it should crash with SIGILL as P3 only had
  SSE and not SSE2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1469342/+subscriptions

  parent reply	other threads:[~2015-09-18 13:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-27  0:39 [Qemu-devel] [Bug 1469342] [NEW] qemu-i386 pentium3 incorrect instruction set PeteVine
2015-09-18 12:37 ` [Qemu-devel] [Bug 1469342] " PeteVine
2015-09-18 13:04 ` Paolo Bonzini [this message]
2015-09-18 13:34 ` [Qemu-devel] [Bug 1469342] Re: qemu-i386 pentium3/athlon " PeteVine
2015-09-18 13:58 ` PeteVine
2015-09-18 14:31 ` PeteVine
2015-09-19 10:13 ` Marina Kovalevna
2015-09-25 22:47 ` PeteVine

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=20150918130408.3195.54740.malone@wampee.canonical.com \
    --to=bonzini@gnu.org \
    --cc=1469342@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).