Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20200120202708.111383-1-alainm@chromium.org> <6E55772A-01D5-4616-B3DB-CC22B935C855@holtmann.org>
 <CALWDO_WyZUvkOgXVSd12q7Trg_=LqSb9KQsXH9_C_k8_kD0ddQ@mail.gmail.com>
 <D0C01568-E48B-46ED-A2CC-D19FB2895756@gmail.com> <CALWDO_Wf3c5Vgt1a_p+pt_SpdkGJnLvneiZZ_1spRVuOr+9n0g@mail.gmail.com>
 <CALWDO_VC2z8ZxCQM0EBWvkEWJRQKaVy0butAeRc+uUqhpGcyMw@mail.gmail.com>
 <DFE9B731-5CB8-4FDA-8E89-1D5A51EAFB67@holtmann.org> <CALWDO_V=Q0725MhnA3hMnvL+hDbGVCa-RCT4d4NCysMo0Fvh7g@mail.gmail.com>
 <F6319DB4-FE70-45C8-A61D-D965CB659C9E@holtmann.org> <CALWDO_Vqboxt4JfV9yGVd5Jv5jZ-vwtOghh4tffpQpQzHuq6NQ@mail.gmail.com>
 <D61B5AA9-A509-4253-95D7-F6401C832081@holtmann.org>
In-Reply-To: <D61B5AA9-A509-4253-95D7-F6401C832081@holtmann.org>
From:   Alain Michaud <alainmichaud@google.com>
Date:   Thu, 23 Jan 2020 13:18:55 -0500
Message-ID: <CALWDO_Ub-orioZmPkCC4BoVfxHv9onP9QXz_M_T9nmh7_78LLQ@mail.gmail.com>
Subject: Re: [Bluez PATCH] doc: Add definition for Set Kernel Debug Level
To:     Marcel Holtmann <marcel@holtmann.org>,
        Archie Pusaka <apusaka@google.com>
Cc:     Johan Hedberg <johan.hedberg@gmail.com>,
        Alain Michaud <alainm@chromium.org>,
        BlueZ <linux-bluetooth@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Hi Marcel,

That makes sense.  Adding +Archie Pusaka as well who may have input into th=
is.

Thanks,
Alain

On Thu, Jan 23, 2020 at 1:16 PM Marcel Holtmann <marcel@holtmann.org> wrote=
:
>
> Hi Alain,
>
> > From a high level, this looks good for me although I agree, this is an
> > order of magnitude bigger in terms of scope.  Can you suggest perhaps
> > an interactive way to deliver this over a period of time, perhaps
> > prioritizing the BT_DEBUG kernel messages first? :)
>
> I am always in favor of increasing the ability to debug things, but we ne=
ed to do this in a clean fashion and not some short term hacks (since they =
will come back and haunt us). I like to get some review on my idea first.
>
> What we could do is work on the BT_DBG etc infrastructure to allow switch=
ing when dynamic_debug is not available. Then you would use some debugfs to=
ggle in /sys/kernel/debug/bluetooth since that is no stable API for us (and=
 of course the clear understanding that this toggle is temporary).
>
> Regards
>
> Marcel
>