From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:53788)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1VRJOK-00055w-Ht
	for qemu-devel@nongnu.org; Wed, 02 Oct 2013 06:10:57 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1VRJOC-0001aC-1W
	for qemu-devel@nongnu.org; Wed, 02 Oct 2013 06:10:48 -0400
Received: from mail-wi0-x231.google.com ([2a00:1450:400c:c05::231]:41739)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1VRJOB-0001a3-FH
	for qemu-devel@nongnu.org; Wed, 02 Oct 2013 06:10:39 -0400
Received: by mail-wi0-f177.google.com with SMTP id cb5so632115wib.10
	for <qemu-devel@nongnu.org>; Wed, 02 Oct 2013 03:10:38 -0700 (PDT)
Date: Wed, 2 Oct 2013 12:10:36 +0200
From: Stefan Hajnoczi <stefanha@gmail.com>
Message-ID: <20131002101036.GL2142@stefanha-thinkpad.redhat.com>
References: <005f01cebdb3$131a9d30$394fd790$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <005f01cebdb3$131a9d30$394fd790$@gmail.com>
Subject: Re: [Qemu-devel] Minimal Qemu build for Plan9
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Ashish Kaila <ashishkaila9@gmail.com>
Cc: maneets@andrew.cmu.edu, qemu-devel@nongnu.org

On Mon, Sep 30, 2013 at 04:00:05AM -0400, Ashish Kaila wrote:
> Additionally if someone could point me to a to-do list of things to look out
> for while porting Qemu on a new platform (new OS/hardware), I would be
> extremely grateful.

Has glib been ported to Plan 9?  You need it since much of QEMU uses
this library.

I guess the code you'll need to port are timers, thread pools, signal
handling, thread-local storage and pthread usage, and maybe some
mmap/mprotect calls.

QEMU uses a coroutines implementation which is done using
makecontext()/sigsetjmp()/siglongjmp() on Linux.  Other OSes have their
own coroutine implementations (see coroutine-*.c).

This port is a lot of work.  If you want to upstream the patches,
consider if you're willing to test and maintain Plan 9 support in the
long term.  Since QEMU is actively developed just getting a port merged
isn't enough, you need to stay involved and continue maintaining it
otherwise the port would bitrot/need to be dropped.

Stefan