On Tue, 2011-11-08 at 20:32 +0100, Andy Polyakov via RT wrote:
> >> As for XEN, if it in fact masks XSAVE, but not AVX bits, than even
> >> check for XSAVE bit should '&jnc (&label("clear_avx"));' instead of
> >> "done". As well as that x86_64cpuid.pl should test for XSAVE...
> >
> > That would also work, but it's useless because the spec OTOH says that
> > you *can* ignore XSAVE (and anyway XSAVE means nothing: it says the
> > feature is available, but only OSXSAVE says it is actually unusable).
>
> I still fail to see how exactly did it fail for you. Once again, which
> flags does guest OS observe exactly? Is guest OS YMM-capable? Does
> latest x86cpuid.pl work for you or is it still problem?
No, it does not work as the cpuid on the guest OS observes cleared XSAVE
and set AVX bit. Which means that the AVX instructions will be used in
the SHA1 code which then fail with SIGILL.
The OSXSAVE is also cleared so that means if the XSAVE test was just
dropped it would work.
--
Tomas Mraz
No matter how far down the wrong road you've gone, turn back.
Turkish proverb
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
