From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Porting KVM to Mac OS? Date: Sun, 25 Jan 2009 12:00:28 -0600 Message-ID: <497CA8BC.6060205@codemonkey.ws> References: <5d649bdb0901250016u1e9dc38cn36bd4ceb523bd752@mail.gmail.com> <60AB6785-BDE0-46A8-BB5B-46B1B790634B@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Neo Jia , kvm@vger.kernel.org To: Alexander Graf Return-path: Received: from rn-out-0910.google.com ([64.233.170.187]:20917 "EHLO rn-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750705AbZAYSAp (ORCPT ); Sun, 25 Jan 2009 13:00:45 -0500 Received: by rn-out-0910.google.com with SMTP id k40so1552869rnd.17 for ; Sun, 25 Jan 2009 10:00:43 -0800 (PST) In-Reply-To: <60AB6785-BDE0-46A8-BB5B-46B1B790634B@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: Alexander Graf wrote: > Hi, > > On 25.01.2009, at 09:16, Neo Jia wrote: > >> hi, >> >> I am thinking if it is possible to port KVM to Mac OS (leopard). Is >> there anybody doing this already? > > I've considered doing it, but haven't gotten around to it, due to lack > of inspiration. > The biggest problem IMHO is the sync. Rewriting a kvm module for Mac > OS X should be fairly easy, but you'll miss all the good bugfixes from > upstream. Using the upstream code with a wrapper on the other hand is > probably a really big hassle, because osx doesn't really know about > mmu notifiers and a lot of other Linux internal things. Most of the special Linux internal things are optional when using the external kernel modules (in order to support older host kernels). If you rely on that, there shouldn't be a huge amount of Linux-specific dependencies. Best thing to do would be to avoid touching the KVM source code as much as humanly possible, and try to write a compatibility layer on top of the external kernel modules. You could even use awk trickery like make sync does. That way you can get bugfixes almost for free. Regards, Anthony Liguori > So if you come up with a good idea for this problem, I'd be glad to > help you out as much as time permits :-). > > Alex > >> If it is possible, which KVM release should I use as a start? >> >> Thanks, >> Neo >> -- >> I would remember that if researchers were not ambitious >> probably today we haven't the technology we are using! >> -- >> To unsubscribe from this list: send the line "unsubscribe kvm" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html