All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Warner Losh <imp@bsdimp.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: qemu bsd-user plans
Date: Mon, 11 Jan 2021 13:27:01 +0000	[thread overview]
Message-ID: <20210111132701.GD1172772@redhat.com> (raw)
In-Reply-To: <CANCZdfo_CDqyG339HwNQb_K+sbsV0t+3nJMXVFf=mYrS3nsv-Q@mail.gmail.com>

On Fri, Jan 08, 2021 at 12:41:30PM -0700, Warner Losh wrote:
> The FreeBSD project has rewritten bsd-user. We've been working on this for
> quite some time (the earliest commits date from 2013). Maybe a dozen people
> have worked on this over time, and there's 3 or 4 active developers focused
> on FreeBSD changes at the moment.

The fact that you have 3-4 people involved in this work is will be very
helpful to you going forward with a QEMU maintenance.

The biggest problem with getting code merged into QEMU is an insufficient
number of reviewers for the amount of patches sent. Since we have a rule
that patches need a review from someone else who isn't the author, if there
are two people with expertize to review patches in a given QEMU subsystem,
then they can become self-sufficient and review each others patches on
qemu-devel, which then makes merging much more productive.

If anyone wants to be automatically CC'd on patches for bsd-user for the
purposes of acting as a designated reviewer, they can added to MAINTAINERS
file to, alongside the primary maintainer(s).


> So, my new plan is to rebase what changes I can to the tip of master and
> submit those for review. I'll work with the developers on the FreeBSD side
> to ensure they are included in reviews in addition to the normal qemu-devel
> list. This will allow us to pare down the deltas between our code and
> upstream to allow us to make progress. The changes will be held to the
> standard 'makes things better'. Given how broken bsd-user is today in qemu
> upstream, at first that will a very easy standard to make.
>
> The first patch I'll submit will be changing MAINTAINERS to point to me,
> since I'm acting as the point person in this effort. I'll then re-submit
> some other changes that I've submitted in the past, but CC the FreeBSD
> folks that are currently active (they were only CC'd to former developers
> who lack the time to review).

> But before I get too far down this path, I thought I'd send out what's
> going on to qemu-devel so I can get feedback and adjust the plan into
> something that's mutually agreeable so time I put towards this is not
> wasted.

No objections from me. Since current bsd-user is orphaned, largely
unusable, and you're volunteering your time to make it better, I'm
supportive of whatever you believe is the most time efficient way
to improve bsd-user.

I presume some of the current QEMU maintainers knowledgable about
linux-user will be able to review the patches, and as mentioned
above, if other BSD devs currently active in bsd-user work can
also provide reviews on qemu-devel that'll be useful long term.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  parent reply	other threads:[~2021-01-11 13:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 19:41 qemu bsd-user plans Warner Losh
2021-01-08 19:56 ` Peter Maydell
2021-01-08 20:17   ` Warner Losh
2021-01-09 17:02     ` Kyle Evans
2021-01-09 17:35       ` Warner Losh
2021-01-11 12:49   ` Thomas Huth
2021-01-11 13:27 ` Daniel P. Berrangé [this message]
2021-01-12  0:33   ` Warner Losh

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=20210111132701.GD1172772@redhat.com \
    --to=berrange@redhat.com \
    --cc=imp@bsdimp.com \
    --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 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.