OPENSSL_ia32cap.pod 1.7 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243
  1. =pod
  2. =head1 NAME
  3. OPENSSL_ia32cap - finding the IA-32 processor capabilities
  4. =head1 SYNOPSIS
  5. unsigned long *OPENSSL_ia32cap_loc(void);
  6. #define OPENSSL_ia32cap (*(OPENSSL_ia32cap_loc()))
  7. =head1 DESCRIPTION
  8. Value returned by OPENSSL_ia32cap_loc() is address of a variable
  9. containing IA-32 processor capabilities bit vector as it appears in EDX
  10. register after executing CPUID instruction with EAX=1 input value (see
  11. Intel Application Note #241618). Naturally it's meaningful on IA-32[E]
  12. platforms only. The variable is normally set up automatically upon
  13. toolkit initialization, but can be manipulated afterwards to modify
  14. crypto library behaviour. For the moment of this writing six bits are
  15. significant, namely:
  16. 1. bit #28 denoting Hyperthreading, which is used to distiguish
  17. cores with shared cache;
  18. 2. bit #26 denoting SSE2 support;
  19. 3. bit #25 denoting SSE support;
  20. 4. bit #23 denoting MMX support;
  21. 5. bit #20, reserved by Intel, is used to choose between RC4 code
  22. pathes;
  23. 6. bit #4 denoting presence of Time-Stamp Counter.
  24. For example, clearing bit #26 at run-time disables high-performance
  25. SSE2 code present in the crypto library. You might have to do this if
  26. target OpenSSL application is executed on SSE2 capable CPU, but under
  27. control of OS which does not support SSE2 extentions. Even though you
  28. can manipulate the value programmatically, you most likely will find it
  29. more appropriate to set up an environment variable with the same name
  30. prior starting target application, e.g. on Intel P4 processor 'env
  31. OPENSSL_ia32cap=0x12900010 apps/openssl', to achieve same effect
  32. without modifying the application source code. Alternatively you can
  33. reconfigure the toolkit with no-sse2 option and recompile.
  34. =cut