public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Nico Prenzel <nico.prenzel@pn-systeme.de>
Cc: kvm@vger.kernel.org
Subject: Re: Passthrough VIA CPU Features
Date: Mon, 27 Dec 2010 14:54:41 +0200	[thread overview]
Message-ID: <4D188C91.2060604@redhat.com> (raw)
In-Reply-To: <OFFD2EB891.448079FB-ONC1257806.00456081-C1257806.0045608D@pn-systeme.de>

On 12/27/2010 02:37 PM, Nico Prenzel wrote:
> Hello KVM developers,
>
> I've recently bought such a nice low-power board from VIA (EPIA M-850).
> The included VIA cpu (VIA NANO U3100) contains of in-silicon features (esp. AES and SHA encryption):
>
> /* VIA/Cyrix/Centaur-defined CPU features, CPUID level 0xC0000001, word 5 */
> #define X86_FEATURE_XSTORE      (5*32+ 2) /* on-CPU RNG present (xstore insn) */
> #define X86_FEATURE_XSTORE_EN   (5*32+ 3) /* on-CPU RNG enabled */
> #define X86_FEATURE_XCRYPT      (5*32+ 6) /* on-CPU crypto (xcrypt insn) */
> #define X86_FEATURE_XCRYPT_EN   (5*32+ 7) /* on-CPU crypto enabled */
> #define X86_FEATURE_ACE2        (5*32+ 8) /* Advanced Cryptography Engine v2 */
> #define X86_FEATURE_ACE2_EN     (5*32+ 9) /* ACE v2 enabled */
> #define X86_FEATURE_PHE         (5*32+ 10) /* PadLock Hash Engine */
> #define X86_FEATURE_PHE_EN      (5*32+ 11) /* PHE enabled */
> #define X86_FEATURE_PMM         (5*32+ 12) /* PadLock Montgomery Multiplier */
> #define X86_FEATURE_PMM_EN      (5*32+ 13) /* PMM enabled */
>
>
> Now, I'd like to use these features in one of my linux driven kvm-guests to gain the performance of in-silicon encryption.
> See some benchmark what performance gain to expect: http://www.logix.cz/michal/devel/padlock/bench.xp
>
> I've found some useful informations about how to pass cpu features to kvm guests in generally. But they simply won't work if I try to pass the phe(_en)/pmm(_en) feautres to a kvm guest.
>
> So my questions by now, would be: Is it generally possible to passthrough these features?

In general cpu features are easy to pass through.  Sometimes all that is 
needed is to enable the cpuid bits in the virtual cpu, sometimes more 
support is needed (generally when extra registers or new bits in 
existing registers are defined).  Someone needs to read the 
documentation and check what's needed to be done for each feature.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-12-27 12:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27 12:37 Passthrough VIA CPU Features Nico Prenzel
2010-12-27 12:54 ` Avi Kivity [this message]
2010-12-27 14:05   ` Antwort: " Nico Prenzel
2010-12-27 14:18     ` Avi Kivity

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=4D188C91.2060604@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=nico.prenzel@pn-systeme.de \
    /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