From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [RFC] QEMU KVM target Date: Tue, 20 Feb 2007 09:26:30 -0600 Message-ID: <45DB1326.3060705@codemonkey.ws> References: <45DA4A16.4050804@codemonkey.ws> <45DAA108.8000501@qumranet.com> <45DAC3FF.1090208@qumranet.com> <45DB119A.8000809@codemonkey.ws> <45DB11FD.1050900@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel To: Avi Kivity Return-path: In-Reply-To: <45DB11FD.1050900-atKUWr5tajBWk0Htik3J/w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Avi Kivity wrote: > Anthony Liguori wrote: >>>> >>>> That kills the -no-kvm switch, which allows a single binary to be >>>> used both with and without kvm. Or do you think both >>>> target-i386+kvm and target-kvm ought to be kept? >>>> >>>> >>> >>> I meant here: target-i386 (with kvm support) and target-i386-kvm. >> >> target-i386 is an architecture. It can currently generate >> i386-softmmu, i386-user, x86_64-softmmu, x86_64-user. We're simply >> adding the ability to generate i386-kvm and x86_64-kvm. I'd like to >> find another name. >> >> I still want to be able to support kvm/qemu in the normal i386-softmmu. > > Thanks, that clears it up. I'll apply the patch. Can you wait on that? I'll submit a better one tonight. It was just an RFC :-) Regards, Anthony Liguori ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV