qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Ashish Kaila <ashishkaila9@gmail.com>
Cc: maneets@andrew.cmu.edu, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Minimal Qemu build for Plan9
Date: Wed, 2 Oct 2013 12:10:36 +0200	[thread overview]
Message-ID: <20131002101036.GL2142@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <005f01cebdb3$131a9d30$394fd790$@gmail.com>

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

      parent reply	other threads:[~2013-10-02 10:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-30  8:00 [Qemu-devel] Minimal Qemu build for Plan9 Ashish Kaila
2013-09-30 13:37 ` Andreas Färber
2013-09-30 13:55 ` Peter Maydell
2013-10-02 10:10 ` Stefan Hajnoczi [this message]

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=20131002101036.GL2142@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=ashishkaila9@gmail.com \
    --cc=maneets@andrew.cmu.edu \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).