virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Molle Bestefich <molle.bestefich@gmail.com>
Cc: virtualization@lists.osdl.org, xen-users@lists.xensource.com
Subject: Re: Virtualization + CPU w/crypto acceleration instructions
Date: Mon, 12 Mar 2007 12:44:45 -0700	[thread overview]
Message-ID: <45F5ADAD.2030902@goop.org> (raw)
In-Reply-To: <62b0912f0703121235l2001eaadra87e9022a8a8c0db@mail.gmail.com>

Molle Bestefich wrote:
> In a virtualized environment running Xen or VMware, can the guest
> operating systems utilize hardware crypto acceleration such as the
> "PadLock" AES acceleration built into VIA CPUs?
>   

If they're unprivileged instructions, then they should just work.  If
its done via MSRs or some other ring0 mechanism, it might be more tricky.

    J

  reply	other threads:[~2007-03-12 19:44 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 [this message]
2007-03-12 19:50 ` Kraska, Joe A (US SSA)
2007-03-12 23:46 ` Zachary Amsden
2007-03-13  0:04   ` Jeremy Fitzhardinge

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=45F5ADAD.2030902@goop.org \
    --to=jeremy@goop.org \
    --cc=molle.bestefich@gmail.com \
    --cc=virtualization@lists.osdl.org \
    --cc=xen-users@lists.xensource.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).