From: Greg KH <gregkh@linuxfoundation.org>
To: Chuang Zhang <zhangchuang3@xiaomi.corp-partner.google.com>
Cc: arve@android.com, tkjos@android.com, maco@android.com,
joel@joelfernandes.org, brauner@kernel.org, cmllamas@google.com,
surenb@google.com, linux-kernel@vger.kernel.org,
Chuang Zhang <zhangchuang3@xiaomi.com>
Subject: Re: [PATCH] Binder: Add timestamp and async from pid/tid to transaction record
Date: Thu, 13 Apr 2023 17:06:01 +0200 [thread overview]
Message-ID: <2023041324-molecule-clad-b580@gregkh> (raw)
In-Reply-To: <CAO+dPF8inueprEXeNMBWZtiqDzcjFQLbKLVq+qL0gGq3gRBu3w@mail.gmail.com>
On Thu, Apr 13, 2023 at 09:03:08PM +0800, Chuang Zhang wrote:
> On Thu, Apr 13, 2023 at 8:36 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> > On Thu, Apr 13, 2023 at 08:34:06PM +0800, Chuang Zhang wrote:
> > > On Thu, Apr 13, 2023 at 8:17 PM Greg KH <gregkh@linuxfoundation.org>
> > wrote:
> > > > And how are pid namespaces being handled here? I know it's just
> > > > debugging data but showing a pid from the wrong namespace probably
> > would
> > > > not be a good idea as it might get confusing quickly.
> > > >
> > > [chuang] Do you have any good suggestions? thanks
> >
> > I do not know what you are using this debug information for, nor how or
> > if Android uses pid namespaces (I think it does?)
> >
> [chuang]
> So can I use (struct binder_thread *async_from) instead ?
> and get the corresponding pid and tid through the following way:
> async_from->proc->pid
> async_from->pid
I don't know, try it and see!
I'm not quite sure what debugging information you can get here with the
pid, nor what you intend to do with it, so I can't answer this very
well, sorry.
thanks,
greg k-h
next prev parent reply other threads:[~2023-04-13 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 10:40 [PATCH] Binder: Add timestamp and async from pid/tid to transaction record Chuang Zhang
2023-04-13 10:51 ` Greg KH
[not found] ` <CAO+dPF9KFJe5h4wO47ypL2-__3+1mnzurdRcj6OCQ1wdku_7cA@mail.gmail.com>
2023-04-13 12:17 ` Greg KH
[not found] ` <CAO+dPF-YNtaZvVax8Z1QD9VtG36uc2C=uus4eR4H_vipEzu8Dw@mail.gmail.com>
2023-04-13 12:36 ` Greg KH
[not found] ` <CAO+dPF8inueprEXeNMBWZtiqDzcjFQLbKLVq+qL0gGq3gRBu3w@mail.gmail.com>
2023-04-13 15:06 ` Greg KH [this message]
2023-04-14 21:03 ` Carlos Llamas
[not found] ` <CAO+dPF9cb5tQzNkuO4hniTfWesACbr4z2YvT8XKj4afFgyYjjw@mail.gmail.com>
2023-04-20 14:28 ` Carlos Llamas
-- strict thread matches above, loose matches on Subject: below --
2023-04-13 9:38 Chuang Zhang
2023-04-13 10:17 ` Greg KH
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=2023041324-molecule-clad-b580@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=surenb@google.com \
--cc=tkjos@android.com \
--cc=zhangchuang3@xiaomi.com \
--cc=zhangchuang3@xiaomi.corp-partner.google.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