From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: Tonnerre <tonnerre@thundrix.ch>, Ville Herva <vherva@viasys.com>,
Arjan van de Ven <arjanv@redhat.com>,
Andrew Morton <akpm@osdl.org>,
petr@vandrovec.name,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8.1-mm2 breaks vmware
Date: Sun, 22 Aug 2004 15:15:32 +0100 [thread overview]
Message-ID: <1093184131.24597.0.camel@localhost.localdomain> (raw)
In-Reply-To: <20040822135923.GA24092@vana.vc.cvut.cz>
On Sul, 2004-08-22 at 14:59, Petr Vandrovec wrote:
> > Does VMware > 4.0 still require cmov?
>
> Yes, this requirement is not going to go away: VMware >= 4.0 / GSX >= 3.0 require
> processors which support CMOV instruction.
qemu isnt as fast and isnt as featured but doesn't need cmov. The
current one runs stuff like Win98 rather well including PCI video card
emulation.
Alan
next prev parent reply other threads:[~2004-08-22 15:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 10:42 2.6.8.1-mm2 breaks vmware Ville Herva
2004-08-20 10:51 ` Andrew Morton
2004-08-20 13:18 ` Ville Herva
2004-08-20 14:43 ` Ville Herva
2004-08-20 15:16 ` Ville Herva
2004-08-20 18:45 ` Andrew Morton
2004-08-20 18:49 ` Arjan van de Ven
2004-08-20 19:30 ` Ville Herva
2004-08-22 11:42 ` Tonnerre
2004-08-22 13:59 ` Petr Vandrovec
2004-08-22 14:15 ` Alan Cox [this message]
2004-08-20 19:25 ` Ville Herva
2004-08-21 6:29 ` Ville Herva
[not found] ` <20040821134918.GA1585@devserv.devel.redhat.com>
[not found] ` <20040821190027.GQ3024@viasys.com>
[not found] ` <20040821190730.GA25932@devserv.devel.redhat.com>
2004-08-22 14:31 ` Petr Vandrovec
2004-08-22 15:07 ` Arjan van de Ven
2004-08-22 21:19 ` Ville Herva
2004-08-23 5:53 ` [OT] vmware, 2.6 kernel and altgr key (Re: 2.6.8.1-mm2 breaks vmware) Ville Herva
2004-08-20 12:11 ` 2.6.8.1-mm2 breaks vmware Arjan van de Ven
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=1093184131.24597.0.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=petr@vandrovec.name \
--cc=tonnerre@thundrix.ch \
--cc=vandrove@vc.cvut.cz \
--cc=vherva@viasys.com \
/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