From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Zachary Amsden <zach@vmware.com>
Cc: virtualization@lists.osdl.org,
Molle Bestefich <molle.bestefich@gmail.com>,
xen-users@lists.xensource.com
Subject: Re: Virtualization + CPU w/crypto acceleration instructions
Date: Mon, 12 Mar 2007 17:04:06 -0700 [thread overview]
Message-ID: <45F5EA76.4080805@goop.org> (raw)
In-Reply-To: <45F5E64C.1050604@vmware.com>
Zachary Amsden wrote:
> VMware doesn't support VIA CPUs, and I think we would have compatibility
> issues with these instructions. In general, most hypervisors would need
> to support decoding of the new instructions for complete emulation in
> various fault and corner cases.
Using a crypto instruction to update a pagetable would be... interesting ;)
J
prev parent reply other threads:[~2007-03-13 0:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 19:35 Virtualization + CPU w/crypto acceleration instructions Molle Bestefich
2007-03-12 19:44 ` Jeremy Fitzhardinge
2007-03-12 19:50 ` Kraska, Joe A (US SSA)
2007-03-12 23:46 ` Zachary Amsden
2007-03-13 0:04 ` Jeremy Fitzhardinge [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=45F5EA76.4080805@goop.org \
--to=jeremy@goop.org \
--cc=molle.bestefich@gmail.com \
--cc=virtualization@lists.osdl.org \
--cc=xen-users@lists.xensource.com \
--cc=zach@vmware.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;
as well as URLs for NNTP newsgroup(s).