public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: Neo Jia <neojia@gmail.com>, kvm@vger.kernel.org
Subject: Re: Porting KVM to Mac OS?
Date: Sun, 25 Jan 2009 12:00:28 -0600	[thread overview]
Message-ID: <497CA8BC.6060205@codemonkey.ws> (raw)
In-Reply-To: <60AB6785-BDE0-46A8-BB5B-46B1B790634B@suse.de>

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


  parent reply	other threads:[~2009-01-25 18:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-25  8:16 Porting KVM to Mac OS? Neo Jia
2009-01-25  9:27 ` Alexey Eremenko
2009-01-25 10:38 ` Alexander Graf
2009-01-25 12:15   ` Izik Eidus
2009-01-25 18:00   ` Anthony Liguori [this message]
2009-02-16 18:01     ` Neo Jia
2009-02-16 18:12       ` Alexander Graf

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=497CA8BC.6060205@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=agraf@suse.de \
    --cc=kvm@vger.kernel.org \
    --cc=neojia@gmail.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