All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerzy Kasenberg <jerzy.kasenberg@tieto.com>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCHv2 0/9] Improve logging for Android
Date: Tue, 29 Oct 2013 12:43:32 +0100	[thread overview]
Message-ID: <CAHCYCoz4tSeimwrwVNENWsGf-ZDq9Huq9jB9dOgwccrPiF8Fow@mail.gmail.com> (raw)
In-Reply-To: <1383042118-21205-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>

Hi Andrei,

On 29 October 2013 11:21, Andrei Emeltchenko
<Andrei.Emeltchenko.news@gmail.com> wrote:
> From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
>
> Changes:
>         *v2: Added thread-safe helpers for printing properties, bdaddr, etc
>         after comments that simple printing is not thread-safe. The idea is to
>         use TLS (thread local storage) like bionic is doing for strerror for

Implementation of strerror in bionic and what is proposed here is
thread safe but not
useful if one wants to use one print to for two addresses or two
properties (one buffer
in one thread for two strings).

In my opinion there should be safe functions that explicitly get
string buffer as
argument. For address and uuid they already exist, property printing
was used in haltest
only in one place and moving buffer form btproperty2str to function
that calls it
makes sense to me.

If there is need for shortcut as for code lines that could be removed
in compilation,
wrapper function with pthread stuff can still be used (provided that
there is no same
type conversion call used in one print)

BTW strerror() works fine when called with value in range 0..131.
But when you call it with higher number there will be a problem
printf("%s\n%s\n\%s\n%s\n", strerror(1), strerror(2), strerror(132),
strerror(133));
prints:
Operation not permitted
No such file or directory
Unknown error 133
Unknown error 133

>         example. More info can be found on manpage for pthread_key_create.
>
> This patch series uses debug functions defined already for haltest and
> allows to print very helpful logs on Android target like shown below:
>
> ...
> hal-bluetooth.c:set_adapter_property() prop: type=BT_PROPERTY_ADAPTER_SCAN_MODE len=4 val=BT_SCAN_MODE_NONE
> ...
>
> Andrei Emeltchenko (9):
...

-- 
Jerzy

  parent reply	other threads:[~2013-10-29 11:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 10:44 [PATCHv1 0/4] Improve logging for Android Andrei Emeltchenko
2013-10-28 10:44 ` [PATCHv1 1/4] android/haltest: Export print property Andrei Emeltchenko
2013-10-28 10:44 ` [PATCHv1 2/4] android/haltest: Use pointer as parameter for debug Andrei Emeltchenko
2013-10-28 10:44 ` [PATCHv1 3/4] android/hal: Print full property in debug Andrei Emeltchenko
2013-10-28 10:44 ` [PATCHv1 4/4] android/hal: Add extra logs Andrei Emeltchenko
2013-10-29 10:21 ` [PATCHv2 0/9] Improve logging for Android Andrei Emeltchenko
2013-10-29 10:21   ` [PATCHv2 1/9] android/haltest: Export print property Andrei Emeltchenko
2013-10-29 10:21   ` [PATCHv2 2/9] android/haltest: Fix compile error making function static Andrei Emeltchenko
2013-10-29 10:31     ` Andrei Emeltchenko
2013-10-29 10:21   ` [PATCHv2 3/9] android/haltest: Use pointer as parameter for debug Andrei Emeltchenko
2013-10-29 10:21   ` [PATCHv2 4/9] android/hal: Print full property in debug Andrei Emeltchenko
2013-10-29 10:21   ` [PATCHv2 5/9] android/hal: Add extra logs Andrei Emeltchenko
2013-10-29 10:21   ` [PATCHv2 6/9] android/hal: Print adapter state Andrei Emeltchenko
2013-10-29 10:21   ` [PATCHv2 7/9] android/hal: Print adapter property in callback Andrei Emeltchenko
2013-10-29 10:21   ` [PATCHv2 8/9] android: Add thread-safe helpers Andrei Emeltchenko
2013-10-29 10:21   ` [PATCHv2 9/9] android: Use " Andrei Emeltchenko
2013-10-29 11:43   ` Jerzy Kasenberg [this message]
2013-10-29 12:18     ` [PATCHv2 0/9] Improve logging for Android Andrei Emeltchenko

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=CAHCYCoz4tSeimwrwVNENWsGf-ZDq9Huq9jB9dOgwccrPiF8Fow@mail.gmail.com \
    --to=jerzy.kasenberg@tieto.com \
    --cc=Andrei.Emeltchenko.news@gmail.com \
    --cc=linux-bluetooth@vger.kernel.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.