All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Sean Bruno <sbruno@freebsd.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] New Year's starting over ... bsd-user
Date: Wed, 04 Jan 2017 18:32:51 +0000	[thread overview]
Message-ID: <8760lu65gs.fsf@linaro.org> (raw)
In-Reply-To: <5dd3d27a-e630-4e92-43fa-13c131e9f880@freebsd.org>


Sean Bruno <sbruno@freebsd.org> writes:

> I'm pondering where to start with getting FreeBSD's bsd-user code into
> shape so it could actually be reviewed and accepted now that its sort of
> working again (signal handling fixed finally).

Also don't forget the parallel_cpus changes which were made for enhanced
atomic support. There was also work in fixing up exclusive_start/end
which is used for safe work like tb_flush.

> I almost feel like the existing code should be purged, except that it
> gives a good history (and this seems lazy to me).
>
> As a first pass, I guess, I'd like to at least make i386 user run on
> x86_64.  What would you folks like to see in a first pass?

One thing that bugs me about linux-user is the amount of copy&paste
repetition that goes on for the main run loop. Perhaps with a clean-up
of the unused BSD architectures we could explore how a re-factored
run loop could look with a view to moving to common run-loop code across
both?

Apart from syscall mapping and backend calls to the BSD ABI what
differences are there between the two user-mode implementations?

>
> sean
>
> ref: https://github.com/seanbruno/qemu-bsd-user/tree/bsd-user


--
Alex Bennée

  parent reply	other threads:[~2017-01-04 18:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03 16:18 [Qemu-devel] New Year's starting over ... bsd-user Sean Bruno
2017-01-03 17:11 ` Sean Bruno
2017-01-04  6:53   ` Thomas Huth
2017-01-04 15:49     ` Sean Bruno
2017-01-04 18:32 ` Alex Bennée [this message]
2017-01-04 19:00   ` Sean Bruno
2017-01-04 19:59   ` Peter Maydell
2017-01-05 11:33 ` Peter Maydell
2017-01-05 15:57   ` Sean Bruno
2017-01-05 16:03 ` Sean Bruno
2017-01-05 16:11   ` Peter Maydell
2017-01-05 16:42     ` Sean Bruno
2019-07-03 12:26 ` Philippe Mathieu-Daudé

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=8760lu65gs.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sbruno@freebsd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.