From: Sean Bruno <sbruno@freebsd.org>
To: Thomas Huth <huth@tuxfamily.org>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
Fabien Chouteau <chouteau@adacore.com>,
Artyom Tarasenko <atar4qemu@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] New Year's starting over ... bsd-user
Date: Wed, 4 Jan 2017 08:49:43 -0700 [thread overview]
Message-ID: <6d7ed825-b712-62db-a6de-e42eece27075@freebsd.org> (raw)
In-Reply-To: <ad4e7809-93e9-b5fa-a6a2-763fa8f1c97a@tuxfamily.org>
[-- Attachment #1: Type: text/plain, Size: 2113 bytes --]
On 01/03/17 23:53, Thomas Huth wrote:
> On 03.01.2017 18:11, Sean Bruno wrote:
>>
>>
>> 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.
>
> It's broken ... nobody maintains it ... and we've got too many
> unmaintained bit-rotten files in the QEMU tree, so IMHO just go ahead
> and send a patch to remove the bsud-user sparc support. If anybody ever
> needs it again, they can revert the commit or simply submit a patch with
> the fixed code.
>
> Thomas
>
>
>
I agree with the exception that its way easier to nuke the sparc/64 code
after I update bsd-user. Right now, its a tangle of #ifdef in a couple
of files that I'd like to un-tangle first.
Regardless, I can maintain the sparc/64 bsd-user target outside of qemu
until such time as someone wants to make it work or the heat death of
the universe occurs.
sean
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2017-01-04 15:49 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 [this message]
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=6d7ed825-b712-62db-a6de-e42eece27075@freebsd.org \
--to=sbruno@freebsd.org \
--cc=atar4qemu@gmail.com \
--cc=chouteau@adacore.com \
--cc=huth@tuxfamily.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.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).