From: Andre Przywara <andre.przywara@amd.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Keir Fraser <keir@xen.org>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH 2/2] hvm: allow pass-through of new CPUID features
Date: Thu, 27 Jan 2011 16:43:16 +0100 [thread overview]
Message-ID: <4D419294.6010806@amd.com> (raw)
In-Reply-To: <19777.34552.594880.846926@mariner.uk.xensource.com>
Ian Jackson wrote:
> Stefano Stabellini writes ("Re: [Xen-devel] [PATCH 2/2] hvm: allow pass-through of new CPUID features"):
>> I think Ian was just looking for a well written explanation of why we
>> need this now :)
OK, I feel challenged, what about this:
The new CPU features are pure "compute" features (ALU/FPU only), they
don't need any support or awareness from any system level software.
Following the definition of virtualization they should be available to
guests unless explicitly disabled.
The AES feature was introduced at the same time as the PCLMULQDQ
feature, AES is passed through, PCLMULQDQ has obviously been forgotten(?).
The Linux kernel uses both instructions in newer versions for optimized
cryptographic algorithms implementation
(arch/x86/crypto/ghash-clmulni-intel_asm.S)
The current version of the Xen hypervisor would deny this feature to any
PV domains, including Dom0, leaving systems running under Xen with an
inferior cryptographic performance.
This patch allows PV domains to use the feature to get on par with
systems running with other virtualization software.
Regards,
Andre.
--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
next prev parent reply other threads:[~2011-01-27 15:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 14:04 [PATCH 2/2] hvm: allow pass-through of new CPUID features Andre Przywara
2011-01-26 16:05 ` Ian Jackson
2011-01-27 12:05 ` Andre Przywara
2011-01-27 12:13 ` Stefano Stabellini
2011-01-27 14:53 ` Ian Jackson
2011-01-27 15:43 ` Andre Przywara [this message]
2011-01-27 15:56 ` Andre Przywara
2011-01-27 19:50 ` Ian Jackson
2011-01-27 16:07 ` Keir Fraser
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=4D419294.6010806@amd.com \
--to=andre.przywara@amd.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=keir@xen.org \
--cc=xen-devel@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 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.