From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
libvir-list@redhat.com,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH for-5.0 3/4] Remove the core bluetooth code
Date: Sat, 1 Feb 2020 19:59:00 +0100 [thread overview]
Message-ID: <1707e18a-6505-4efe-a85d-7525267bd72a@redhat.com> (raw)
In-Reply-To: <CAAdtpL7vPCQ8k91nvBWc_NLrmhu6OPVprUSL8uzi_v6HMiSrnw@mail.gmail.com>
On 01/02/2020 19.53, Philippe Mathieu-Daudé wrote:
> On Sat, Feb 1, 2020 at 7:51 PM Thomas Huth <thuth@redhat.com> wrote:
>> On 01/02/2020 17.09, Philippe Mathieu-Daudé wrote:
>>> On 11/20/19 10:10 AM, Thomas Huth wrote:
>>>> It's been deprecated since QEMU v3.1. We've explicitly asked in the
>>>> deprecation message that people should speak up on qemu-devel in case
>>>> they are still actively using the bluetooth part of QEMU, but nobody
>>>> ever replied that they are really still using it.
>>>>
>>>> I've tried it on my own to use this bluetooth subsystem for one of my
>>>> guests, but I was also not able to get it running anymore: When I was
>>>> trying to pass-through a real bluetooth device, either the guest did
>>>> not see the device at all, or the guest crashed.
>>>>
>>>> Even worse for the emulated device: When running
>>>>
>>>> qemu-system-x86_64 -bt device:keyboard
>>>>
>>>> QEMU crashes once you hit a key.
>>>>
>>>> So it seems like the bluetooth stack is not only neglected, it is
>>>> completely bitrotten, as far as I can tell. The only attention that
>>>> this code got during the past years were some CVEs that have been
>>>> spotted there. So this code is a burden for the developers, without
>>>> any real benefit anymore. Time to remove it.
>>>>
>>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>>> ---
>>>> Makefile.objs | 2 -
>>>> bt-host.c | 198 ----
>>>> bt-vhci.c | 167 ----
>>>> configure | 31 -
>>>> hw/Kconfig | 1 -
>>>> hw/Makefile.objs | 1 -
>>>> hw/bt/Kconfig | 2 -
>>>> hw/bt/Makefile.objs | 3 -
>>>> hw/bt/core.c | 143 ---
>>>> hw/bt/hci-csr.c | 512 ----------
>>>> hw/bt/hci.c | 2263 ------------------------------------------
>>>> hw/bt/hid.c | 553 -----------
>>>> hw/bt/l2cap.c | 1367 -------------------------
>>>> hw/bt/sdp.c | 989 ------------------
>>>> include/hw/bt.h | 2177 ----------------------------------------
>>>> include/sysemu/bt.h | 20 -
>>>> qemu-deprecated.texi | 7 -
>>>> qemu-options.hx | 79 --
>>>> vl.c | 136 ---
>>>> 19 files changed, 8651 deletions(-)
>>>> delete mode 100644 bt-host.c
>>>> delete mode 100644 bt-vhci.c
>>>> delete mode 100644 hw/bt/Kconfig
>>>> delete mode 100644 hw/bt/Makefile.objs
>>>> delete mode 100644 hw/bt/core.c
>>>> delete mode 100644 hw/bt/hci-csr.c
>>>> delete mode 100644 hw/bt/hci.c
>>>> delete mode 100644 hw/bt/hid.c
>>>> delete mode 100644 hw/bt/l2cap.c
>>>> delete mode 100644 hw/bt/sdp.c
>>>> delete mode 100644 include/hw/bt.h
>>>> delete mode 100644 include/sysemu/bt.h
>>>>
>>> [...]> diff --git a/configure b/configure
>>>> index 6099be1d84..ecce4ada2d 100755
>>>> --- a/configure
>>>> +++ b/configure
>>>> @@ -349,7 +349,6 @@ unset target_list_exclude
>>>> # Distributions want to ensure that several features are compiled in, and it
>>>> # is impossible without a --enable-foo that exits if a feature is not found.
>>>>
>>>> -bluez=""
>>>> brlapi=""
>>>> curl=""
>>>> curses=""
>>>> @@ -1151,10 +1150,6 @@ for opt do
>>>> ;;
>>>> --enable-brlapi) brlapi="yes"
>>>> ;;
>>>> - --disable-bluez) bluez="no"
>>>> - ;;
>>>> - --enable-bluez) bluez="yes"
>>>> - ;;
>>>
>>> Now than I'm bisecting over this commit, I realize removing this
>>> option was not a good idea, we should have done like commit
>>> cb6414dfec8 or 315d3184525:
>>>
>>> @@ -886,10 +885,6 @@ for opt do
>>> - --disable-uuid) uuid="no"
>>> - ;;
>>> - --enable-uuid) uuid="yes"
>>> - ;;
>>> ...
>>> + --enable-uuid|--disable-uuid)
>>> + echo "$0: $opt is obsolete, UUID support is always built" >&2
>>> + ;;
>>
>> Looks trivial ... so if it bugs you, just send a patch?
>
> I thought about it but this won't fix much, it is too late now.
>
> I simply wanted to share this bugged me so we try to avoid doing the
> same mistake again.
Makes sense. I'll try to remember it for the future.
Thomas
next prev parent reply other threads:[~2020-02-01 19:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 9:10 [PATCH for-5.0 0/4] Remove the deprecated bluetooth subsystem Thomas Huth
2019-11-20 9:10 ` [PATCH for-5.0 1/4] hw/arm/nseries: Replace the bluetooth chardev with a "null" chardev Thomas Huth
2019-11-20 10:51 ` Peter Maydell
2019-11-20 9:10 ` [PATCH for-5.0 2/4] hw/usb: Remove the USB bluetooth dongle device Thomas Huth
2019-11-20 9:35 ` [libvirt] " Ján Tomko
2019-11-20 9:10 ` [PATCH for-5.0 3/4] Remove the core bluetooth code Thomas Huth
2019-11-20 9:36 ` [libvirt] " Ján Tomko
2020-02-01 16:09 ` Philippe Mathieu-Daudé
2020-02-01 18:50 ` Thomas Huth
2020-02-01 18:53 ` Philippe Mathieu-Daudé
2020-02-01 18:59 ` Thomas Huth [this message]
2020-02-05 15:26 ` Paolo Bonzini
2020-02-05 17:40 ` Aleksandar Markovic
2020-02-05 17:46 ` Thomas Huth
2020-02-05 17:54 ` Daniel P. Berrangé
2020-02-05 17:51 ` Daniel P. Berrangé
2020-02-05 18:03 ` Aleksandar Markovic
2020-02-05 18:53 ` Aleksandar Markovic
2020-02-06 6:49 ` Thomas Huth
2020-02-05 19:13 ` Philippe Mathieu-Daudé
2020-02-06 9:56 ` Daniel P. Berrangé
2019-11-20 9:10 ` [PATCH for-5.0 4/4] Remove libbluetooth / bluez from the CI tests Thomas Huth
2019-11-20 9:58 ` [PATCH for-5.0 0/4] Remove the deprecated bluetooth subsystem Paolo Bonzini
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=1707e18a-6505-4efe-a85d-7525267bd72a@redhat.com \
--to=thuth@redhat.com \
--cc=f4bug@amsat.org \
--cc=kraxel@redhat.com \
--cc=libvir-list@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.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).