Re: [libvirt] [PATCH] "pclmuldq" was introduced with Westmere, not Sandy Bridge. This feature is important to get proper performance for aes-128-gcm in openssl, an important cipher for https communica

On Wed, Oct 08, 2014 at 09:49:35AM +0200, Jiri Denemark wrote: > > Technically you are correct and even QEMU added this feature to Westmere > in April 2013. However, our goal is to provide stable virtual hardware > that doesn't change when, e.g., a domain is migrated to another machine > (let's ig

Re: [libvirt] [PATCH] "pclmuldq" was introduced with Westmere, not Sandy Bridge. This feature is important to get proper performance for aes-128-gcm in openssl, an important cipher for https communica

Just some documentation for the fact that this was introduced with Westmere: https://software.intel.com/sites/default/files/managed/72/cc/clmul-wp-rev-2.02-2014-04-20.pdf "Intel® PCLMULQDQ instruction is a new instruction available beginning with the all new 2010 Intel®

[libvirt] [PATCH] "pclmuldq" was introduced with Westmere, not Sandy Bridge. This feature is important to get proper performance for aes-128-gcm in openssl, an important cipher for https communication

Signed-off-by: Jan-Frode Myklebust --- src/cpu/cpu_map.xml |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/cpu/cpu_map.xml b/src/cpu/cpu_map.xml index 18c7b0d..94f1458 100644 --- a/src/cpu/cpu_map.xml +++ b/src/cpu/cpu_map.xml @@ -488,11 +488,11