qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Kamil Rytarowski <n54@gmx.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Large patch set advice
Date: Thu, 26 Apr 2018 13:53:40 -0600	[thread overview]
Message-ID: <CANCZdfpWBLRbdY3rf8LwuxNPxMbB_HCZP6oBPJ4Kone6AeL5cQ@mail.gmail.com> (raw)
In-Reply-To: <28c598cc-40e4-8191-a48c-5edf8eeb9cf0@gmx.com>

On Thu, Apr 26, 2018 at 5:22 AM, Kamil Rytarowski <n54@gmx.com> wrote:

> On 26.04.2018 10:11, Peter Maydell wrote:
> > On 25 April 2018 at 20:57, Warner Losh <imp@bsdimp.com> wrote:
> >> I’ve foolishly volunteered to rebase all the changes that the bad-user
> >> mode folks have done to a recent master rev to get these changes
> upstreamed.
> >> A number of people have been working on this for a long time. It’s
> possible
> >> now to run almost any FreeBSD binary from all the architectures. We use
> it
> >> to do ‘native’ builds of tens of thousands of packages in a chroot (so
> >> building FreeBSD/arm packages on a FreeBSD amd64 box). The diffs are
> quite
> >> large (on the order of 42k lines), so I anticipate some bumps in moving
> >> this stuff upstream.
> >
> > So, first up, thanks for agreeing to do this. It sounds from your
> > mail like you're already pretty well aware of the usual pitfalls
> > with this kind of work, and I don't really have much to add that's
> > QEMU specific that nobody else has said already.
> >
> > One question I do have is about the other BSDs: bsd-user at least
> > in theory is supposed to support freebsd, netbsd and openbsd.
> > Your patchsets should fix freebsd, but do you know what the status
> > is of netbsd and openbsd? Upstream we do compiletest but no runtime
> > testing; I think last time I tried it they didn't work very well,
> > but it would be worth checking with the other BSDs downstream to
> > see if they're using bsd-user and to make sure we don't break anything
> > that is currently working for netbsd/openbsd...
> >
>
> I'm looking forward to see it updated for FreeBSD first. We can
> reschedule NetBSD part for later.
>
> Feel free to CC me for code review.
>

Sure. Will do. Do you have NetBSD patches against the git repo as well?

Warner

  reply	other threads:[~2018-04-26 19:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-25 19:57 [Qemu-devel] Large patch set advice Warner Losh
2018-04-26  4:18 ` Thomas Huth
2018-04-26  7:02 ` Markus Armbruster
2018-04-26  7:09 ` Daniel P. Berrangé
2018-04-26  8:11 ` Peter Maydell
2018-04-26 11:22   ` Kamil Rytarowski
2018-04-26 19:53     ` Warner Losh [this message]
2018-04-26 19:58       ` Kamil Rytarowski
2018-04-26 19:51   ` Warner Losh
2018-04-27 10:05     ` Peter Maydell
2018-04-30 14:44   ` Warner Losh
2018-04-30 15:05     ` Peter Maydell

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=CANCZdfpWBLRbdY3rf8LwuxNPxMbB_HCZP6oBPJ4Kone6AeL5cQ@mail.gmail.com \
    --to=imp@bsdimp.com \
    --cc=n54@gmx.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).