mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Avi Kivity <avi@qumranet.com>
Cc: Roland Dreier <rdreier@cisco.com>,
	kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/14] KVM: Kernel-based Virtual Machine (v4)
Date: Wed, 8 Nov 2006 00:30:28 -0800	[thread overview]
Message-ID: <20061108003028.6212045b.akpm@osdl.org> (raw)
In-Reply-To: <45519033.3060409@qumranet.com>

On Wed, 08 Nov 2006 10:07:15 +0200
Avi Kivity <avi@qumranet.com> wrote:

> Andrew Morton wrote:
> > On Wed, 08 Nov 2006 09:14:50 +0200
> > Avi Kivity <avi@qumranet.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 :(

  reply	other threads:[~2006-11-08  8:30 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-05 20:27 Avi Kivity
2006-11-05 20:29 ` [PATCH 1/14] KVM: userspace interface Avi Kivity
2006-11-06 10:03   ` Arjan van de Ven
2006-11-06 10:28     ` Avi Kivity
2006-11-06 10:32       ` Arjan van de Ven
2006-11-06 10:47         ` Avi Kivity
2006-11-05 20:30 ` [PATCH 2/14] KVM: Intel virtual mode extensions definitions Avi Kivity
2006-11-05 20:31 ` [PATCH 3/14] KVM: kvm data structures Avi Kivity
2006-11-05 20:32 ` [PATCH 4/14] KVM: random accessors and constants Avi Kivity
2006-11-05 20:33 ` [PATCH 5/14] KVM: virtualization infrastructure Avi Kivity
2006-11-05 20:34 ` [PATCH 6/14] KVM: memory slot management Avi Kivity
2006-11-05 20:35 ` [PATCH 7/14] KVM: vcpu creation and maintenance Avi Kivity
2006-11-05 20:36 ` [PATCH 8/14] KVM: vcpu execution loop Avi Kivity
2006-11-05 20:37 ` [PATCH 9/14] KVM: define exit handlers Avi Kivity
2006-11-05 20:38 ` [PATCH 10/14] KVM: less common " Avi Kivity
2006-11-05 20:39 ` [PATCH 11/14] KVM: mmu Avi Kivity
2006-11-05 20:40 ` [PATCH 12/14] KVM: x86 emulator Avi Kivity
2006-11-07 12:49   ` Pavel Machek
2006-11-07 12:55     ` Avi Kivity
2006-11-07 13:00       ` Arjan van de Ven
2006-11-07 13:22         ` Avi Kivity
2006-11-07 13:35           ` Miguel Ojeda
2006-11-07 13:44           ` Arjan van de Ven
2006-11-07 13:12       ` Hesse, Christian
2006-11-08 16:54         ` David Bristow
2006-11-05 20:41 ` [PATCH 13/14] KVM: plumbing Avi Kivity
2006-11-05 20:42 ` [PATCH 14/14] KVM: Dynamically determine which msrs to load and save Avi Kivity
2006-11-07 16:59 ` [PATCH 0/14] KVM: Kernel-based Virtual Machine (v4) Yinghai Lu
2006-11-07 19:56   ` Avi Kivity
2006-11-08  4:44 ` Andrew Morton
2006-11-08  4:51   ` Roland Dreier
2006-11-08  7:14     ` Avi Kivity
2006-11-08  7:33       ` Andrew Morton
2006-11-08  8:07         ` Avi Kivity
2006-11-08  8:30           ` Andrew Morton [this message]
2006-11-08  9:39           ` Arjan van de Ven
2006-11-08  9:54             ` Avi Kivity
2006-11-08 10:01               ` Arjan van de Ven
2006-11-08 10:10                 ` Avi Kivity
2006-11-08 18:26       ` Roland Dreier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061108003028.6212045b.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdreier@cisco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®