qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
	qemu-devel@nongnu.org,
	Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Daniel P . Berrange" <berrange@redhat.com>
Subject: Re: [RFC PATCH for-7.1] Remove the slirp submodule (and only compile with an external libslirp)
Date: Mon, 11 Apr 2022 10:11:40 +0200	[thread overview]
Message-ID: <cabbe1ff-a8da-c858-a4e1-00db856d1e6c@redhat.com> (raw)
In-Reply-To: <774adae3-ff97-44b2-a510-fd46c073eb1a@redhat.com>

On 4/11/22 09:11, Paolo Bonzini wrote:
> On 4/8/22 18:47, Thomas Huth wrote:
>> The only one that still seems to be missing a libslirp package is
>> OpenBSD - but I assume that they can add it to their ports system
>> quickly if required.
>>
>> So there is no real urgent need for keeping the slirp submodule in
>> the QEMU tree anymore. Thus let's drop the slirp submodule now and
>> rely on the libslirp packages from the distributions instead.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
> 
> I would like to have feature parity even with CFI.  I had written the 
> libslirp side a few months ago, but never tested it because I didn't get 
> to the QEMU side.
> 
> I updated it and you can find it at 
> https://gitlab.freedesktop.org/slirp/libslirp/-/merge_requests/117. I'll 
> get to the QEMU side now.

Also, doing this at the same time as a switch to Meson >=0.60 (probably 
0.61.x) would allow something like

option('slirp', type: 'feature', value: 'auto',
        description: 'libslirp user mode network backend support',
        deprecated: {'system': 'enabled', 'internal': 'auto'})

This keeps incremental builds working.  All of this should be doable in 
7.1, so this is not an objection to removing the submodule in 7.1.

Paolo



      reply	other threads:[~2022-04-11  8:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 16:47 [RFC PATCH for-7.1] Remove the slirp submodule (and only compile with an external libslirp) Thomas Huth
2022-04-10  4:49 ` Brad Smith
2022-04-10  9:06   ` Peter Maydell
2022-04-10 23:50     ` Brad Smith
2022-04-11  6:55       ` Thomas Huth
2022-04-14  7:23         ` Brad Smith
2022-04-19 16:24         ` Daniel P. Berrangé
2022-04-20 10:13           ` Thomas Huth
2022-04-23 22:06             ` Brad Smith
2022-04-11  7:11 ` Paolo Bonzini
2022-04-11  8:11   ` Paolo Bonzini [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=cabbe1ff-a8da-c858-a4e1-00db856d1e6c@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=berrange@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=samuel.thibault@ens-lyon.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).