qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Sean Bruno <sbruno@freebsd.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] New Year's starting over ... bsd-user
Date: Tue, 3 Jan 2017 10:11:41 -0700	[thread overview]
Message-ID: <5540064c-613c-c0df-ae69-d41d45b4501d@freebsd.org> (raw)
In-Reply-To: <5dd3d27a-e630-4e92-43fa-13c131e9f880@freebsd.org>

[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]



On 01/03/17 09:18, 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
> 

Primitive example of what I think I should base my patchset on.  Its
invasive and large.

https://github.com/seanbruno/qemu-bsd-user/tree/merge1

That branch, is all the bsd-user changes that are pending in one large
"splat".  It excludes the new architectures (arm, aarch64, mips, mips64)
that we are actively using.  i386-bsd-user when compiled statically on
x86_64 will run a static (rescue) sh ... so, I think that's good.
x86_64 running on x86_64 just blows up.

As for sparc/sparc64 ... I'm tempted to delete them as nobody in freebsd
is actively maintaining them nor do we have any expectation that they
will work someday.

sean


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  reply	other threads:[~2017-01-03 17:11 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 [this message]
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é

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=5540064c-613c-c0df-ae69-d41d45b4501d@freebsd.org \
    --to=sbruno@freebsd.org \
    --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).