From: Yuanyuan Zhong <yzhong@purestorage.com>
To: elver@google.com
Cc: akpm@linux-foundation.org, corbet@lwn.net, dvyukov@google.com,
glider@google.com, joern@purestorage.com,
kasan-dev@googlegroups.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH mm v2] kfence: show cpu and timestamp in alloc/free info
Date: Wed, 14 Jul 2021 11:37:55 -0600 [thread overview]
Message-ID: <20210714173755.1083-1-yzhong@purestorage.com> (raw)
In-Reply-To: <20210714082145.2709233-1-elver@google.com>
> + /* Timestamp matches printk timestamp format. */
> + seq_con_printf(seq, "%s by task %d on cpu %d at %lu.%06lus:\n",
> + show_alloc ? "allocated" : "freed", meta->alloc_track.pid,
> + meta->alloc_track.cpu, (unsigned long)ts_sec, rem_nsec / 1000);
s/meta->alloc_track\./track->/
next prev parent reply other threads:[~2021-07-14 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 8:21 Marco Elver
2021-07-14 17:37 ` Yuanyuan Zhong [this message]
2021-07-14 17:54 ` Marco Elver
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=20210714173755.1083-1-yzhong@purestorage.com \
--to=yzhong@purestorage.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=joern@purestorage.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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