Re: [kvm-devel] [PATCH] portability: add top level config-$arch files v2

2008-01-10 Thread Avi Kivity
Christian Ehrhardt wrote: > This includes the comments from Jerone. Moving the targets back into the > Makefile e.g. easen things for people looking at the Makefile for the first > time and looking for targets. So here v2 of the patch. > changes to v1: > - defining per arch targets via variables i

[kvm-devel] [PATCH] portability: add top level config-$arch files v2

2008-01-09 Thread Christian Ehrhardt
This includes the comments from Jerone. Moving the targets back into the Makefile e.g. easen things for people looking at the Makefile for the first time and looking for targets. So here v2 of the patch. changes to v1: - defining per arch targets via variables in config-$arch - removed that user

Re: [kvm-devel] [PATCH] portability: add top level config-$arch files

2008-01-08 Thread Jerone Young
This is a patch that we do need. Though instead of redefining "qemu" target in every config file. It's best to use a variable and have "qemu" target in the main Makefile use that variable for dependencies. example: Makefile qemu: $(ARCH_QEMU_DEP) config-x86 ARCH_QEMU_DEP = libkvm extb

[kvm-devel] [PATCH] portability: add top level config-$arch files

2008-01-08 Thread Christian Ehrhardt
Subject: [PATCH] portability: add top level config-$arch files From: Christian Ehrhardt <[EMAIL PROTECTED]> This allows per arch configuration for the top level Makefile of kvm-userspace e.g. allowing to disable extboot for non x86 or disabling kvmctl build until ported to an architecture. I'm awa