On Thu, Feb 9, 2012 at 5:00 PM, Eliot Moss <[email protected]> wrote:
> I was wrong :-( ...
>
> 0x66 0x0F 0x3A 0xDF appears to be AESKEYGENASSIST.
> Someone else will have to address that (if at all).
>
> Sorry ... Eliot
There used to be a bug about incorrect declaration of AESKEYGENASSIST:
https://bugs.kde.org/show_bug.cgi?id=249991
Can you please try this code:
====================
#include <stdio.h>
int main() {
unsigned int result = -1;
asm volatile(
"mov $0x1, %%eax\n"
"cpuid\n"
"mov $0x02000000, %%eax\n"
"and %%eax, %%ecx\n"
"mov %%ecx, %0\n": "=r"(result));
printf("%x\n", result);
return 0;
}
====================
under Valgrind on your machine?
If it returns 0, it means that the code you're running is incorrectly
assuming AES support on the CPU (this is still a reason to fix
AESKEYGENASSIST)
Otherwise cpuid is broken under Valgrind.
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
