linux-kernel - Re: [PATCH 0/14] KVM: Kernel-based Virtual Machine (v4)

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20061108003028.6212045b.akpm@osdl.org>
Date:	Wed, 8 Nov 2006 00:30:28 -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 10:07:15 +0200
Avi Kivity <avi@...ranet.com> wrote:

> Andrew Morton wrote:
> > 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.
> >   
> 
> These crosses are usually for $wierd target on x86 host, right?

Not necessarily.  If you're going to build kernels with distcc then you
need the same toolchain on all machines, so you probably build it with
crosstool.

Or if you want a consistent, tested, internally-maintained build
environment then you use a specific toolchain so your developers aren't
dependent on whatever their distro happened to put in /usr/bin

> 
> config AS_VERSION
>         eval as --version | awk '{ ... }'
> 
> ?

It'd be more complex than that :(
-
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/