From: David Hopwood <david.nospam.hopwood@blueyonder.co.uk>
To: xen-devel@lists.sourceforge.net
Subject: Re: running Windows (albeit slowly)
Date: Wed, 24 Nov 2004 17:08:24 +0000 [thread overview]
Message-ID: <41A4C008.1000003@blueyonder.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.60.0411241301070.23620@hermes-1.csi.cam.ac.uk>
Mark Williamson wrote:
>> Under the opinion that there is no crime if optimization fails on
>> incorrect code, would it not be appropriate to do all the things
>> necessary to run Windows unmodified albeit poorly slash slowly?
>
> It's not just that the modifications improve performance, guests
> actually need to be modified to work on Xen at all.
Supporting full virtualization on x86 is *much* more complicated
than Xen-style paravirtualization, mainly because the x86 has some
instructions that are not privileged, but reveal state that needs to
be virtualized.
> When Intel's VT extensions come out, supporting unmodified guests will
> be rather easier.
Is there any information available on what the extensions will be?
> Yeah, speech recognition on Linux (and others) is a bit of a pain.
There was recently a big fanfare about IBM open-sourcing some of their
speech recognition code, but I don't know how much development it needs.
--
David Hopwood <david.nospam.hopwood@blueyonder.co.uk>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-11-24 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 12:38 running Windows (albeit slowly) Eric S. Johansson
2004-11-24 13:09 ` Mark Williamson
2004-11-24 14:15 ` Eric S. Johansson
2004-11-24 16:36 ` M.A. Williamson
2004-11-24 14:50 ` Dave Feustel
2004-11-24 17:08 ` David Hopwood [this message]
2004-11-24 13:27 ` Steven Hand
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=41A4C008.1000003@blueyonder.co.uk \
--to=david.nospam.hopwood@blueyonder.co.uk \
--cc=xen-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.