qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Sean Bruno <sbruno@freebsd.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	 Kamil Rytarowski <kamil@netbsd.org>,
	Thomas Huth <thuth@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [Qemu-devel] New Year's starting over ... bsd-user
Date: Wed, 3 Jul 2019 14:26:56 +0200	[thread overview]
Message-ID: <75c05e38-1dfe-81a0-a403-791489173fed@redhat.com> (raw)
In-Reply-To: <5dd3d27a-e630-4e92-43fa-13c131e9f880@freebsd.org>

[Reviving an old thread]

Hi Sean,

On 1/3/17 5:18 PM, Sean Bruno wrote:
> 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).
> 
> 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?
> 
> sean
> 
> ref: https://github.com/seanbruno/qemu-bsd-user/tree/bsd-user

Looking at your repository I see you are still active and merging
patches from other users.

Could you summarize how your tree differs from the upstream one?
I guess your work could benefit other users, stucked at the current
broken state of bsd-user.

Some users who reported they switched to the Unicorn Engine [*], I
haven't looked at it yet, since I found this thread first, while reading
on deprecating unsupported code (another old thread):
https://lists.gnu.org/archive/html/qemu-devel/2017-03/msg03519.html

Thanks,

Phil.

[*] https://www.unicorn-engine.org/



      parent reply	other threads:[~2019-07-03 12:28 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
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é [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=75c05e38-1dfe-81a0-a403-791489173fed@redhat.com \
    --to=philmd@redhat.com \
    --cc=berrange@redhat.com \
    --cc=kamil@netbsd.org \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sbruno@freebsd.org \
    --cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).