From: Andrzej Hajda <andrzej.hajda@intel.com>
To: Eric Dumazet <edumazet@google.com>
Cc: netdev@vger.kernel.org, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Chris Wilson <chris@chris-wilson.co.uk>,
dri-devel@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Jakub Kicinski <kuba@kernel.org>,
David Airlie <airlied@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [Intel-gfx] [PATCH v7 2/7] lib/ref_tracker: improve printing stats
Date: Fri, 21 Apr 2023 16:30:34 +0200 [thread overview]
Message-ID: <a10480c6-162b-a886-28f6-e95930d4664b@intel.com> (raw)
In-Reply-To: <CANn89iLUDXz9VAtCQ6Gr2Jkxogdu_5g0tN9iCkAB0JD_B_05Gw@mail.gmail.com>
On 21.04.2023 16:21, Eric Dumazet wrote:
> On Fri, Apr 21, 2023 at 1:35 PM Andrzej Hajda <andrzej.hajda@intel.com> wrote:
>> In case the library is tracking busy subsystem, simply
>> printing stack for every active reference will spam log
>> with long, hard to read, redundant stack traces. To improve
>> readabilty following changes have been made:
>> - reports are printed per stack_handle - log is more compact,
>> - added display name for ref_tracker_dir - it will differentiate
>> multiple subsystems,
>> - stack trace is printed indented, in the same printk call,
>> - info about dropped references is printed as well.
>>
>> Signed-off-by: Andrzej Hajda <andrzej.hajda@intel.com>
>> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
>> ---
>> include/linux/ref_tracker.h | 15 ++++++--
>> lib/ref_tracker.c | 90 +++++++++++++++++++++++++++++++++++++++------
>> 2 files changed, 91 insertions(+), 14 deletions(-)
>>
>> diff --git a/include/linux/ref_tracker.h b/include/linux/ref_tracker.h
>> index 87a92f2bec1b88..fc9ef9952f01fd 100644
>> --- a/include/linux/ref_tracker.h
>> +++ b/include/linux/ref_tracker.h
>> @@ -17,12 +17,19 @@ struct ref_tracker_dir {
>> bool dead;
>> struct list_head list; /* List of active trackers */
>> struct list_head quarantine; /* List of dead trackers */
>> + char name[32];
>> #endif
>> };
>>
>> #ifdef CONFIG_REF_TRACKER
>> -static inline void ref_tracker_dir_init(struct ref_tracker_dir *dir,
>> - unsigned int quarantine_count)
>> +
>> +/* Temporary allow two and three arguments, until consumers are converted */
>> +#define ref_tracker_dir_init(_d, _q, args...) _ref_tracker_dir_init(_d, _q, ##args, #_d)
>> +#define _ref_tracker_dir_init(_d, _q, _n, ...) __ref_tracker_dir_init(_d, _q, _n)
>> +
> We only have four callers of ref_tracker_dir_init() .
>
> Why not simply add a name on them, and avoid this magic ?
If this can be done in one patch, that's great.
Regards
Andrzej
next prev parent reply other threads:[~2023-04-21 14:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 11:35 [Intel-gfx] [PATCH v7 0/7] drm/i915: use ref_tracker library for tracking wakerefs Andrzej Hajda
2023-04-21 11:35 ` [Intel-gfx] [PATCH v7 1/7] lib/ref_tracker: add unlocked leak print helper Andrzej Hajda
2023-04-21 14:24 ` Eric Dumazet
2023-04-21 11:35 ` [Intel-gfx] [PATCH v7 2/7] lib/ref_tracker: improve printing stats Andrzej Hajda
2023-04-21 14:21 ` Eric Dumazet
2023-04-21 14:30 ` Andrzej Hajda [this message]
2023-04-21 11:35 ` [Intel-gfx] [PATCH v7 3/7] lib/ref_tracker: add printing to memory buffer Andrzej Hajda
2023-04-21 11:35 ` [Intel-gfx] [PATCH v7 4/7] lib/ref_tracker: remove warnings in case of allocation failure Andrzej Hajda
2023-04-21 14:21 ` Eric Dumazet
2023-04-21 11:35 ` [Intel-gfx] [PATCH v7 5/7] drm/i915: Correct type of wakeref variable Andrzej Hajda
2023-04-21 11:35 ` [Intel-gfx] [PATCH v7 6/7] drm/i915: Replace custom intel runtime_pm tracker with ref_tracker library Andrzej Hajda
2023-04-23 4:45 ` Zhou Furong
2023-04-21 11:35 ` [Intel-gfx] [PATCH v7 7/7] drm/i915: track gt pm wakerefs Andrzej Hajda
2023-04-23 3:53 ` Zhou Furong
2023-04-21 12:56 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: use ref_tracker library for tracking wakerefs (rev8) Patchwork
2023-04-21 12:56 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-04-21 13:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-04-21 14:09 ` [Intel-gfx] [PATCH v7 0/7] drm/i915: use ref_tracker library for tracking wakerefs Jakub Kicinski
2023-04-21 20:57 ` [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: use ref_tracker library for tracking wakerefs (rev8) Patchwork
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=a10480c6-162b-a886-28f6-e95930d4664b@intel.com \
--to=andrzej.hajda@intel.com \
--cc=airlied@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rodrigo.vivi@intel.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