lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 7 Nov 2006 23:33:23 -0800
From:	Andrew Morton <akpm@...l.org>
To:	Avi Kivity <avi@...ranet.com>
Cc:	Roland Dreier <rdreier@...co.com>, kvm-devel@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/14] KVM: Kernel-based Virtual Machine (v4)

On Wed, 08 Nov 2006 09:14:50 +0200
Avi Kivity <avi@...ranet.com> wrote:

> Roland Dreier wrote:
> >  > That's gas 2.16.1.  I assume it needs some super-new binutils.
> >  > 
> >  > I'm not sure what to do about this.  What's the minimum version?
> >
> > According to http://kvm.sourceforge.net/howto.html :
> >     A recent enough binutils (>= 2.16.91.0.2) for vmx instruction support
> >   
> 
> Either that or a bunch of ugly .byte macros.
> 

I think we could live with the binutils requirement as long as we can find
some automagic way of not breaking people's `make allmodconfig'.  Because
quite a lot of those people who do cross-compilation tend to use older
binutilses.

But I don't know how to do that.  We _could_ do a trick similar to the
`cc-version' make rule, and then use the new `as-version' to make the whole
kvm.o compile down to an empty .o file.  But that's pretty hacky.  Would
really prefer something at Kconfig-time, but we have no way of letting the
assembler version feed into the Kconfig system (nor do we want it, I
suspect).

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ